rick.curl Posted November 10, 2013 Posted November 10, 2013 I purchased some used ApplianceLinc 2456S3's on eBay and it turns out they are the older "V2" version, revision 1.3. When I send them a command, they do switch the load on or off properly, but they are not reporting their status. When I look at the ISY Administrative Console I get the error "Cannot communicate with (7 CD 42 1). Please check connections". If I click Query, then the status is properly reported, so I know they are reporting status- it's just that the ISY is not seeing it. Maybe it's timing out too fast? Is there anything I can do to make these work properly? Thanks! -Rick
LeeG Posted November 10, 2013 Posted November 10, 2013 ApplianceLincs do not report local status changes. Do not know what the comm issue is but it is unrelated to an ApplianceLinc not reporting local status changes. The newest Insteon On/Off Module 2635-222 (ApplianceLinc replacement) does report local state changes.
rick.curl Posted November 10, 2013 Author Posted November 10, 2013 Update: I **think** I have found a workaround. For each of the 2456S3 V2's I have added a program like this: If Status 'Deck Light' is not Responding Then Set 'Deck Light' Query Else - No actions This seems to be working fine. Is there a better solution, though? -Rick
Brian H Posted November 10, 2013 Posted November 10, 2013 Seven of my nine 2456S3 ApplianceLinc modules are v1.3s and I rarely get those error messages you are reporting. Is this every time you change one of their outputs though your ISY console or after the 3:00 AM Query? Maybe once a month for some odd reason, a few of mine will not respond properly to the 3:00 AM Query and at that time there should be no power line issues. I think the firmware may have slight quirks as I found a few if you added an X10 Scene Address in addition to a Primary X10 Address.
rick.curl Posted November 10, 2013 Author Posted November 10, 2013 Hi Brian- It seems to be almost every time I send a command to them. I just tried sending 25 commands in a row, and I got the error message 22 times. I tried a different V1.3 device and got similar results. Using the program I mentioned above I still see the error message on the Admin Console, but the status is correct every time now. I just started tinkering with this today, so the 3AM query has not run yet.
LeeG Posted November 10, 2013 Posted November 10, 2013 When the roof is leaking a bucket can be used to catch the water or the leak can be fixed. The Program to correct the status is a bucket. There is clearly a communications problem when that many direct commands fail. Direct commands are automatically retried multiple times so a failure indicates multiple attempts have failed.
Brian H Posted November 10, 2013 Posted November 10, 2013 An Event Viewer running on level 3 would show the messages and success or failure. Along with the hops left= count. That I suspect is 0.
rick.curl Posted November 11, 2013 Author Posted November 11, 2013 I stopped the program that triggers a query when the device doesn't respond. Then used the event viewer on level 3. The3 symptoms were a little different then earlier today. I sent a few on and off commands to the device and it did turn the load on and off, but the status always stayed "off". I did not get any "Cannot communicate" errors during this capture: Sun 11/10/2013 07:06:54 PM : [iNST-TX-I1 ] 02 62 07 CD 42 0F 11 FF Sun 11/10/2013 07:06:54 PM : [iNST-ACK ] 02 62 07.CD.42 0F 11 FF 06 LTONRR (FF) Sun 11/10/2013 07:06:55 PM : [iNST-SRX ] 02 50 07.CD.42 1E.49.6C A7 11 FE LTONRR (FE) Sun 11/10/2013 07:06:55 PM : [std-Direct Nack] 07.CD.42-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 11/10/2013 07:07:09 PM : [iNST-TX-I1 ] 02 62 07 CD 42 0F 13 00 Sun 11/10/2013 07:07:09 PM : [iNST-ACK ] 02 62 07.CD.42 0F 13 00 06 LTOFFRR(00) Sun 11/10/2013 07:07:09 PM : [iNST-SRX ] 02 50 07.CD.42 1E.49.6C A3 13 FE LTOFFRR(FE) Sun 11/10/2013 07:07:09 PM : [std-Direct Nack] 07.CD.42-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 11/10/2013 07:07:24 PM : [iNST-TX-I1 ] 02 62 07 CD 42 0F 11 FF Sun 11/10/2013 07:07:24 PM : [iNST-ACK ] 02 62 07.CD.42 0F 11 FF 06 LTONRR (FF) Sun 11/10/2013 07:07:25 PM : [iNST-SRX ] 02 50 07.CD.42 1E.49.6C A7 11 FE LTONRR (FE) Sun 11/10/2013 07:07:25 PM : [std-Direct Nack] 07.CD.42-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 I tried it a few minutes later and I did get a "Cannot communicate" error: Sun 11/10/2013 07:15:06 PM : [iNST-TX-I1 ] 02 62 07 CD 42 0F 11 FF Sun 11/10/2013 07:15:06 PM : [iNST-ACK ] 02 62 07.CD.42 0F 11 FF 06 LTONRR (FF) Sun 11/10/2013 07:15:06 PM : [iNST-SRX ] 02 50 07.CD.42 1E.49.6C A7 11 FE LTONRR (FE) Sun 11/10/2013 07:15:06 PM : [std-Direct Nack] 07.CD.42-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 11/10/2013 07:15:06 PM : [ 7 CD 42 1] ERR 1 By the way, all of the newer ApplianceLinc's are working first time, every time, with no errors. It seems to be only the older devices that are having trouble. Can one of you experts help me understand what this is telling me? Thanks! -Rick
LeeG Posted November 11, 2013 Posted November 11, 2013 The newest ApplianceLinc equivalent (Insteon On/Off Module 2635-222) is a Dual Band device. The devices that carry the actual ApplianceLinc name are not Dual Band. The event trace shows poor powerline comm. Hops Left=1 is okay but the next command issued has a Hops Left=0 (as bad as it gets and still work). The fact that Hops Left=x count is changing from command to command indicates a unreliable comm problem is likely.
Recommended Posts