lilyoyo1 Posted September 26, 2022 Posted September 26, 2022 7 hours ago, atmarosi said: How do I correct this....? Factory reset the switch. Then right click on the device in the admin console and restore 2
hart2hart Posted September 26, 2022 Posted September 26, 2022 Something went wrong with you original PLM restore PLM. It only takes that one step and then a lot of device updating occurs. My only guess is you had device writes turned off but that’s just a guess. I’d open a ticket wit UDI. .
atmarosi Posted September 26, 2022 Author Posted September 26, 2022 Opening ticket with UDI.. Thanks ya'll!
kclenden Posted September 28, 2022 Posted September 28, 2022 (edited) On 9/25/2022 at 11:35 PM, atmarosi said: How do I correct this....? You don't. That actually doesn't show a problem. The only difference between the rows is that one has "EA" and the other has "E2". They're effectively the same thing. You see when the original link was created, it was "E2", but as the devices are used they detect whether there are communication issues and adjust the second part of the byte accordingly. The ISY "Compare" function doesn't take this into account and reports as mismatch (which there is) but it's not a mismatch that matters. That most certainly isn't the cause of your scene issues. The cause is that there isn't an "E2" record for your PLM. Since the ISY copy of the device Links Table also doesn't have an "E2" record, using "Restore Device" isn't going to solve your problem. When UD looks at the mismatch issue, which isn't really a problem, ask them about the missing "E2" record for your PLM. As far as I know, the only way to fix that will be to relink your switch to your PLM. Edited September 28, 2022 by kclenden 2
Recommended Posts