Latest release motion zones not working if active when upgrading or rebooting

kahn-hubitat · April 4, 2025, 10:26pm

the built in motion zones code no longer seems to work correctly if the zone was active when you reboot or install an update.. i have a 10 minute cool down and it appears the state is not getting set correctly even on subsequent firing of a included sensor after reboot because it is still seeing the zone as active so does not redo setting it to active and subsequently when one of the include sensors then goes innactive it never resets the motion zone to innactive either.

i have to resave the zone after reboot/install to get it to reset.

@bravenel

bravenel · April 4, 2025, 11:53pm

@mike.maxwell

mike.maxwell · April 5, 2025, 12:23pm

There haven't been any changes in this app in 2.4.1
Can you post the configuration of the specific zone?, not sure if there's anything that can be done about this.

kahn-hubitat · April 5, 2025, 2:04pm

mike.maxwell · April 5, 2025, 5:38pm

I just ran a test of a zone similar to yours
created a zone with two motion sensors, each with their internal 15 second time out.
activated the zone and it went active, installed an update, after reboot checked scheduled jobs in the logs, the zoneOff job was still in the list, waited for the expected execution time and it fired and the zone went inactive.

kahn-hubitat · April 5, 2025, 5:43pm

weird i will try again with a reboot maybe it is only on an install i have a 10 minute timeout.

i think the issue also may be the device in the zone going innactive during the reboot.

mike.maxwell · April 5, 2025, 6:01pm

In that case the device going active should trigger the zoneOff method anew

kahn-hubitat · April 5, 2025, 6:11pm

maybe something else is going on notice here the zone is active..
the sensor that triggered is already innactive..

but there is no scheduled job to retest at the 10 minute cool down time?

kahn-hubitat · April 5, 2025, 6:12pm

notice everything but thqt zone is now innactive but there is no scheduled job for the timeout period

on that zone.

mike.maxwell · April 7, 2025, 4:28pm

If the zone is active (the zoneOff method is scheduled) when the hub is rebooted that method should still be active after reboot.
I verified this. If zoneOff isn't scheduled than after a reboot it still isn't going to be scheduled, I'm unsure what one would expect the app to do after a restart as any motion events that transpired whilst the hub is being rebooted aren't going to be captured

system · April 7, 2026, 4:28pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.