jsandlin

Upgraded to 2.8.12 from 2.8.11 and lost all communication with the ISY. Power cycled several times with no luck. Did a reset still no communication? Finally held the reset button for two reset cycles and could get back in. The about page said 2.8.12 but everything else was back to factory. It was getting late so I reinstalled 2.8.11 and restored from a backup. It is now back up and running as before. I have installed every firmware for about the last two years and this was the first one, other than the certificate problem in 2.8.9 that has given any problem. I am back up and running so it was no problem just wanted to let you know that I also had a problem.

There seem to be some changes to the way dusk/dawn and motion sensor react in version 2.8.9. There is no status until the first cycle. Before it seems that there was always a value and if not the query device would put a value in. I understand that the battery devices can’t be queried but at least there was a value. With 22 motion sensors, some in rooms that are only occupied once a week or so it creates a problem with some of the programs after every reboot of the ISY. Is there any way to put the last value in after the reboot even if it is not the correct value it would be better that no value?

After trying to upgrade to the latest firmware 2.8.9 I now have a couple problems. I have downloaded and reloaded version 2.8.9 four times on 2 different machines Windows XP and Windows 7 clearing the cache each time. Each time it comes up with version 2.8.8 in the about box. Tried to clear the Universal Device certificates from the Java control panel with no luck. Both my machines are 32 bit Now the statuses of all my motion sensors and dusk/dawn sensors have no value until they trigger. I thought at one time I could query the device and it would put a status in. When I query a sensor now there is no action (small icon in the status box for a few seconds) like before. Internet access was disabled and now can’t be enabled. I then dropped back to 2.8.7 and powered down the PLM and ISY and still have the problems. Any help would be appreciated. Thanks Jim

Thanks for all the replies. I suspected that the older sensors did not support occupancy mode but I wanted to hear it from someone that knew for sure. That program is what I was looking for.

I am trying to come up with a simple program to control a light with a motion sensor.What I would like to do is turn the light on when you enter the room and turn it off 10 after the last movement The first one I tried is: control motion sensor is switched on and status light is off then set light on else wait 10 minutes set light off This works somewhat but if there is only one on from the motion sensor it never gets to the else so the light stays on. The next attempt was to try it with two programs: control motion sensor is switched on and status of light is off then set light on control motion sensor is switched on then wait 10 minutes set light off This one will not reset the timer if there is continuous movement and the lights go off while there is still movement in the room. I have set the motion sensors to send an on command when ever there is movement that seems to help but the light still go out sometimes. Any help would be appreciated. One more observation this seems to happen more with the older motion sensors than the newer ones. Dose anybody know if the older sensors support the on commands when ever movement is sensed