Zooz won't report state change after 0.1.17

Configuration Z-Wave
1

I have around 10 Zwave devices from Zooz
Most of them are Zen30

My zwave JS was 0.1.17
After I updated it to 0.1.18 or 19 the devices stopped reporting changes when you use the physical buttons.
Sometimes it reports wrong as well. You turn on the light and shows that I turned on the relay and the light doesn’t change.

The thing is, I noticed that, went back to 0.1.17 using a backup and everything was fine.
Until I updated HA to the latest version.

It automatically updated my ZWaveJS to 0.1.21.
Now if I restore a backup with 0.1.17 if works for a minute and then HA automatically updates it to 0.1.21 again (the auto update option is off) and screws up everything again.

I saw a work around for it using templates and stuff, but it was working before without any of that.

Anyone experiencing the same?

My Zen30’s are using firmware 1.07.
I rolled back to 1.05 because I’ve heard in the past people having problems with state changes using hubitat. It worked fine for a couple minutes and it stopped again.

2

Have you contacted Zooz support? In my experience they are very helpful.

3

First, you should probably re-interview the nodes to pickup changes between different versions of node-zwave-js.

Second, there is an open issue pointing to some strange behavior with either the driver (node-zwave-js) and/or the device. I’d watch this for progress: https://github.com/zwave-js/node-zwave-js/issues/2536

This sounds similar to the behavior described in the Github issue linked above. Do you have any links to Hubitat forums that discuss this? If you re-interview the nodes with the 1.05 firmware, does it work as expected?

1 Like
4

I just sent them an e-mail asking for the original 1.03 firmware and told what was going on, let’s see

1 Like
5

I’ll take a look at the github link
So, when you update the firmware you need to add the device again because the node becomes dead.
So I usually do a factory reset on the Zooz Switch and then add the device again (new node number and everything).
I did this yesterday and thought it fixed the issue because it was working fine again. In the morning today the problem was back :frowning:

6

The link from github describes exactly what’s happening with me.
I just posted a reply there adding that I have the same issue but it didn’t happen up to Z-Wave JS 0.1.17
Thanks!

1 Like