Is the humidity populated in your current states?
Ok. My mistake
Just have to wake up the device clicking 4 times the button.
Now, it works fine.
I appologize 
You switched from my driver to another custom driver, and there is a left over reoccurring scheduled job from this driver. If your hub is up to date one of the most recent builds they added a feature to clean things up when you switch drivers. So you could switch the driver to anything else then back again and it should take care of it. You can also switch to the "Device" driver and then use the command button to delete the scheduled jobs.
You are correct. I picked the wrong driver. Just updated it. Thanks a ton!
About to pair a zse70 on battery. If I decide to wire it in later, what's the process like to switch?
Just factory reset it, and start the pairing process over? Just thinking if I start building automations and switch later what's the easiest option.
Edit: I'm dumb I just realized the driver gives you an option to change the setting without excluding and re-including it. 
And that is just back up, all you have to do is plug it in and it reports that it got plugged in to the hub, the status should change by itself.
Now the hub itself will still think it needs a wake-up because it only checks the "NIF" at pairing (where the clusters come from). With ZIP gateway I did not notice any issues because it just does whatever the driver says to do. However with Zwave JS it has more built in handling for sleepy devices so I think it was refusing to send commands out until it gets a wake up, which will never happen once you plug it in.
So for Zwave JS you may need to exclude and pair again.
Good deal. I haven't made the switch to zw js yet. Just been gunshy about it still. Though I could probably do it on the garage hub since I really don't have much zwave stuff on that one..
On battery, will the pending commands eventually update when it wakes up or will I have to open it up and hit the button?
And ever notice the mounting tab/keyway is upside down on these sensors?
@TommyBoy, turn on debug logging and then wake one up again, it should clear the pending changes when it wakes. You should see in debug logs a message about the device waking up. Post the resulting logs. It would work from a manual wake or an automatic one. If you open/close the sensor do you get status updates?
@scoob8000 It will sync everything up at the next automatic wake up. For the mounting clip I have an original (pre-release actually). I think some of the initial users on Hubitat and maybe elsewhere had issues with the keyway on the back cover breaking, so Zooz changed it a little and sent all those people new back plates.
You would have to edit the driver and fix the range on that setting, although I would not recommend setting it that low. You will get very jittery reporting bouncing back and forth. Someone else already has tried it and said it was unreliable that low.
Thanks.
I'm giving it a whirl.
I've seen humidity with a similar issue elsewhere, so I'm minimizing that since I'm not interested in that.
Curious: Will battery life take a hit?
Yes, more reporting will drain the battery faster, because otherwise it goes into sleep mode when not reporting. No way to know for sure how much though.
Ok, thanks. I'll give it a whirl.
edit: Bounced around too much, irrationally. Went to 1 degree F,
Hi @jtp10181
First of all, thank you so much for implementing this driver. I am encountering an issue that is hard to replicate on my Hubitat. I have ZSE44 devices with the 1.2.2 version of your driver. After a few weeks, maybe a month, all of a sudden both of them start triggering an exception in the hubitat app:
com.hubitat.app.exception.LimitExceededException: Device 1 generates excessive hub load on line 436 (method parse)
(I’m getting an error pasting the screenshot.)
The devices are not too chatty, I report the temperature every 10 minutes in one and every 20 minutes in the other. Do you know what could be causing this? A hubitat reboot fixes this.
Usually that error is very misleading and has nothing to do with the driver or app triggering it. From what I understand it is basically saying is that the hub is already overloaded and because of that, when the driver got triggered it failed to run. It is a horribly misleading error and leads people in the wrong direction for a fix. You will need to look at the device and app stats to see if you can narrow down what is actually overloading the hub.
Thank you so much for your reply. I will wait for it to happen again and then look at the stats. Right now my usage stats averages less than 1%.
@jtp10181 Jeff, i just noticed today that my logs are getting spammed with a Warning:
dev:3072026-08-30 9:45:02.295 pmwarnOUT Luminance Patio (ZSE70): Unsupported Device USE AT YOUR OWN RISK: [0000, 0000]
This is occurring with startling regularity across both Sensors. I've been using these for several years, and don't recall these warnings.
Admittedly, when things work, I really dont pay attention, and they are working, I just found this odd.
Thoughts?
Scott