After switching the zse41 driver the device says there are 5 pending changes that will happen the next time the device wakes. I pressed the button 4x on the device to force the check in. Device blue light blinks, but it still says 5 pending changes even after waiting a few days.
I'm doing something wrong, because I have the same thing happening on all 10 of these devices in my castle.
Here's what I did -
I am not seeing any response to the various Get requests the driver is sending. The only things coming through are its own pushed events.
Are you by chance running Zwave JS gateway (C8 Pro)? If so, that is probably the issue.
You can tell on the Z-wave details page if you have a button that says "Switch to Legacy Zwave" then you are currently running Zwave JS
Yes running zwave JS.
I have 3 zse41s all paired LR using JS on my 8-Pro, and they're doing well. My 41s are the 800LR models - do you have those or the 700-series models?
With all of my Zooz battery devices, I typically have to do that button-x4 sequence several times in order to chip away at that pending-changes Sync Status, but I've always been able to eventually clear it down to "Synced".
All 10 of them are 800LR. Yesterday I was playing around with one of them and did multiple manual wake ups (maybe 4 or 5). I was able to get it to 3 pending changes. I felt like "this is stupid, I'm not supposed to be doing this. There is a better way."
Thanks for your experience. I'll have to decide if I can live with pending changes that don't seem to be impacting it much. The thought of doing multiple refreshes for 10 devices doesn't sound like much fun.
I split your topic off to a new thread. The issue is almost certainly with Zwave JS. I am confident if you switched back to ZIP the issue would go away.
What platform version are you on? I do not think you are in Beta so should be 2.4.2.158. The 2.4.2 release was especially problematic for Zwave JS. Your issue is possibly fixed in the current 2.4.3 beta version.
Were the devices paired on the Zwave JS gateway, or on ZIP then migrated to Zwave JS? It seems like maybe JS did not fully interview the device, that's where messages get blocked sometimes.
@bcopeland for your attention. See my assessment above, no response is coming back to the driver from GET requests.
It will marginally impact your battery life. Every 12 hours or whenever the device wakes up, the driver is sending them 10 messages to try and set the preferences (2 messages per setting).
If you want to troubleshoot further you would have to do a wake up and snag Z-wave logs from Zwave details. May not be worth it though, since issue is possibly already fixed in beta.
I never have this problem, if the z-wave is in good health it should sync up in one try.
Right on... I'm pretty sure we've both said this to each other before.
Once in a while, I'll get it to sync on first try, but it usually takes me 2, maybe 3. It's always been that way for my ZW battery stuff as long as I can ever remember on all of my Hubitat hubs.
It's no big deal at all -- I didn't mean for my comment to come across as a complaint or possible bug or anything else along those lines -- I always just figured the hub was maybe a little too busy right then or perhaps I'm just stepping on it being impatient 
. I've always been able to clear it easily enough, so all's well that ends well!
Thanks Jeff,
I'm current - 2.4.2.158
Were they in the system when I coverted to JS? I don't think so. I killed those brain cells off long ago. Definitely not all them were before the conversion, so I suspect other things may be contributing.
If I get bored I'll experiment with some additional device wake ups. Otherwise sounds like the best course of action is hang tight until 2.4.3
If that is the case you can go to:
/hub/zwave2/reinterview?node=xxx
If it's a sleepy device it will have to be woken up after this request
I tried running the reinterview link (I'm guessing node is the device ID?), and got a confirmation of "Done". Tried waking the device. Still shows 5 pending changes.
Node ID...
This number from Z-Wave Details page:
In the "it's worth a shot" category, you might try completely removing the call to wakeUpNoMoreInformation() in the driver to see if that fixes it.
I ran into this with my own drivers with ZWaveJS. The call to wakeUpNoMoreInformation() was preventing re-interview and firmware update from working correctly.
You can actually just disable the device in the devices list to prevent that command from going out. Might be worth trying disabling the device then do the interview and wake it up. You wont get any system logs since device will be disabled, but you could check the zwave logs.
After a minute or two you could turn the device back on and try the wake again to see if it worked.
4 posts were split to a new topic: Should Z-wave drivers be sending wakeUpNoMoreInformation
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
