Motion detection no longer working properly

Since the recent upgrade on Vera Lite to 1.7.569 my two Aeon Labs Multisensors have stopped working properly for motion detection
I have two scenes configured for each of these, the first to turn on a light when motion is detected and the second to turn it off when motion stops. Parameter 3 is set to 240 seconds and so I get a 4 minute delay before the lights go off
Now this was all working fine before. As soon as I went passed a sensor the light came on almost immediately and then after 4 minutes it would be turned off
Now when I go passed nothing seems to happen. But what I’ve found is that if I keep out of range and wait for 4 minutes the light will turn on but it won’t go off
So it seems to be a strange coincidence that this just happens to be the motion timeout setting
Anyway, when I check Vera I see that I’m getting alerts in the Dashboard about motion being detected whereas before that only happened if the motion sensors were armed
The mode is set to Home and the scenes only operate in that mode. So thinking the arming may have a problem I changed the mode to Away then back to Home but it made no difference. I then changed the sensors to armed and then back to bypassed but that made no difference. I still get these alerts of motion being detected
Now when I look at the two scenes for a sensor they both have the same time stamp instead of a four minute gap so something has clearing gone wrong here but I’m not sure what
I’ve rebooted Vera, I’ve tried a Z-Wave repair and I’ve pulled the power on the sensors but it makes no difference
Oddly enough I also have a Fibaro motion sensor with two scenes and that’s still working as before
Any thoughts as to what’s causing this problem?

Looks like its a documented error with the latest firmware update and motion detectors (at least Monoprice ones). Probably should send tech support a message to add your motion detectors to the list of sensors that don’t work with the latest firmware (Monoprice and Vision afaik).

The link below shows the error other users see and a crude method of untripping the sensors.

http://forum.micasaverde.com/index.php/topic,31793.msg230737.html

I can confirm that the EzMotion 3-1 and the Aeon 4-1 doesnt work correctly with the latest firmware. I let support know.