With User Developed Drivers, the code is always available on the web or Github. But where do I get the Hubitat basic Driver code so that I can attempt to add to it to add wakeup interval?
This not a built-in driver. The source code is available linked to in the post @hydro311 wrote above.
Sorry, I am looking for the Zooz ZSE43 Driver Code, not the Basic Z-Wave Tool code. Or, are you saying that the code you provided, above, should be added to the Basic Z-Wave Tool code?
I highly doubt hubitat will modify the in-box driver to make wakeup configurable - they tend to try and keep all their devices similar in functonality, and they didn't add this feature for anything else.
Could use this one chad made a long time ago, and modify it to your heart's content.
1 Like
Yes, the idea was to add this to the Basic Z-Wave Tool driver, as I mentioned; it could then be used for any Z-Wave device with this added functionality.
The built-in ZSE43 driver is not accessible, so to do otherwise, you'd have to start with something else, like the above.
1 Like
@dean contacted me and asked for a driver with the wakeup setting. I already had a partially complete driver but no device to test it with. Anyone with a ZSE43 can test this out if you want and let me know how it works.
I saw that another user driver is out there using the acceleration attribute due to app compatibility, so if this works I was thinking about adding a toggle so you can select if it will report as shock or acceleration.
You just set the setting in hours, save, then you will need to wake up the device so it can be set. If you enable debug logging you will see a confirmation when it is set, also the value in the data at the bottom will update (in seconds).
Z-Wave spec says this can be set up to around 4600 hours (in seconds), but I tested on another Zooz device and it maxed out at 24 hours so I made that the max. I chose to make the setting in hours so its easier to figure out, not sure when anyone would need 1s granularity on this?
hxxps://gist.github.com/jtp10181/d01a4de4145f0f08f6b20e20dda1b3dd
Test Link removed, driver added to HPM package:
-- [DRIVER] Zooz Sensors Advanced (ZSE11, ZSE18, ZSE40, ZSE41, ZSE42, ZSE43, ZSE44)
3 Likes
After configuring this driver and sending a wakeup I'm still showing 1 pending change, tried several times. My device is on 1.2 firmware.
Edit: Tried the driver with a second ZSE43, same results (1 pending change)
1 Like
I see in the changelog they removed Param 2 in firmware 1.4 which is the one it is having issues with, are you sure you are only on 1.2, it should actually be working on that FW. Either way, I will just remove param #2 from the settings and post a new version when I get a chance. The pending change wont hurt anything really, rest should still function.
1 Like
Yeap, somehow I was on the ZSE42 changelog, the ZSE43 does not say anything about removing param 2 but they must have removed it in 1.2 as part of "optimized battery reporting"
2 Likes
Pretty sure they removed it.
1 Like
My ZSE43 is running firmware 1.10. I have just tried the Driver, above.
- Seems to be working on my device. Pending Refresh and SyncStatus both report properly. Though I don't know if it has really adjusted the Wakeup Interval.
- The Shock Sensitivity now provides for only High and Low values. With the HE Driver it provided for High, Medium, and Low.
- The Wakeup Interval will only accept a maximum value of 24 hours. Really wanting to set it to something like 120 hours.
- I really appreciate the fuller description of every parameter.
You could try, but I doubt it will work.
Last time I tested this on a zooz device (admittedly a long time ago) it did ~24h max. Any setting above that still did ~24h. I think it is a "quirk" of their firmware...
I just posted an updated version at the same link. @dean @halfrican.ak
- You can check the last reported wakeup value in the "data" at the bottom of the device page listed as zwWakeupInterval
- Fixed, I had both Medium and Low mapped to the same value on accident.
- I explained this above. If you want to edit the code it is around line 92, you can adjust the range higher but the device probably will not take anything greater than 24hrs.
This is also now fixed.
3 Likes
Driver seems to be working perfectly for me now, thanks
1 Like
Should there be an option for Reporting of "None"?
Zooz Support confirmed to me that the ZSE43 has an allowable wakeup interval of 600 to 86400 seconds.
Note/Rant: I am constantly surprised by the engineering decisions made by Zooz. They have some really innovative products, but they are usually hampered by really dumb design decisions. In the case of the ZSE43, the battery is way too small, and there is no reason to limit the wakup interval to 24 hours, nor make it so difficult to change.
Not sure what you are asking exactly? What reporting?
It is not difficult to change, it is easily changed using the standard zwave commands. It was only difficult because drivers typically do not implement a setting for this.
2 Likes
Meh. All of that is debatable/opinion.
Battery too small?
- Maybe. I always want bigger battery, but it does last about a year for me on my garage doors, so it doesn't seem THAT bad. I only have the tilt sensor enabled on mine, maybe that makes it last longer than having shock + tilt? Don't know, didn't test shock on it other than to write an (unpublished) driver for it.
- EDIT: Never mind the below text. Zooz confirmed the ZSE43 800LR will use the same CR2032 battery as the previous model. Boo.
That said, I am hoping they put a CR2450 battery in the ZSE43 800LR version that is upcoming, like they did on the ZSE42 800LR model. Not sure if they will or not as they left the ZSE41 800LR model at CR2032, so they clearly aren't going to CR2450 across the board...
Wakeup period?
- Yes, I also think they should support the max in the spec. But that said, there is almost zero PRACTICAL battery life to be gained doing 1 day vs 30 days vs 90 days on wakeup. It is easy to calculate what the benefit would be, and it is essentially zero.
- Plus I could totally see users setting it to 180 days and then also bitching that changes to the configuration never work/take effect.
Wakeup difficult to change?
- It is changed the same way it is changed on every other zwave device.
- Maybe the complaint is with Hubitat and their in-box drivers that don't expose most settings? Still not a Zooz specific issue though.
1 Like
@dean @halfrican.ak
Driver was released and added to HPM package. Minor updates since the test driver was posted:
-- [DRIVER] Zooz Sensors Advanced (ZSE11, ZSE18, ZSE40, ZSE41, ZSE42, ZSE43, ZSE44)
2 Likes
