Zone Motion Controller - didn't wake up in the morning, failing to trigger

[danabw]

@mike.maxwell, appreciate if you can provide advice on this:

Having an issue w/motion zone not triggering in the AM, worked perfectly last night before. Appreciate help w/this - am I missing something? The zone was created recently, can't remember exactly how many days ago. C7 on 2.2.4.158. Sensors are three Iris v2s, and one ST. I'm using the Motion Aggregation option.

There was motion this AM on all of the sensors included in the zone but the zone didn't trigger active at that time.

The Motion Zone:

7:07 AM - The sensors in the MZone are triggered, but the MZone doesn't trigger for some reason:

7:18 AM - The MZone finally triggers, but it's not triggering "Active" - it's triggering "Inactive" without first showing active this morning when I came out at 7:07, or later when there were more motion events on the motion sensors in the motion zone:

From the time I came out this AM at 7:07 until 7:18 when the MZone triggered inactive, there is no "Active" event from the MZone, even though all of the motion sensors included in the MZone were triggered Active during that time.

Summary

The MZone did trigger active later this morning at 7:42 when I got up to feed the dogs:

All of the sensors are working and trigger normally.

[mike.maxwell]

a zone can't go active if it never went inactive, best to check each device that's part of the zone to verify they all went inactive.
some devices will stay active when their batteries get low...

[danabw]

Thanks, Mike.

All sensors are >60% battery reported.

All of them went active this morning at 7:07 when I came into the room:

An all of them are continuing to consistently move between active/inactive as expected, so there doesn't appear to be any issue with them getting stuck.

Summary

Anything else I can check?

I'll also see how things go tomorrow morning, of course.

[mike.maxwell]

assuming this is a motion aggregation zone, it will go inactive as follows:
The Activity Timeout is started after all motion sensors become inactive.
This virtual zone motion sensor will become inactive when the Activity Timeout expires, and no further motion was detected.
So it should be fairly simple to see how all these events happen in live log history

[danabw]

Yes, you're correct, it is a Motion Aggregation Zone. I'll see what happens tomorrow AM.

[kahn-hubitat]

can you look at the event history on the device page for the zone.. that should show the active inactive.. and see if it is really missing.. could just have missed it in the logs..

[danabw]

Unfortunately the available events on the Device page don't go back far enough.

[danabw]

Hey, Mike. It does seem like the zone motion controller is not going active when it should this morning. Log entries from this AM from the motion zone and the motion sensors that are included in the motion zone.

Motion sensors:

They show multiple active states, but the motion zone only became active once this AM, at 7:30:

Logs:

Motion zone Device page events:

But motion sensors in the motion zone became active serveral other times and the motion zone didn't activate:

The activity time-out on the motion zone is one minute:

Am I doing something wrong, misunderstanding how this works, or is my setup of the motion zone incorrect, or ?

[mike.maxwell]

the zone cannot go active, until all the members have gone inactive, and the zone times out and goes inactive.
If the zone is already active, further active events from it's members will not generate additional active events for the zone.

[danabw]

Thanks. I'll play around w/this some more.

[mike.maxwell]

@danabw

I'll play around w/this some more.

maybe build your self a test zone using two virtual motion detectors to simplify playing around with it.

[danabw]

Great minds, I just pulled out two motion sensors to add to my mesh to use just for that purpose.

[mike.maxwell]

@danabw

I just pulled out two motion sensors to add to my mesh

not real ones, use virtual ones...

[danabw]

Ah yes, I frequently forget about that (easier) option. I have a couple that I created for some previous testing. Will put them back to work - they shouldn't complain, they've been resting unused for weeks.