Motion Sensor status does not update after motion time out -- staying tripped

Community Playground General Discussions
1

Anyone seen/fixed this? thanks for the help!

I have had this issue on both 7.0.19b & 7.0.20 (updated today)

For the past month or so, a few motion sensors get ‘stuck’ in tripped (motion detected) mode; even after motion stopped and the motion timeout expires.

I’m NOT getting Device not detected errors and in AltUI is shows the zwave polling to those devices as green… so communication is perfectly fine.

They stay in the motion detected mode until someone walks past them to trigger motion again, then after timeout expires the sensor returns to motion not detected mode.

It has happened a lot in the last few weeks and results in alarms going off and lights not shutting off - and coming back on when manually turned off.

Has happened with two different sensors: Zooz MultiSensor (Zwave+ gen5) and Schlage (Zwave gen4)).

The only Fix is a full Vera reboot (not just a Lua reload). This is not reasonable as it has happened several times a day for the past few weeks.

Even code that should reset the sensor status, which works normally, does not…
function resetSensor (device)
local SECURITY_SENSOR_SERVICE =“urn:micasaverde-com:serviceId:SecuritySensor1”
luup.variable_set (SECURITY_SENSOR_SERVICE, “Tripped”, 0, device)
end

2

can you see a list of the neighbour devices?

go to advanced and variables, there should be neighbours listed.

The only time I have had this issue was with 2 different sensors that were only routed through one other device or straight to the Vera.

Battery sensors tend not to get information from the nightly heal so as you build the network these don’t receive their updates.

I excluded and reincluded the two I had these issues with and after they configured they had many more neighbours.
the problems stopped

3

[quote=“Aaron, post:1, topic:195613”]Anyone seen/fixed this? thanks for the help!

I have had this issue on both 7.0.19b & 7.0.20 (updated today)

For the past month or so, a few motion sensors get ‘stuck’ in tripped (motion detected) mode; even after motion stopped and the motion timeout expires.

I’m NOT getting Device not detected errors and in AltUI is shows the zwave polling to those devices as green… so communication is perfectly fine.

They stay in the motion detected mode until someone walks past them to trigger motion again, then after timeout expires the sensor returns to motion not detected mode.

It has happened a lot in the last few weeks and results in alarms going off and lights not shutting off - and coming back on when manually turned off.

Has happened with two different sensors: Zooz MultiSensor (Zwave+ gen5) and Schlage (Zwave gen4)).

The only Fix is a full Vera reboot (not just a Lua reload). This is not reasonable as it has happened several times a day for the past few weeks.

Even code that should reset the sensor status, which works normally, does not…
function resetSensor (device)
local SECURITY_SENSOR_SERVICE =“urn:micasaverde-com:serviceId:SecuritySensor1”
luup.variable_set (SECURITY_SENSOR_SERVICE, “Tripped”, 0, device)
end[/quote]

Yeah…I’ve noticed the exact same thing… Happens every time you edit a scene, if it is tripped,stays tripped.

4

[quote=“wadesready”][quote=“Aaron, post:1, topic:195613”]Anyone seen/fixed this? thanks for the help!

I have had this issue on both 7.0.19b & 7.0.20 (updated today)

For the past month or so, a few motion sensors get ‘stuck’ in tripped (motion detected) mode; even after motion stopped and the motion timeout expires.

I’m NOT getting Device not detected errors and in AltUI is shows the zwave polling to those devices as green… so communication is perfectly fine.

They stay in the motion detected mode until someone walks past them to trigger motion again, then after timeout expires the sensor returns to motion not detected mode.

It has happened a lot in the last few weeks and results in alarms going off and lights not shutting off - and coming back on when manually turned off.

Has happened with two different sensors: Zooz MultiSensor (Zwave+ gen5) and Schlage (Zwave gen4)).

The only Fix is a full Vera reboot (not just a Lua reload). This is not reasonable as it has happened several times a day for the past few weeks.

Even code that should reset the sensor status, which works normally, does not…
function resetSensor (device)
local SECURITY_SENSOR_SERVICE =“urn:micasaverde-com:serviceId:SecuritySensor1”
luup.variable_set (SECURITY_SENSOR_SERVICE, “Tripped”, 0, device)
end[/quote]

Yeah…I’ve noticed the exact same thing… Happens every time you edit a scene, if it is tripped,stays tripped.[/quote]
Exactly!

Ok, another bug they have not fixed. Fantastic

Sent from my SAMSUNG-SM-G935A using Tapatalk

5

Good to see that it is not only my problem !!!
Thanks.

6

Any updates with this? I just moved all my equipment to a new house and now my 2 Philio 4-in-1 motion/door sensors keep getting stuck on/don’t time out after motion is detected. Shows lots of neighbor devices, so not sure what is going on.

Running a Vera Plus on latest firmware.

7

I am having the same issue.

8

I have this with the latest update on my Veraplus but only with one of my chinese sensors. I have others working perfect though … I generally noticed some stability issues with both my PLEG rules and connectivity to vera servers.

9

I have this issue. What happens is when Vera reboots while the sensor is tripped, it then stays tripped. Vera rebooting is causing this.

10

I disagree. Mine does not reboot when I see this issue. I get notifications anytime mine reboots and can also check the last time it rebooted by itself. When I see the issue it is not rebooting at the time the sensor sticks.