I have created the Zone Controller and switch the SL to use this sensor. In the Zone Configuration options I am not certain what value I should use for the "Activity Timeout" . I entered 5 seconds but think I may want it at "no selection". Doing a test walking past the motion the lights both turned on/off but it also worked this way with the other configuration. I am attaching the log for the zone device which still shows multiple reports but not as bad as before. The real test will come in the morning.
I also use Zen26 and Zen27 with Zooz ZSE40. The thing works from time to time and sometimes my light doesn't even turn on. I heard the switch click but no light. However, if I press the switch physically or use the device page, the switch works without a problem. I've been working with Zooz but they are running out of ideas and want me to contact Hubitat. I am using the Motion Lighting app as well.
Well, there goes my guess--looks like that won't help. I'm still not sure that "debouncing" will solve the problem because I'm really not sure what could be causing it, but I figured it couldn't hurt, and if this lessens the incendence of that, then I guess it's not bad, either. To really make it not double-report, there's probably a way to manually do this with a Rule instead of a Zone Motion Controller (trigger on motion changed and use a local variable [but not the built-in private boolean] to track whether it's already beomce active, and manipulate a virtual sensor with custom actions accordingly), but I'm not sure if that effort would be worth it considering this whole thing is just a guess on my part since everything else looks right.
Well there's nothing wrong with the switch then.
Apps use the same commands that get executed from the device page...
Is it somehow possible the switch is getting turned on, then off again immediately by the automation?
On my configuration there is only one automation at the time that the senor is supposed to turn on the lights. Since the lights turn on manually and with a time based automation, and the sensor shows going active/inactive in the logs, it seems that something is not working with HE. I have the same issue using RM and also SL.
I have been on contact with Zooz support on this issue and they have acknowledged the issue. Response from Zooz support:
"I looked into this further, and it turns out that we've seen this issue before with other ZEN26s where they're not working well in sensor automations on Hubitat. We've verified this is a Hubitat issue and they'll be addressing this in the next firmware update. We will follow up with them regarding an update for the new firmware."
I hope that Hubitat responds and comes up with an update soon.
This is news to me, both the issue and and an update to fix said issue...
I have the latest version of Hubitat installed 2.1.5.124 and it still records multiple events being recorded each time the sensor goes active/inactive. The log file attached shows this. It is the multiple events occurring that is causing the switch not to turn on.
We will have a fix for the motion sensor double reporting in 2.1.6 via a preference setting, however we can't fix a switch that crashes when multiple commands are sent to it too quickly, this is the real reason that it's not turning on all the time...
Anyone else still having this issue after the last firmware update? Zen26/27 and zse40 using motion lighting app. Reboot seems to clear it up for a bit.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
