Approximately 10 minutes ago, I replaced the battery in the sensor. Ever since I did, HE7 shows the sensor as active but its in a closet with the door closed. I've even walked in to active it but after the timeout (15 seconds), it still shows "active" in HE. Anyone know how to "reset" this motion sensor in HE?
If you can, try putting in near the hub for a few minutes. Maybe it is having a problem finding a route. If it starts working near the hub move it back and just give it a little time to work out its routes.
I'll give that a try... what is confusing is it was working prior to the battery replacement and it was returned to its original location after the replacement.
Yeah it should have just kept on going. I have pulled the batteries on mine and they work again right after putting them back in.
Did you try forcing a wake up by pressing the zwave button with a paperclip? That will force it to send some commands out. Depending on what driver you are using you could request a refresh before you wake it up.
1 Like
I'm using the "new" driver but did not think to press the button on the sensor... off to do that now.
Well my problem is not with just one sensor. I also have a Fibaro ZW5 motion sensor. When I walked by it, it activated but now 10 minutes is still showing active motion.
Both of these devices have been working for over a year... the only thing that has changed is the new firmware updates in the past 2 weeks.
Does anyone else have either of these devices? If so, what firmware are you running?
I have (3) Zooz ZSE40 V2 and (1) ZSE40-700, am in beta testing group and running current hub firmware. Have had no issues. I would have noticed because 3 of them I am using the motion for lighting. I am using my custom driver, not the stock one, but id the stock driver is capturing the motion active it should also get the motion clear alert.
- Did you update the zwave firmware (separate process from the hub), and also
- if you have not tried this yet you could power down the hub totally, unplug for about 30s then power it back up. Sometimes that cold boot cycle will clear up mysterious zwave issues.
1 Like
I have 2 ZSE40-700's installed a couple weeks ago, firmware 32.32, on HE v2.3.1.142. I'm testing them for reliability - collecting 100+ data points a day from each - and haven't seen any problems.
Did you upgrade your zwave firmware per this thread? C7 2.3.1 and Z-Wave Firmware 7.17.1 - #66 by bertabcd1234
(Doh! Jeff already asked 
1 Like
Yes, my HE7 is current on both firmware and Z-Wave firmware. I figured out the problem with the Fibaro was a low battery (but for some reason the HE was reporting the battery was 100%). Still unable to get the Zooz 4-in-1 to work or not show as active in HE.
Zooz firmware update? Last idea is hard reset.
Hard Reset Instructions
- Open the battery cover
- Press and release the Z-Wave button with a paperclip 10 times within 10 seconds
Ok after waiting a day (or two), the Zooz is now not stuck on Active and is back to normal operation (yea). But I'm still having a issue with the battery level (HE7 shows it a 1%).
As for updating the firmware on a Zooz device (my device is at v32.2), I've never perform that task on a Zooz device. Can you provide the steps or a link to a document which outlines the steps?
For the battery level, I am not sure when/if the stock driver requests the battery level or if it just waits for the wakeup. My custom driver requests it specifically on wakeup because some of the devices do not report it automatically. If it has already been 24 hours and the battery has not been reported then you might have to try my custom driver to see if it can get it.
Your reported 32.2 is probably actually 32.02 and the subversion is not being padded by the driver properly. For the firmware I have done these with the built in firmware update app. You just hit "add built in app" and you will see it in the list. You need the firmware file from Zooz (Be sure to request 32.12 specifically which is much less chatty). I would use a laptop or tablet and have that along with the device close to the hub. Its pretty straightforward to use but the trick with battery devices is once you select it from the list you need to wake it up right away. Then depending on how long it takes you to select the options and hit the update button you may need to wake it up again so the update can start. Then it can take 15-30 minutes to go through it.
I usually turn on debug logging on the device as well and watch the logs, you can see the firmware update command kick out form the driver in the debugging as unhandled events usually.
1 Like
Much thanks for your suggestions/assistance I've tried 3 batteries and the device is basically dead. This is the 4th Zooz device which has failed or will not work with my HE7. I'm SO done with that brand.
I know that when my Zen34s were spamming the hub with battery reports the batteries would discharge and give very low readings. Updating the device’s firmware mostly fixed this for me (I haven’t had this happen for at least a couple months now). Perhaps something like that was going on with your sensors? I’ve found @agnes.zooz is very responsive to people reporting problems on this forum. Maybe she can help you resolve this?
I'm so sorry to hear about your issue! Have you reported the problem to our support team yet? It sounds like the sensor was working well for you until a recent battery replacement and that you're having issues with at least another device from a different brand so there may be a few factors at play here that require a more in-depth troubleshooting.
Thank you for the tag @Ken_Fraleigh, Agnes is actually a she 
2 Likes
Oops. Sorry. Fixed it.
1 Like
ZSE40 Specs
Full specs aren't in the manual or online, but I was able to get them from Zooz suport (thanks @agnes.zooz! didn't know you were here 
) :
- Temperature: +/- 0.5 °F
- Humidity: +/- 2.5% RH
- Light: 0 lux = 1%, 20 lux = 50%, 40 lux = 75%, 70 lux = 100% (reports as % but HE converts it to lux)
Cross-posted here with more info about my use case.
1 Like
