Jump to content

problems after upgrade to pro.


flemingmike

Recommended Posts

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.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...