Hi

 

I just upgraded both my isy and admin software to version 4.6.2 from 4.5.4. The upgrade went fine except, now nothing shows up in the current state window for any of my motion sensors. They are the old version 2842-222 and have been and still are working fine. However since no status appears, my programs using the status field no longer work.

 

Does anyone have an idea what might be wrong?

 

As an aside, I also bought a new sensor, the 2844-222. I was able to add it using the device type for the old ones. It's state window also shows up blank.

 

Thanks 

Hi

 

I just upgraded both my isy and admin software to version 4.6.2 from 4.5.4. The upgrade went fine except, now nothing shows up in the current state window for any of my motion sensors. They are the old version 2842-222 and have been and still are working fine. However since no status appears, my programs using the status field no longer work.

 

Does anyone have an idea what might be wrong?

 

As an aside, I also bought a new sensor, the 2844-222. I was able to add it using the device type for the old ones. It's state window also shows up blank.

 

Thanks

This a normal effect. ISY wakes up knowing nothing of device statuses until they report in the first time.

 

Walk through all the zones and test them.

 

Sent from my SGH-I257M using Tapatalk

I should have been more clear. I did the upgrade Thursday. The motion sensors are detecting motion. I can also still change their configuration, if I hold the set button. It just that their status no longer shows up in the ISY admin console. Could it be a PLM problem? Should I try restoring it?

 

Thanks

Before doing that, pick one MS, put it in linking mode and then use Restore Device for it from the console. Retry it a motion test.

 

Paul

Does your ISY detect all of your other devices?

Also, battery power devices show a blank state until they're activated normally for the first time.

just a followup for anyone interested. It was a corrupt PLM. I restored it and the motion sensors are working as expected.

 

Steve

just a followup for anyone interested. It was a corrupt PLM. I restored it and the motion sensors are working as expected.

 

Steve

That's good and it's bad too. It could be an indicator of a failing PLM.

Edited October 9, 20178 yr by larryllix