jimbarstow Posted March 28, 2014 Posted March 28, 2014 I had a single tree with LED lights controlled by an insteon on/off module. It was referenced in a program that turned it on at sunset and off at 11 pm. I just added lights to another tree controlled by a new on/off module. The new module responds just fine but the ISY now says it can't communicate with the original one. I did a factory reset on the original and added it back to the system. I can turn it on and off manually via the ISY interface but I get a complaint that it can't communicate. I also updated the program to turn both sets of tree lights on at sunset and the program runs fine. It appears that sending a command works but the ISY isn't getting anything back.
jimbarstow Posted March 28, 2014 Author Posted March 28, 2014 Safari wouldn't let me save a log but firefox would: Thu 03/27/2014 08:15:40 PM : [iNST-TX-I1 ] 02 62 27 DA 5D 0F 11 FF Thu 03/27/2014 08:15:40 PM : [iNST-ACK ] 02 62 27.DA.5D 0F 11 FF 06 LTONRR (FF) Thu 03/27/2014 08:15:41 PM : [iNST-SRX ] 02 50 27.DA.5D 2A.A1.0F 2B 11 FF LTONRR (FF) Thu 03/27/2014 08:15:41 PM : [std-Direct Ack] 27.DA.5D-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/27/2014 08:15:41 PM : [ 27 DA 5D 1] ST 255 Thu 03/27/2014 08:15:48 PM : [iNST-TX-I1 ] 02 62 27 DA 5D 0F 13 00 Thu 03/27/2014 08:15:48 PM : [iNST-ACK ] 02 62 27.DA.5D 0F 13 00 06 LTOFFRR(00) Thu 03/27/2014 08:15:52 PM : [ 27 DA 5D 1] ERR 1
jimbarstow Posted March 28, 2014 Author Posted March 28, 2014 Two more things I tried: 1. I unplugged the new on/off module and the problem with communication with the original persisted 2. I cycled the power on the PLM but it didn't fix it either
LeeG Posted March 28, 2014 Posted March 28, 2014 The event trace shows comm sending the On command is good. The device did not answer the Off command. When a device will turn On but not Off it is often the type of load being controlled. The load is generating some form of interference when powered. Unplug the load and see if the Off command works.
jimbarstow Posted March 28, 2014 Author Posted March 28, 2014 I removed the load on the problematic on/off module and it still failed. I then unplugged the new module and the old one continued to fail.
oberkc Posted March 28, 2014 Posted March 28, 2014 Or...the device DID answer, but the ISY could not hear it. What devices do you have plugged into the same outlet or circuit as the PLM?
LeeG Posted March 28, 2014 Posted March 28, 2014 Run the same On/Off test with 27.DA.5D and no load (event viewer at LEVEL 3). It is odd for a device to respond to an On command but not respond to an Off command that is not load related.
oberkc Posted March 28, 2014 Posted March 28, 2014 Perhaps I misunderstand something, but when I read "I can turn it on and off manually via the ISY interface but I get a complaint that it can't communicate", it makes me think that the command is getting TO the device, but the acknowledgement is not getting back to the ISY.
jimbarstow Posted March 29, 2014 Author Posted March 29, 2014 Perhaps I misunderstand something, but when I read "I can turn it on and off manually via the ISY interface but I get a complaint that it can't communicate", it makes me think that the command is getting TO the device, but the acknowledgement is not getting back to the ISY. That is my understanding. It is working ok to turn off/on but the isy can't read its status
jimbarstow Posted March 29, 2014 Author Posted March 29, 2014 Or...the device DID answer, but the ISY could not hear it. What devices do you have plugged into the same outlet or circuit as the PLM? Keep in mind that it worked perfectly until I added another on/off module. It continues to fail when I remove the new module, also.
LeeG Posted March 29, 2014 Posted March 29, 2014 I can only evaluate what is happening now. From the previous event trace the Direct On receives an ACK with a Hops Left=2. This is as good as comm gets Thu 03/27/2014 08:15:40 PM : [iNST-TX-I1 ] 02 62 27 DA 5D 0F 11 FF Thu 03/27/2014 08:15:40 PM : [iNST-ACK ] 02 62 27.DA.5D 0F 11 FF 06 LTONRR (FF) Thu 03/27/2014 08:15:41 PM : [iNST-SRX ] 02 50 27.DA.5D 2A.A1.0F 2B 11 FF LTONRR (FF) Thu 03/27/2014 08:15:41 PM : [std-Direct Ack] 27.DA.5D-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/27/2014 08:15:41 PM : [ 27 DA 5D 1] ST 255 The Direct Off command receives NO 02 50 response from the device which is why the ERR 1. Thu 03/27/2014 08:15:48 PM : [iNST-TX-I1 ] 02 62 27 DA 5D 0F 13 00 Thu 03/27/2014 08:15:48 PM : [iNST-ACK ] 02 62 27.DA.5D 0F 13 00 06 LTOFFRR(00) Thu 03/27/2014 08:15:52 PM : [ 27 DA 5D 1] ERR 1
oberkc Posted March 29, 2014 Posted March 29, 2014 Keep in mind that it worked perfectly until I added another on/off module. It continues to fail when I remove the new module, also. It is my perceptions from experience that there are often no single cause of communication issues. Perhaps, before, comms were marginal but servicable. Perhaps something (like a CFL bulb) has simply degraded in your house to the point that some communication is now more than insteon can handle. Perhaps it has nothing to do with the new module. Things are often not obvious and isolating these types of problems can be difficult, unfortunately. LeeGs observations are solid, and he is probably right about the comms being generally good. But I would not totally discount the possibility that you have something around your PLM that is causing it to be a little hard of hearing. One of the obvious places many put their PLM is near the computer systems, which can be full of devices and power supplies that make it hard on the insteon signals to get through.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.