flemingmike Posted August 28, 2012 Posted August 28, 2012 after I upgraded to pro, my isy can no longer work with my morninglinc. some programs are starting to act weird also. I have a program that checks the status of lights, then turns on a scene if any of them are on. this is working about 20% of the time. any ideas?
Michel Kohanim Posted August 29, 2012 Posted August 29, 2012 Hello flemingmike, Pro and non-Pro version use the the same exact code base and thus I really do not think the problem is related to the upgrade. What happens if you unplug the PLM and then plug it back in? With kind regards, Michel
flemingmike Posted August 29, 2012 Author Posted August 29, 2012 I tried a restore device on my morninglinc and it has been running now for 2 hours in an endless loop.
LeeG Posted August 29, 2012 Posted August 29, 2012 That is what happens when the MorningLinc has lost its authorization link that identifies the ISY PLM as a device allowed to interface with the MorningLinc. The commands being used to interface with the MorningLinc are being echoed back from the MorningLinc with invalid cmd2 values because the PLM is no longer authorized to interface with the MorningLinc. That is why I asked if the PLM had changed. Unplug the MorningLinc to cause a permanent no response error. Then delete the MorningLinc and add it back following the Wiki instructions exactly. I recommend doing a factory reset of the MorningLinc before adding it back. This will clear the MorningLinc link database so the ISY starts with a clean device. The factory reset does not erase the link between the MorningLinc and the lockset as that information is maintained in the lockset itself.
Recommended Posts