cmccartney Posted July 25, 2014 Posted July 25, 2014 Earlier this week, upon starting the Admin Console, I was greeted with a number of "Cannot communicate with..." error dialog boxes, one for every Insteon device in my system as it turned out! A brief investigation found a red light on my several year old PLM. I followed instructions and unplugged power from the ISY, then unplugged the PLM, waited a moment and plugged in the PLM followed by plugging the power back into the ISY. All appeared OK until I noticed later in the day that some programs were not working. Furhter investigation revealed that while I could turn devices on and off from the Admin Console, the console was not getting updates on the status of any of the devices. E.g., I could turn a device on of off manually but the state in the UI would not change, and any program looking, for instance, for a 'control switched on' did not run. Another ISY/PLM reset, with factory reset of the PLM produced the same symptoms. However, if I right click on a device and select Query, then the UI is updated with the correct status. I ordered a replacement PLM from Smarthome the first day of failure and it is due to arrive today via FedEx. Is there anything else I should do before following the replace PLM procedure in the Wiki?
bpwwer Posted July 25, 2014 Posted July 25, 2014 Earlier this week, upon starting the Admin Console, I was greeted with a number of "Cannot communicate with..." error dialog boxes, one for every Insteon device in my system as it turned out! A brief investigation found a red light on my several year old PLM. I followed instructions and unplugged power from the ISY, then unplugged the PLM, waited a moment and plugged in the PLM followed by plugging the power back into the ISY. All appeared OK until I noticed later in the day that some programs were not working. Furhter investigation revealed that while I could turn devices on and off from the Admin Console, the console was not getting updates on the status of any of the devices. E.g., I could turn a device on of off manually but the state in the UI would not change, and any program looking, for instance, for a 'control switched on' did not run. Another ISY/PLM reset, with factory reset of the PLM produced the same symptoms. However, if I right click on a device and select Query, then the UI is updated with the correct status. I ordered a replacement PLM from Smarthome the first day of failure and it is due to arrive today via FedEx. Is there anything else I should do before following the replace PLM procedure in the Wiki? Sounds similar to what I just went through. Although my PLM failed less dramatically. It started getting random communication errors with older (mostly Icon) devices. It never completely failed. I follows the instructions on the WIKI with a new PLM and everything went pretty smooth. Turned off updates to battery devices, did the PLM replacement, updated the battery based devices. No more random communication errors. I did make several ISY backups in the couple of days before I got the new PLM just to be sure I had a good backup.
LeeG Posted July 25, 2014 Posted July 25, 2014 The lack of real time Status updates means the PLM has lost its link database. A File | Restore Modem (PLM) will rebuild the PLM link database. The PLM detected an issue and turned the LED Red. Could be a one time issue or the beginning of a permanent PLM failure. I would do a Restore Modem (PLM) as it could have been a powerline issue. If it fails again or the link database will not reload then move to the new PLM.
cmccartney Posted July 25, 2014 Author Posted July 25, 2014 Lee, Thanks for the information. I did a Restore Modem and it seems to be getting status now. Time will tell how long that lasts. I will put the new modem on the shelf when it is delivered later today.
Brian H Posted July 25, 2014 Posted July 25, 2014 Mine died two years and three months after purchase, Right over the warranty period. Mine seemed to just go dead. I powered it down and waited a few minutes. It then again powered up OK. Week later it died again and would only run for a few minutes and die again. There is a thread here. UDI is developing their own PLM and I would expect it to be much more rugged and well built.
cmccartney Posted July 26, 2014 Author Posted July 26, 2014 Thanks, Brian. I have a new one from SmartHome on the shelf and am aware, and waiting for, a UDI manufactured replacement eventually.
Xathros Posted July 28, 2014 Posted July 28, 2014 Brian- Didn't you repair your failed PLM? How did it hold up after the repair? -Xathros
Brian H Posted July 28, 2014 Posted July 28, 2014 Yes I did get the power supply running again and I burned it in for a few weeks. I didn't put it back in service as my main ISY994i connection to the outside world. I did use BusyRats PLM test program and do some testing. So It may not be 100% cured but I know the +12 volts {usually closer to 20 volts} is not just under 5 volts into the 5 volt logic supply regulator.
SteinyD Posted July 30, 2014 Posted July 30, 2014 Could a failing PLM also be the cause of wrong states on keypadlincs? In other words, the lights are off but the light on the keypad button is on? I see the same wrong states in MobiLinc. Or, is this crappy programming on my part and not related to a potential failing PLM?
Xathros Posted July 30, 2014 Posted July 30, 2014 SteinyD- A failing PLM could certainly be a cause but there are so many other possibilities as well. Post the related programs along with a description of the actions that cause the undesired result and we can start the investigation with that. -Xathros
LeeG Posted July 30, 2014 Posted July 30, 2014 Is that the load control button on the KPL (ON for 6 button or Main A for 8 button) or a Secondary button. Also note that a failing PLM would not be limited to wrong KPL button states. Xathros will be able to determine if the Program logic as at fault. Hard to find a better analysis.
SteinyD Posted July 31, 2014 Posted July 31, 2014 Honestly, my use of ISY is quite simple. I have many insteon devices in my home but my use of the ISY is quite simplistic, limited to many scenes and controller / responder setups. The only programs I have turn lights on and off at a couple different times of the night / morning. With that said, I have keypadlincs all over the house. I have many common buttons that control the same lights. It is likely the lack of logic or missing configuration on my part as to how the backlight state of the keypadlinc buttons represent the state of the lights. This incorrect state is then reflected in Mobilinc. I may have a button on 4 keypadlincs that have the ability to be controllers for the same devices. Thanks for the offer of assistance! I'm happy to take this conversation to another thread as to not derail this one if my issue is not PLM related. SteinyD- A failing PLM could certainly be a cause but there are so many other possibilities as well. Post the related programs along with a description of the actions that cause the undesired result and we can start the investigation with that. -Xathros
LeeG Posted July 31, 2014 Posted July 31, 2014 The thing that is helpful is that Backlight levels are not used to turn On/Off KPL button LEDs. Changing the Backlight level affects all the KPL buttons.
Xathros Posted July 31, 2014 Posted July 31, 2014 From the sound of it, you are only using scenes. Scenes create links between the devices and if done correctly, will keep things in sync as long as there are no communications problems on your insteon network. Were things working and problems recently developed? This would indicate that the scenes were created properly and something has changed to prevent them from working. Have they never worked the way you want? -Xathros
Recommended Posts
Archived
This topic is now archived and is closed to further replies.