I have a Zooz ZSE42 Leak Sensor and several ZSE41 Contact Sensors. They work perfectly except when not "tripped" they do not "check-in" with the hub. What is a good way to determine if the device is still alive? I would have expected a periodic wakeup and check-in, like a heartbeat. I am currently using "Botched1" custom drivers. Any thoughts?
Both the ZSE42 and ZSE41 manuals say that they do a wakeup every 12 hours by default, checking in with the hub to see if it has anything to do or update. The driver could request a battery update or another operation during the wakeup, and update data timestamps if it wanted. The wakeup interval is adjustable from the device's POV, you could change the wakeup interval with one of the zwave parameter drivers, or have the Botched1 driver enhanced to allow adjustment of the wakeup period.
My ZSE29 motion wakes up every 12 hours.
edit: correction, my ZSE18
Interesting, what driver are you using? Built in or community?
I have tons of Zooz battery powered stuff, including several ZSE42s and they all check in approximately every 12 hours with the possible exception of ones sort of at the edge of the mesh that do occasionally miss a check-in (e.g. Water Sensor Master Bath Toilet in the bottom row in the following snip). I only use stock drivers and @jtp10181 's drivers.
All of the yellow highlighted ones are Zooz battery devices and the blue ones specifically are ZSE 42s:
1 Like
I also have a couple of Zooz ZSE 42 leak sensors that miss their check-in periodically, both in edge areas. They however work perfectly if triggered.
1 Like
For leak sensors, I tend to set the checkin/battery update period to every 2 to 4 hours. It does decrease battery life a bit but batteries are cheap, water damage is not.
How do you modify the checkin value? It is not exposed in the driver.
Speaking of the driver, I switched back to the built-in driver for the ZSE42 to see if that makes any difference.
- Easiest way is to quickly modify the value in your local copy of the driver:
// Wakeup Interval
cmds.add(zwave.wakeUpV2.wakeUpIntervalSet(seconds: 43200, nodeid:zwaveHubNodeId).format())
Update to the number of seconds you'd like to wake up on. Then you'll need to change any parameter so that when it wakes up and checks in, it will detect something has changed and send all configuration over, including the wake up.
2. Advanced would be to add the ability to adjust the wakeup period via a UI parameter. Not too difficult.
3. There may be one of the "generic parameter" drivers that allow you to adjust zwave parameters that also allows adjusting the wake up period. I couldn't find one off hand, sorry.
1 Like
It appears that the Community drivers that I have been using do not get or respond to the battery reports. When I switch to the built-in drivers I see check in events. but quite frequently.
Is anyone else seeing this?
I actually recommend the system driver for the ZSE42. The community driver was made before the system driver was available and there is really not much for settings. I only switch to a modified community driver if I need to change any other settings.
Anyway... reporting is normally only every 12 hours. What firmware do you have? Some of the recent Zooz battery devices early firmware versions had issues with spamming battery reports, especially if the signal was weak or there were a lot of hops. I think they fixed the majority of the issues with current firmware.
Is your feeling the same about the ZSE41 open/close? Prefer the system driver? I am having the same issue with those.
The one ZSE42 that I have is at frn 1.50, the latest from what I can determine.
I have 8 ZSE41's, 6 are at frn 1.40, 1 is at frn 1.30 and 1 does not report what it is at. Updating the firmware on these is a B$%^H with the "Device Firmware Updater" app, especially once installed in their final location. Hate to take them down to move them closer because then you ruin the mounting tape. Would using a Zooz Z-Wave stick make this any easier? I just bought one as they are 20% all today.
Yes I use the system driver on those as well, but it wont help with excessive reporting. Looks like the battery reporting issues were addressed with the 1.30 FW on the ZSE41 so you should be OK there.
Every couple of hours is not the worst that could happen. Before the fixes some people were getting reports every few seconds non-stop. I would just let it sit for a few days with the system drivers and see what the event log looks like.
Yes, you can use PC Controller on a laptop, join the stick as a secondary controller and then to do FW updates from the stick with it right next to the device. I have done this before and it works good. Works with any security level as long as you join the stick with the full S2 permissions.
Do you know if the system drivers will set/revert the wakeup interval to the default of 43200 if I changed it with the community driver?
I suspect that would only happen at a configure, which there is no button for on the system driver. So that would normally only run if the device was reset and paired again using the "replace" feature.
Is there a write-up somewhere about updating firmware via the Stick (secondary controller)? Does the device have to be excluded from HE first?
Not that I can recall. I do need to update something though so I could grab some screenshots. Its pretty easy. Just pair it to your hub as a secondary controller, instructions for that are in the ghost removal guide. Once that is done, there is a firmware update section in PC Controller. Pretty self explanatory from there.
1 Like
Thank you, that would be very helpful.
I wrote this up and then realized you have battery devices. They are much more of a pain to update using PC Controller as a secondary. I don't have any battery devices on my test hub to confirm the exact steps I have used before. But maybe this will help?
That does seem really easy. That just means I'll spend hours trying to get it to work. Still waiting on my Zooz Stick. USPS is sloooooooow. I'll report back. Thanks again for all your advice.
