From my limited knowledge of Z-Wave, your battery devices are supposed to work in 3 ways:
- Detect motion, sent report of motion.
- Initiate countdown of n-second, as defined in their configuration. Zooz goes with 15 seconds by default. Their output then depends on how the countdown resolves.
a. Was motion detected within the time frame? If yes, restart countdown, don’t send report (status remains the same, i.e. “active”).
b. If no motion was detected, stop countdown, activate Z-Wave radio, proceed to step 3; meanwhile, do computery things like looping.
- Report change in status being no motion (i.e. cleared), go back to step 1.
They do this because otherwise, every motion sensor on your network would send a report every 15 seconds, then there’d be an ACK report too, and possibly additional transmissions with group binding. Do you really need to tell a lightswitch to turn on every 15 seconds, even if it’s already on? More traffic!
I’m thinking your problem lies with some of your devices not properly updating their status. You might want to look at their configuration settings and see if your “motion timeout” window is abnormally long.
When I first paired some of my motion detectors for example, their awake timer defaulted to 0 seconds; endlessly pinging my controller, flooding the network, preventing any other traffic.
Once I forced it back to default (12 hours) I’ve never had a similar problem.