It seems that every time I upgrade Z-wave JS I constantly have this issue where devices become unavailable immediately following the upgrade. Previously, I was able to address this by manually turning each device on; not optimal, but at least it worked. With this latest upgrade, that doesn’t even seem to work. I also tried restarting Home Assistant which didn’t make the devices available.
I’m getting really frustrated with the amount of time it takes to troubleshoot after every upgrade. It’s really affecting my ability to use Home Assistant consistently.
I rolled back to the previous version, which didn’t work. I ultimately unplugged HA and plugged it back in, which worked. I’m waiting for the next version after 14.0 to upgrade.
My guess would be that the upgrade restarted the integration and the availability values are not restored on restart, which makes sense.
That means the sensors will be unavailable until the device report in again and that can take some time depending on the devices.
This can often not be controlled by HA, because the devices are in sleep mode. A triggering on the device should however update it, but it might still take. A few seconds for the device to transmit.
Same happened to me, I rolled back to yesterday backup of the Addon without luck. All of them are death, they don’t come back even after using the ping or manually turning on/off the lights.
I’m using the Aoetec 700 series.
All the Fibaro or Shelly Zwave switches are out, same as the movement sensors.
I cannot make it work. I tried to restart full PC (proxmox → HA VM). Unplug plug stick. Rolled back to 13.1 version, nothing seems to work.
The Zwave js integration load just fine, it seems to be connecting with Stick.
However, logs after initiation are full of
2025-06-10T22:06:17.503Z CNTRLR [Node 019] ping failed: The node did not acknowledge the command (ZW0204)
2025-06-10T22:06:21.692Z CNTRLR [Node 011] The node did not respond after 1 attempts, it is presumed dead
2025-06-10T22:06:21.692Z CNTRLR [Node 011] The node is dead.
2025-06-10T22:06:21.693Z CNTRLR [Node 011] ping failed: The node did not acknowledge the command (ZW0204)
2025-06-10T22:06:26.659Z CNTRLR [Node 006] The node did not respond after 1 attempts, it is presumed dead
2025-06-10T22:06:26.660Z CNTRLR [Node 006] The node is dead.
2025-06-10T22:06:26.661Z CNTRLR [Node 006] ping failed: The node did not acknowledge the command (ZW0204)
I saw this on the logs
It seems the update changed the frequency from Europe to US. I guess that explains why it doesn’t work.
Question is how do I put it back in EU frequency??
2025-06-10T19:43:58.540Z CNTRLR Querying configured RF region...
2025-06-10T19:43:58.547Z CNTRLR The controller is using RF region Europe
2025-06-10T19:43:58.547Z CNTRLR Current RF region (Europe) differs from desired region (USA (Long Range)), con
figuring it...
2025-06-10T19:43:58.555Z CNTRLR Changed RF region to USA (Long Range)
2025-06-10T19:43:58.555Z CNTRLR Querying configured max. Long Range powerlevel...
2025-06-10T19:43:58.562Z CNTRLR The max. LR powerlevel is 14.0 dBm
2025-06-10T19:43:58.563Z CNTRLR Querying configured Long Range channel information...
2025-06-10T19:43:58.569Z CNTRLR received Z-Wave Long Range channel information:
channel: Unsupported
supports auto channel selection: false
2025-06-10T19:43:58.569Z CNTRLR Performing soft reset...
Starting from v0.14.0 of the the add-on it automatically sets the controller’s region based on the home country of your Home Assistant. Is your HA set to USA for some reason, or any of the other similar regions? (Or maybe there’s a bug…)
Edit: I confirmed the following on my HAOS test instance:
The add-on region is set to Automatic as expected
My controller region was USA LR and HA country set to US, nothing changed on add-on restart
I changed my HA country to Denmark and restarted the add-on, it automatically set the controller region to EU as expected
I changed my HA country back to USA and restarted the add-on, it automatically set the controller region to USA, and Z-Wave JS automatically set it to USA LR (as my controller supports LR), as expected
Having the same problem. My Z-wave sensor seems to be OK, but both my zwave enbrighten switches are not being found. I removed them, and tried adding them again and it doesn’t even find them.
I’m located on Argentina. I’m not even sure what we are supposed to have here. Since this kind of tech was very hard to buy here, specially few years back, I just bought everything in europe…
Anyway. I was trying to find the option where to change the frequency on the Zwave device without any luck until today. I remembered there are also settings on the Addons section.
The way to fix it is to go into Settings → Addons → Zwave Addon → Configuration → Change the Frequency region from Automatic into the one you want.
Ok, so I did go and check the configuration and it should have been US and it switched to EU. I switched it back to US and now I can add the two switches again, however they don’t appear as switches, they just appear as devices and the only option is to ping it. Manufacturer and Model both appear as unknown. How can I manually edit the device that was found to match the appropriate device? Things I have tried. Removed the device, and re-add them. Re interview same thing, it finds it but doesn’t know what it is apparently.
I went ahead and removed it again from the z-wave.js area went through the process of removing the node. As soon as I removed that node, the enbrighten switch showed up on the dashboard. I did the same thing with the other switch and was able to add that one as well.
