Occupancy V Motion

Why would you use OCCUPANCY v MOTION in a motion detector? Sorry I am new to this stuff but want to understand why you would use one over the other. Any case?

Occupancy is a state that can be triggered by motion and last until no motion was detected for a (often configurable) time. Motion is more an event.

@m0wlheld so each time motion is detected Occupancy state is reset to ON again?

Usually if motion ends, the occupancy timeout countdown starts. If it passes with no motion, occupancy is set off. If motion is noticed while timeout is not done, the timer is resetted and occupancy stays on.

1 Like

You can also have calculated occupancy such as…

If a room has a closed door and motion happens inside the room. Set ‘occupied’ until the door opens again.

You can set the asme sensor occupied from other sensors too such as your phone or a smartwatch and BLE.

Occupancy is a construct based on other sensors. Motion is just motion.

I’m a recent newbie to HA. Do any integrations exist that do the Occupancy as specified by @m0wlheld using only Motion Sensors? Ideally triggering a space as ‘Occupied’ if there are X number of motion activations in Y minutes. Similarly a room is set to ‘Unoccupied’ if there are no longer motion activations after Z minutes.