All configuration variables available with designated defaults per Zooz
Pressing Configure will queue up a full reconfigure next wake up.
Pressing Refresh will queue up a full refresh next wake up.
Normally at Wake Up it will just request the battery level to avoid excessive commands.
If you change settings and save it will queue them up to be set at the next wake up. So you can force it to wake up right away or just leave it and let it do it on its own.
Works for ZSE40 (original 500 chip) and ZSE40-700 series. (May work on older models as well)
IMPORTANT Tips for ZSE40 MultiSensor
NOTE: The ZSE40 v2 with 500 chip has a final firmware update to 32.12 that you can get from Zooz. This sends alerts to the hub at the start and end of active motion only. The repeated alerts every 8 seconds was removed. This will greatly cut down on excessive z-wave traffic.
NOTE: For the original ZSE40 (500 series) FW < 32.12 I would HIGHLY recommend changing Parameter 8 to "Notification Reports Only". For the ZSE40-700 I am myself leaving it at the default to make sure no motion reports get missed.
Please use GitHub to report any issues so each one can have its own conversation and tracking. Please provide as much info as you can including model, firmware and the "configVals" data string. Issues · jtp10181/Hubitat · GitHub
Must PRESS CONFIGURE BUTTON and check all your parameters after changing to this driver.
I actually just realized that out of my 3 ZSE40s, one is on 24.16, one is 32.20, and the 3rd one isn't showing a version number at all. No biggie, I thought. I switched to the zwave firmware updater driver, thinking I could initiate a get version report, and then go wake up the sensor with the zwave button. But I can't get the get version report to queue up. After clicking the button, literally nothing happens (confirmed with debug logging turned on). So I'm not sure what version my 3rd one is.
So this makes me wonder, what has changed between firmware versions on this sensor? I don't even see a changelog for it on Zooz's website. @agnes.zooz
@jtp10181 why does this driver require a minimum firmware of 32.02?
32.02 is the listed minimum because I don’t know what was added or changed anywhere before that, so it might actually work fine with older versions. If anyone wants to test and we find issues I can adjust the driver to work on them.
Its basically the same device, just upgraded chip to 700 series and updated the command classes and firmware. I think the 700 chip is supposed to get better battery life and the fact that it does not send constant motion notifications while motion is active should prolong the battery as well.
Since it is a brand new device, wont have a real life answer for you for a few months. Mine is being long term tested as we speak.
There are 3 versions of this sensor now. The V1 ran off of I think a CR2032 battery. The V2 (of which I have 3) runs on a CR123a battery. I've had them for at least a year at this point and have not had to replace the battery yet.
Technically, there is not a V3. They took the V2 sensor and put a 700 series chipset in it and updated the firmware.
Thats probably actually 32.02 which is the original the v2 came with. You can try my driver and setting parameter 8 to off. I am not sure if that firmware has it implemented yet so you might just get a pending changes where it cannot set it. 32.18 for sure has that parameter if you get the newest and update it.
Also pairing with a USB stick and bypassing the S0 pairing will cut down on the zwave chatter some (there is a guide on here somewhere for it). I am running a V2 32.18 on S0 security in my office that gets motion non-stop during the day and it has not been causing any obviously detrimental to the mesh. Also Zooz keeps telling me they are working to see if they can get rid of all the extra chatter totally with another firmware update to the 500 series model (I remind them about it every once and a while).
Oh, also you need to wake the device up manually so the driver can grab a version report. Then refresh the page and it should have the deviceModel in the state variables.
If that doesn't work you could try doing configure, press configure first then wake up the device. Configure might reset some of your parameters to the defaults.
Did a battery pull this morning, noticed sync status doesn't update, even with config pushed and additional battery pulls:
syncStatus : 3 Pending Changes
tamper : clear
Went to the device driver, and confirmed the URL for the code.
Also, saw this in the logs: dev:8382021-11-07 05:53:12.002 pm [error](org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZSE40_4_in_1_Multisensor_883.logsOff() is applicable for argument types: () values: 
EDIT: Noted the menu config options are still not showing up in the device.