My zooz 4 in 1 seems to get stuck in a motion active/inactive state. It is random if I get each event on the device. I see the led flash for each motion event. is there any way I can confirm the Z-wave signal is getting through?
Craig
My zooz 4 in 1 seems to get stuck in a motion active/inactive state. It is random if I get each event on the device. I see the led flash for each motion event. is there any way I can confirm the Z-wave signal is getting through?
Craig
I experience the same, with Zooz. I have 4 of them.
Instead of Logs, look at device events from the device page.
What am I missing? It doesn't seem stuck based on that. It's sending both events, with inactive a variable number of seconds after active --> which is to be expected.
What makes you think it's stuck?
The logs show that those events are coming into the hub from the device.
You aren't seeing all of the times I triggered the sensor that happened. Note the 6 min since it went active, there has been no motion
Does that help?
Craig
OK, that helps.
and it is random, which I am sure makes it the easiest to troubleshoot
I have been experiencing similar issues with my two 4-in-1 sensors as well. Started after the 1.1.5 update.
We made an adjustment to the driver, which should be out in a hot fix tomorrow that should resolve this.
Awesome!
Oh that is so cool!
I played with this device a little yesterday, like 5 minutes. I can't say I would place it within my top 5 list of sensors to deploy.
I'm not slamming it by any means, but it is a little pokey, there are certainly faster motion sensors out there, and I'm not in love with their lux implementation.
The various firmwares in the wild, and their somewhat arbitrary motion timeout scale changes makes setting these up confusing as well.
Agreed, totally! I use them as backup motion, over bathroom showers, because for battery powered multi sensors, they have a pretty good humidity setup. Their lux setup is just silly. Why forgo a standard like that?
If you have a top choice temp and motion, Iโd be interested. Smatthings killed me with their battery type changing every sensor. I am trying to figure out which sensors to โstandardizeโ on.
Not following this?
Z-Wave fans aren't going to like to hear this, but virtually every Zigbee motion sensor includes temp, and all of them are consistent in their motion active response times.
They can vary in their timeouts, but generally they are in the 15 to 30 second range.
Personally I use Lows Iris (I probably have 20 of these), NYCE, all of which include humidity and temp. I also have many coin cell ST motions, and the original gigantic centralites , the coins are EOL, and almost my least favorite, the gigantic centralites are indestructible.
The least favorite being the Bosch, but that's an aesthetic call, not a functional one.
The hue motion is problematic, not recommended.
I have one of the new Samsung manufactured motions as well, no complaints on this sensor, it has nice mounting features and a good price point.
My final plug for Zigbee battery devices in general being Zigbee doesn't sleep the same way that Z-Wave does. Zigbee doesn't have a wakeup interval setting, devices are supposed to check their parent every 7 seconds at most for any commands.
So there is no stumbling around the house poking these things if you need to make configuration changes.
A side effect of this being drivers are less complicated and therefore more reliable since there is no need to track and Q pending configuration commands ect.
Zigbee includes, out of the box payload encryption roughly equal to Z-Waves S0 security, without the additional packet exchange overhead involved with S0.
The only down side to Zigbee being the 2.4G RF spectrum it uses, it doesn't have the range of 900M, and your WIFI can seriously mess with it if you don't plan properly.
I already run Keen vents, so I have the zigbee solved. I saw others have a mount for the Iris, so that might be an option.
Thanks!
The release seemed to help a little. But I'm still having trouble with them getting motion active and HE not picking up the inactive report.
can you wake it up, then hit configure?