Z-Wave JS Server version is incompatible after 2022.5 update

[ben1492 (William Chesnutt)]

I’m running HAOS in a VM. I found that after adding the repository, updating the zwave2mqtt add-on to 0.39, and updating Core to 2022.5.3, I then had to restart the host in order for zwave2mqtt to find the zwave stick. Simply restarting HA or even the HA VM was insufficient. Others have had success by simply unplugging / replugging the zwave stick, but that did not work for me.

Even after getting it all up and running, I was unable to lock / unlock my locks and much of the additional lock sensor data, like battery life, were unavailable. I’ve since gone back to Core 2022.4.7 and zwave2mqtt add-on 0.37. Everything is working now. There are some really great improvements in the May update, so hopefully these zwave glitches get sorted soon.

[Cavallo]

Thanks for the help, here. I’ll detail my use case:

Issue Statement:

The default add-on repository was missing from my Home Assistant ESXi VM instance after the recent core update from 2022.4.7 to 2022.5.3.

Resolution:

Step 1) Re-adding the add-on repository https://github.com/hassio-addons/repository then updating my add-ons from it (for Node-RED and zwave2mqtt) only half-resolved my z-wave issues, but was definitely a necessary first step (strangely, about half my devices worked after adding the repository & updating from it, including two devices of the exact same make and model, one working and one not. This includes multiple reboots, including even safely rebooting the ESXi server after shutting down the HASSIO VM).

Step 2) The second step that fixed everything for me was to do a network-wide re-interview of devices. It’s available to do in bulk via the general actions button on the Z-Wave JS to MQTT dashboard. I did NOT reset security classes during the re-interviews (left the checkbox unchecked). Once the devices which weren’t responding were interviewed again, they began working as-intended.

Afterthoughts:

It DOES bother me greatly that this repository just went missing (as I remember it being there while adding zigbee2mqtt on a separate occasion a couple of months ago), but for now I’m glad the devices are functioning as-intended on the latest version, again. Thanks for everyone’s help, here.

[pentar (Joris)]

I have the same problem, but don’t really understand what the problem is and what fixes are proposed above. I’m running HA on a RPi, with HACS and ZWaveJS2MQTT.

Is there a clear step by step explanation of the fix? Thanks!

[petro]

You’re really making this seem complicated. It’s not. Click the link and add the repo. It’s a single button click to add it.

2022.5: Streamlining settings

So in core version 2022.4 there was a bug where the hassio integration asked supervisor to do a full update check on all addon repos every 5 minutes. This meant that every user with supervisor on core-2022.4 was trying to pull the official, community and esphome addon repos every 5 minutes. GitHub (understandably) took defensive action because of this as it saw it as either a DOS attack or a breach of TOS (using a repository as a CDN) and started dropping requests. When the request got dropped s…

[mtnman]

I had this same issue but have made things worse and now am stuck. I added the repository back and could see zwave2mqtt again but the old version would not show an update button so I added the newest 0.39 which left me with 2 versions of the addon so deleted the old (working) one which then broke the z-wave js integration.

I now get the following error and am unsure how to fix it.

Retrying setup: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Name does not resolve]

I did try deleting and re-adding the integration but it won’t connect using port 3000.

What should I do next?

EDIT:
I realized the mqtt needed configured since it was effectively a new install. Once done, things are showing back up and the integration is working.

[petro]

You should restore to your previous backup, add the repository and wait for the update to appear. You can also click the check for updates button to speed up that process.

[mtnman]

@petro

he

Thank you. I found a solution which I added as an edit to my original post. Appreciate your response though.

[trikar21b]

This fixed it for me too! Thanks! Should’ve searched here before I tried anything else.

[taxelas (Alex)]

Hi folks,
after update to 2023.3.5
I faced the same issue.
I run zwave2mqtt on the remote raspberry as docker container.
Updating zwave2mqtt didn’t help
It appeared that zwave2mqtt docker image is deprecated
I did change the image to zwavejs/zwave-js-ui in my docker-compose file
and run it : docker-compose up --remove-orphans
And it worked
Edit:
As @petro rightfully noticed, I meant zwavejs2mqtt image which is deprecated and zwave-js-ui is its successor.

[petro]

You’re confusing zwave2mqtt with zwavejs2mqtt. They are 2 different things. Either you went to the wrong docker image or you’re mistaken about your install. Either way zwave2mqtt uses mqtt to talk with HA. That will always work. Zwavejs2mqtt uses websockets to talk with HA, that requires the api versions to be in sync.