Hi, I'm new to HE migrating from VeraPlus. I set up a zooz 4-in-1 motion sensor and motion events are being generated twice within milliseconds of each other. For example, when motion is detected, the log shows two events. The same thing happens when motion stops. To test if this was simply a 'logging' issue, I installed Pushover for notifications and I set up a rule to notify me on motion detected from this sensor. Not surprising, I get two notifications per event instead of one.
Other non-zooz motion sensors are working correctly.
Are there any known issues with the Zooz 4-in-1 sensor? Anyone experiencing the same behavior?
This device sends 2 types of reports for motion events for some users, but other users only get one report and it's not the same report for all of those users.
To prevent the duplicate events the driver would need to ignore one of those reports, but ignoring either of those reports breaks motion reporting for some users.
Maybe Hubitat can add a setting to the driver that suppresses duplicate events when enabled like they did for the Ecolink Contact Sensor.
^What he said. But another question is: could you work around this issue? I'm not sure how you're setting up your notification, but in the built-in Notifications app, you can use the "Only once within this number of minutes" option to eliminate the double-notifications. If your sensor is set to a 1-minute (or longer) timeout, this wouldn't really change anything, but if you want to reduce the time further, you could do one of a couple things with Rule Machine (either do the notification there and prevent it from firing multiple times within a few seconds, say by using the private boolean to restrict it; or "syncing" the Zooz with a separate virtual motion sensor with a similar restriction, with this sensor being the one you'd actually use for automations if this matters for more than just this one app/notification).
Since I just use mine to turn on a light if it's dark, I hadn't really noticed the double events. Has anyone asked Zooz support or @agnes.zooz about this?
The sensor sends 2 types of reports when motion is detected: 1. notification report (to indicate motion to hub) 2. basic set report (to indicate motion to directly associated devices such as light switches). Most motion sensors or contact sensors will send both types of reports but some of them will send basic set to group 2 and not group 1 like the ZSE40. The report is still being sent but it may not be visible in the logs since the hub is always in group 1 of associated devices. So in terms of network traffic, you'll usually get both reports sent out from any type of security sensor like that. But it's not always going to be visible in the logs depending on which association group it's sending it to.
Oh, interesting. I thought I also experienced the "double-report" problem, but mine is really just two "active" events at nearly the same time, usually within a few milliseconds of each other--I assume for the reason Zooz support mentioned above. This is not a continuous string of such events.
On at least the v2 revision of the sensor, you can use parameter 5 to set the motion retrigger interval pretty low (a 1-byte value representing the number of seconds, though supposedly it won't take anything less than 15, which is also the default), so if it's really 15 seconds and not exactly 8, that would explain this problem--but setting this parameter to your desired value would probably be a good idea in any case to see if it helps. (No need to bust out the Basic Z-Wave Tool or anything here; the ZSE40 Hubitat driver lets you configure it to common values out of box.)
It's because the ZSE18 sends basic set to Group 2 and Hubitat as the hub is in Group 1 so it doesn't receive it so it doesn't display it in the log. That's the difference I had mentioned in the above post.
ZSE40 sends both reports to Group 1 so Hubitat displays them both.
But at the end of the day, both devices send the same amount of reports which is in line with the Z-Wave protocol.
Seeing this issue come up on multiple thread posts, I would recommend the possibility of a firmware update that only sends basic set to Group 2 like the ZSE18, for the ZSE40.
Changing the setting in the driver--or more specifically, changing that, clicking Configure, and making sure the device is awake to receive it--does change a setting on the device, not (just) the driver. I was just wondering if it might be the right setting here. Two logs for the same event within milliseconds of each other sounds a lot like the notification vs. basic set Z-Wave issue Zooz support mentioned above; two events multiple seconds apart from each other sounds a lot like just two "active" events that could happen with an extremely low retrigger interval, which this paramater adjusts (but, yes, it's still a bit odd since the docs don't indicate it can be set quite this low).
The device will still send the double report to the log every 8 seconds no matter what setting you want it to retrigger at. All that does is change the timeframe from when that 8 second report changes from active to inactive. It will still send the report every 8 seconds while active, no matter if you set it for 60 seconds/60 minutes
We'll see if we can add another group or a setting to disable basic set reports to minimize the amount of reports shown in the log without having to re-certify the device (which would affect the price of the sensor and nobody wants that).
We'll also try adding a setting to change the interval for active reports sent to the hub while motion is being continuously detected.
We're about to finish another production now so the changes won't be applied for a few months at least but if we have an OTA file for you guys to try, I'll post the news here.
Thank you all for your replies... setting up to notify only once within a number of minutes will do the trick until we see some sort of update from Zooz.
But another question is: could you work around this issue? I'm not sure how you're setting up your notification, but in the built-in Notifications app, you can use the "Only once within this number of minutes" option to eliminate the double-notifications. If your sensor is set to a 1-minute (or longer) timeout, this wouldn't really change anything, but if you want to reduce the time further, you could do one of a couple things with Rule Machine (either do the notification there and prevent it from firing multiple times within a few seconds, say by using the private boolean to restrict it; or "syncing" the Zooz with a separate virtual motion sensor with a similar restriction, with this sensor being the one you'd actually use for automations if this matters for more than just this one app/notification).
