cyberk Posted November 21, 2015 Posted November 21, 2015 So i tried deleting the device from the ISY and re-adding it...now everything works. We have new links 0 : 0FF8 : A2 00 1C.FC.52 FF 1F 01 1 : 0FF0 : E2 01 1C.FC.52 01 00 01 2 : 0FE8 : 00 00 00.00.00 00 00 00
cyberk Posted November 21, 2015 Posted November 21, 2015 0 : 0FF8 : A2 1D 1C.FC.52 FF 1F 03 1 : 0FF0 : A2 1C 1C.FC.52 00 1F 06 2 : 0FE8 : A2 1B 1C.FC.52 FF 1F 05 3 : 0FE0 : A2 1A 1C.FC.52 FF 1F 04 4 : 0FD8 : A2 00 1C.FC.52 FF 1F 01 5 : 0FD0 : EA 00 1C.FC.52 03 1C 01 6 : 0FC8 : E2 03 14.AA.0D 03 1C 03 7 : 0FC0 : E2 03 1C.FC.52 01 00 03 8 : 0FB8 : E2 04 14.AA.0D 03 1C 04 9 : 0FB0 : E2 04 1C.FC.52 01 00 04 10 : 0FA8 : E2 05 14.AA.0D 03 1C 05 11 : 0FA0 : E2 05 1C.FC.52 01 00 05 12 : 0F98 : E2 06 14.AA.0D 03 1C 06 13 : 0F90 : E2 06 1C.FC.52 01 00 06 14 : 0F88 : A2 1D 1C.FC.52 00 1F 05 15 : 0F80 : A2 1D 1C.FC.52 00 1F 04 16 : 0F78 : A2 1D 1C.FC.52 00 1F 06 17 : 0F70 : A2 1A 1C.FC.52 00 1F 06 18 : 0F68 : A2 1A 1C.FC.52 00 1F 05 19 : 0F60 : A2 1A 1C.FC.52 00 1F 03 20 : 0F58 : A2 1B 1C.FC.52 00 1F 06 21 : 0F50 : A2 1B 1C.FC.52 00 1F 04 22 : 0F48 : A2 1B 1C.FC.52 00 1F 03 23 : 0F40 : A2 1C 1C.FC.52 00 1F 03 24 : 0F38 : A2 1C 1C.FC.52 00 1F 05 25 : 0F30 : A2 1C 1C.FC.52 00 1F 04 26 : 0F28 : 00 00 00.00.00 00 00 00
LeeG Posted November 21, 2015 Posted November 21, 2015 Post #25 has no Controller link back to the PLM. That indicates a PLM was Deleted Post # 26 corrects the problem because the PLM is now known to the ISY. If there are other devices not reporting state changes do a Show Device Links Table and look for E2 xx 1C.FC.52 .. .. .. Likely they do not have the required Controller link(s) unless there is a comm issue.
cyberk Posted November 21, 2015 Posted November 21, 2015 Thanks LeeG, is there any way to correct the link without deleting/re-adding the device?
LeeG Posted November 21, 2015 Posted November 21, 2015 Do a Show ISY Links Table for the device in question. If it has the E2 ... 1C.FC.52 ........ link(s) a simple Restore Device should fix the issue. If not in the ISY Link Table a restore of a current ISY Backup taken before a PLM was Deleted followed by a File | Restore Devices.
cyberk Posted November 22, 2015 Posted November 22, 2015 What I find weird is that I've never deleted a PLM. For the case of the switch, both the ISY and the device showed the same links, I'm guessing that's why a restore didn't fix the problem. One would think the ISY could repair missing links?
LeeG Posted November 22, 2015 Posted November 22, 2015 The device did not have the link back to the PLM 0 : 0FF8 : A2 00 1C.FC.52 FF 1F 01 1 : 0FF0 : E2 01 1C.FC.52 01 00 01 - this link was missing from device and from the ISY link information. 2 : 0FE8 : 00 00 00.00.00 00 00 00 The only way I have seen this happen is to click on File | Delete Modem (PLM) which removes the PLM Controller information from the devices and the ISY link data. That is why a Restore Device does not fix the issue because the ISY was told to remove the PLM. The Delele Modem and Restore Modem functions are next to each other so an accidental click on the wrong function will cause this. Perhaps there is some combination of Safe Mode where ISY cannot communicate with PLM and Restore Modem has the same result but I have not seen that. When moving to a new PLM the ISY and PLM need to be powered down, bring power on new PLM first, then powering up ISY. If the ISY is not powered down it is not aware the PLM has been replaced.
larryllix Posted November 22, 2015 Posted November 22, 2015 We seem to be seeing a few of these "never deleted the PLM" reports over the last while. Is there a confirmation of action input for this ISY command? If not, perhaps this should be added in a future version by UDI. I don't want to test it.
Brian H Posted November 22, 2015 Posted November 22, 2015 When delete Modem is chosen. There is a big RED Print warning screen about the consequences of continuing. A cancel or continue input is required before anything further happens.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.