Z-Wave JS fails with error "invalid response status"

Configuration Z-Wave
1

Hello,

So I thought I’d update to Home Assistant Core 2023.10.5 today. Turns out the Z-Wave integration did not like that one bit. After the update it failed with the following message:

Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: 200, message='Invalid response status', url=URL('ws://192.168.1.207:3000/login'); Retrying in background

I tried upgrading zwavejs2mqtt with no luck.

I’ve searched around and found that a lot of people are having issues with 2023.10.5 and Z-Wave. I am running HA in docker with zwavejs2mqtt in another docker container. This has been running smoothly for quite a while. Naturally I tried downgrading to see if I could get rid of the issue, but as it turns out not even that helped. I haven’t tried anything lower than 2023.9.0 since I’m fairly sure I at least had that version previously (I’m not quite sure, I’ve been running on the stable tag. Guess I’ve learned my lesson now). I also downgraded zwavejs2mqtt but nothing seems to convince it to start working again.

Any suggestions?

Please let me know if you’d like me to post more details.

2

Theres been MANY updates to Zwave JsUI (so many you missed a name change from Zwavejs2mqtt?)

Reason I ask the last few updates have a minimum ZWave JS/JS_UI version. Current JsUI is 3.0 something and I think you need a recent 2+something to be able to even connect to HA after 2023.10

3

SO bloody many… Sheesh, it’s been a bit of a roller coaster!

1 Like
4

I’m using the docker image zwavejs/zwavejs2mqtt:8 and have been for some time: Docker.

I am using the regular Z-Wave integration in Home Assistant.

Edit
It’s still being updated as far as I can tell. But there may well be something I missed.

5

Excellent then we know exactly what you need.

See this page-specifically breaking changes section. Under ZWave:

It says this :
With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 1.32.0 or greater (schema 32).

  • If you use the Z-Wave JS add-on, you need at least version 0.1.91.
  • If you use the Z-Wave JS UI add-on, you need at least version 2.0.0.
  • If you use the Z-Wave JS UI Docker container, you need at least version 9.0.0.
  • If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 1.32.0.
6

Ah, okay thanks. I did try upgrading to 9 as well. Let me try again.

1 Like
7

Yeah i dont know how many versions you skipped but you need to spot check the breaking changes for each release you skipped and make sure they don’t apply.

Good luck!

8

Still the same. I already tried upgrading to 9 after upgrading to HA 2023.10.5 (it’s frequently been the case so I made it a habit to upgrade zwavejs2mqtt anyway).

So I’m now on

zwave-js-ui: 9.3.1.f26b79e
zwave-js: 12.2.3

and
Home Assistant 2023.10.5.

I think I was on 2023.9.x previously, but not sure. I will try rolling back to 2023.8 tomorrow as rolling back to 2023.9 did not fix the issue either (as well as rolling zwavejs2mqtt back to 8).

Any other suggestions in the mean time is much appreciated :pray:

9

You should be looking at the Z-Wave JS UI logs at this point, and look for any additional messages in the HA logs.

1 Like
10

Unfortunately even including debug logs did not grant me any additional insight into what’s going on.

11

I’m not quite sure what happened, but changing the exported port in the container fixed the issue. Might be that since I have 2 Pis configured in a Docker Swarm, traffic was routed to the other host where some other service was using the same port. Normally that would cause the container to fail, but I had zwavejs2mqtt running with docker-compose and not Swarm, so the port wasn’t really bound on the host on which I was running zwavejs2mqtt.

1 Like