Issues with z-wave since availability of update

Configuration Z-Wave
1

On my Home Assistant (HA), I’m using the Z-Wave JS add-on, which is now causing problems for the second time in a row. As soon as a new update becomes available, HA already starts displaying error messages. Most recently, this issue started at the end of last week when the update to version 0.18.0 became available. Even installing the update did not resolve the problem, meaning I can no longer control my devices. Sometimes a reboot helps for a few hours, sometimes unplugging and replugging the Z-Wave stick does, otherwise only restoring a backup works. Finally I spent two weeks now get it back running stable and it drives me mad.

With the previous update a few months ago, I had to restore the backup three times, then it worked again — until last weekend.

Error message:

“The action cover/close_cover could not be executed.

Unable to set value 50-38-0 targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts (ZW0202).”

Stick: zooZ 800 Z-Wave Stick ZST39

Trying different USB ports didn’t help either.

Core: 2025.7.2
Supervisor: 2025.07.01
Operating System: 16.0
Frontend: 20250702.2

Even though the devices can’t be controlled via HA, their states — such as on/off for lights — are still being reported to HA.

Z-Wave driver version: 15.6.0
Server version: 3.1.0

As mentioned before, the issues already occur when a Z-Wave update is merely available — even before it’s installed.

Thursday I updated the Z-Wave stick to version 1.60 via the JS UI (I tried to use it instead, as there are more options for failure analysis) and initiated a re-routing and node refresh overnight. However, the day after there was still no improvement. So, I reverted to the backup from three days ago and also back to Zwave JS. For a couple of hours my devices were available again. If not, it was possible to get them back to work with pinging.

In between HA is also updated to the latest version.

  • Installationsmethode Home Assistant OS
  • Core 2025.7.3
  • Supervisor 2025.07.1
  • Operating System 16.0
  • Frontend 20250702.3

Any idea to get rid of this issue? Same or similar experiences?

2

Is it always node 50 or does it change to other nodes.

Usually these problems are network issues or low battery —even at 50% some devices give trouble— and everything else is coincidence

How many zwave device you have?

What is mix battery vs AC powered?
A network composed of mostly battery devices may have trouble if, for example, battery device A connect to controller through battery device B. It it grows worse if multiple battery devices connect that way.

3

I wasn’t aware that battery devices ever act as repeaters in the mesh.

4

They don’t.

5

I have around 70 devices. Only 20 of them are batterie powered. As failure message I also received value 25-37-0, 13-37-2, 2-37-0 (checking the device list I saw that the first numbers are the IDs of the failed devices).

I just recognized weird values for some fibaro wall plugs >rain rate, another with water temperature and illuminace, or even -301°C air temperature and water oxidation reduction potential and even formaldehyde level. Checking other AC powered devices did not show those abnormalities.
The issues are only related to the AC powered devices

6

In the meantime, I found the error. Three Z-Wave switches that I use to measure my solar energy were sending their readings at very short intervals, which caused my Z-Wave network to collapse. I reduced the update rate, and now everything is running stably again and can be switched without any problems. I figured this out by observing the Z-Wave JS log protocol. I’m still puzzled as to why this happened when an update became available, but at least everything is working again now, and I’ve learned something from it…

2 Likes