dpfrez Posted January 22, 2017 Share Posted January 22, 2017 Oh the horror.... I've been pulling my hair out for months trying to determine the cause of my comm issues and things seem to be only getting worse. Like many threads in this topic, things seemed to be pointed towards a PLM failure. Devices would not respond to ISY commands and would become unavailable. It was random and they would typically come back over time. A power cylce of the PLM and ISY seemed to resolve things for a day or two. At this point, I cannot tell whether I was fighting a noise issue that has now manifested into something larger due to all the things I have tried or if it is something different. - Replaced PLM twice, first time with a 2.1 I had on hand, second one just recently 2.2 off Amazon. - The replacement of the 2.1 went fine and things operated without flaw for about 2 days, which was typical for a power cycle, then started getting spottly comms - Tried shutting off all kinds of breakers in the house to determine if there was something interfering, no luck ended up finding that the RX light on the ISY doesn't even flash when you toggle an insteon device within 5 ft of it. Whats really strange is if I put the old PLM on the ISY, toggle the device the RX light, lights up. I'd be quick to point to the new PLM being the problem but I am starting to suspect the ISY. I went to restore the 2.1 unit back on the ISY, it went through the motions although it didn't seem to program nearly all the devices light it normally does (restore process was too short). Now the RX light on the ISY with the 2.1 unit doesn't light when a device is toggled either? I swear it did before??? The PLM restore didn't seem to go very well. Trying a Device restore as we speak and that seems to be taking so far. What does it mean when you don't see an RX light on the ISY when devices are surely sending data over the air and line? Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 22, 2017 Share Posted January 22, 2017 Hi dpfrez, I am so very sorry to hear. Frist of all - and if you have a good backup - I strongly recommend Restore Devices (http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices). Above and beyond PLM: 1. If you have any INSTEON thermostats, unplug them 2. If your PLM is plugged into an outlet that's shared by other transformers/power supplies, move to a different outlet With kind regards, Michel Link to comment Share on other sites More sharing options...
dpfrez Posted January 23, 2017 Author Share Posted January 23, 2017 Michel, thanks for the help. Did the full restore. Things are looking a little better, but they normally do, I'll watch it. One ongoing problem I have right now is the 8-way and IO devices which have status only, no longer show status. The 8-way switch responds to commands to change the switch channel (1) but the status will not display on the other channels. (2- Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 23, 2017 Share Posted January 23, 2017 Hi dpfrez, I am glad to hear. With regards to IOLinc, is it the relay or sensor? With regards to your KPL, do a factory reset on it and then right mouse click | Restore Device. If that also fails, remove it from ISY and then link it back. If that also fails, I suspect it to be a bad switch. With kind regards, Michel Link to comment Share on other sites More sharing options...
dpfrez Posted January 23, 2017 Author Share Posted January 23, 2017 IOLinc ==> its the sensor, relays are responding. KPL ==> did a link compare and found that the PLM was missing from the table. Factory reset the PLM and the status is back showing on the GUI but ISY is not seeing the updates without a query refresh. Thinking the PLM doesn't have a responder link back to the KPL? There is definitely a lot of missing links in the PLM. Restore PLM doesn't seem to do anything. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 24, 2017 Share Posted January 24, 2017 Hi dpfrez , Most probably you/someone has either done a Restore PLM on a dead PLM or Delete Modem. The only solution is to find a good backup and do a restore devices: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices With kind regards, Michel Link to comment Share on other sites More sharing options...
dpfrez Posted January 26, 2017 Author Share Posted January 26, 2017 No delete modem was done. It's possible on of my restores failed. I ran a backup and got things back to a fairly normal state. Since then, I added 3 range extenders, one right behind the PLM, and two close to my power panels. Ensuring at least one was on the second phase. I also added noise filters on some electronic devices in the house. Unfortunately, I'm back to where I started. A restart of the ISY and PLM seem to allow things to run smoothly, and things have started to go back to orginal comm issues. The ISY sends commands but the device does not respond. Here's some events from me toggling the on/off in the ISY for a device: Thu 01/26/2017 07:20:30 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:20:32 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:20:35 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:20:37 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:20:39 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:20:40 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:20:41 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:20:41 AM : [iNST-ACK ] 02 62 3D.E1.B4 0F 13 00 06 LTOFFRR(00) Thu 01/26/2017 07:20:45 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:20:47 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:20:48 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:20:48 AM : [iNST-ACK ] 02 62 3D.E1.B4 0F 11 00 06 LTONRR (00) Thu 01/26/2017 07:20:48 AM : [iNST-ACK ] 02 62 3D.E1.B4 0F 11 00 06 LTONRR (00): Duplicate or ACK for a different device Thu 01/26/2017 07:20:50 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:20:52 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:20:53 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:15 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:16 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:17 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:19 AM : [iNST-SRX ] 02 50 40.D4.7D 00.00.09 CF 13 00 LTOFFRR(00) Thu 01/26/2017 07:21:19 AM : [std-Group ] 40.D4.7D-->Group=9, Max Hops=3, Hops Left=3 Thu 01/26/2017 07:21:19 AM : [D2D EVENT ] Event [40 D4 7D 9] [DOF] [0] uom=0 prec=-1 Thu 01/26/2017 07:21:19 AM : [ 40 D4 7D 9] DOF 0 Thu 01/26/2017 07:21:19 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:20 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:22 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:23 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:23 AM : [iNST-ACK ] 02 62 3D.E1.B4 0F 13 00 06 LTOFFRR(00) Thu 01/26/2017 07:21:25 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:26 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:27 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:28 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:30 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:31 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:32 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:33 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:34 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:35 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:36 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:37 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:38 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:39 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:41 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:42 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:44 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:46 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:48 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 Thu 01/26/2017 07:21:50 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 13 00 Thu 01/26/2017 07:21:50 AM : [iNST-ACK ] 02 62 3D.E1.B4 0F 13 00 06 LTOFFRR(00) Thu 01/26/2017 07:21:50 AM : [iNST-ACK ] 02 62 3D.E1.B4 0F 13 00 06 LTOFFRR(00): Duplicate or ACK for a different device Thu 01/26/2017 07:21:53 AM : [iNST-TX-I1 ] 02 62 3D E1 B4 0F 11 00 I also attached a large log. ISY-Events-Log.v4.5.4__Thu 2017.01.26 07.39.19 AM.txt Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 26, 2017 Share Posted January 26, 2017 Hi dpfrez, Unfortunately I think your PLM is dead: every INST-TX must follow INST-ACK (from the PLM). It does not. With kind regards, Michel Link to comment Share on other sites More sharing options...
dpfrez Posted January 26, 2017 Author Share Posted January 26, 2017 Thanks for the reply Michel. I've scoured the forum in hopes to help me resolve this and found that particular response "your PLM is dead" seems to be pretty high up there in the top responses to why someone has comm issues like this. I've replaced my PLM three times, which caused some of my other issues along the way becuase the comm issues persisted during device restores. I think I may be onto something here and will post later on what I find. It's not the PLM. Link to comment Share on other sites More sharing options...
dpfrez Posted January 26, 2017 Author Share Posted January 26, 2017 Ok, 99% sure I have found the problem. This appears to be a classic Clark Griswold christmas light type issue. My daughters room has a light fixture: Which I installed these LED bulbs: More specifically, its a LOHAS LED E12 6W Dimmable bulb As my frustration culminated not unlike our friend Clark seen below, I started flipping breakers in the the house and testing the comm issue. Sure enough, I found one breaker which when off would permit the comms to flow normally, and on would not. Of all places to suspect, I never would have thought it was there. It was pretty easy to find the source as she didn't have anything electric plugged in. Took my laptop over and sure enough, light switch on, comm issues, light switch off, not issues. You can only imagine what kind of troubleshooting problem this was, I'd be working along, she'd go turn on her lights (unbeknownst to me) and the ISY wouldn't be able to communicate. | | | | | | | | | | | | | | | | | | Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 27, 2017 Share Posted January 27, 2017 Hi dpfrez, That's excellent news and thanks so very much for sharing it. This said, as much as I want to declare victory, experience tells me to be more cautious (when you don't get ACK, it's the firmware in the PLM that's not sending the ACK). So, please keep an eye and keep us posted. With kind regards, Michel Link to comment Share on other sites More sharing options...
dpfrez Posted January 28, 2017 Author Share Posted January 28, 2017 as much as I want to declare victory, experience tells me to be more cautious (when you don't get ACK, it's the firmware in the PLM that's not sending the ACK). I'll have to disagree that its the firmware on the PLM. One reason is, I had similar results with multiple PLM's. The other reason is the very consistent correlation with the LED lights mentioned above being on and the comm issues occurring. Given your skepticism, I videoed a demonstration of the issue to prove it: https://drive.google.com/open?id=0B0qg83tehhnrYlotVGhuTlhjTGs Also, for those wondering, here are the replacement LED's that seemed to work just fine with the PLM: Link to comment Share on other sites More sharing options...
MWoods329 Posted January 29, 2017 Share Posted January 29, 2017 Ok, 99% sure I have found the problem. This appears to be a classic Clark Griswold christmas light type issue. My daughters room has a light fixture: Which I installed these LED bulbs: More specifically, its a LOHAS LED E12 6W Dimmable bulb As my frustration culminated not unlike our friend Clark seen below, I started flipping breakers in the the house and testing the comm issue. Sure enough, I found one breaker which when off would permit the comms to flow normally, and on would not. Of all places to suspect, I never would have thought it was there. It was pretty easy to find the source as she didn't have anything electric plugged in. Took my laptop over and sure enough, light switch on, comm issues, light switch off, not issues. You can only imagine what kind of troubleshooting problem this was, I'd be working along, she'd go turn on her lights (unbeknownst to me) and the ISY wouldn't be able to communicate. | | | | | | | | | | | | | | | | | | Did the light fixture use an Insteon switch?I just bought some of those - want to make sure I don't fall victim to any potential issues with them. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
dpfrez Posted January 31, 2017 Author Share Posted January 31, 2017 Did the light fixture use an Insteon switch? I just bought some of those - want to make sure I don't fall victim to any potential issues with them. Sent from my iPhone using Tapatalk No it was a standard wall switch, would be interesting to know what that would have done but I suspect it would have behaved the same. To be clear, the issue was with the LED bulb not a problem with any Insteon device other than the Insteon PLM's incapability with the LED bulb. Link to comment Share on other sites More sharing options...
stusviews Posted January 31, 2017 Share Posted January 31, 2017 The problem may have been due to Insteon signals, but I doubt that the PLM was the cause. Link to comment Share on other sites More sharing options...
dpfrez Posted January 31, 2017 Author Share Posted January 31, 2017 The problem may have been due to Insteon signals, but I doubt that the PLM was the cause. The PLM wasn't the cause, the LED bulbs caused the issue. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.