Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Build/Run method
zwavejs2mqtt version: 1.4.0
zwavejs version: 6.5.0
The bump to zwave-js/server 1.0.0 https://github.com/zwave-js/zwavejs2mqtt/commit/a89643eb72b30d0974154b6eb382db21a025c33c seems to have broken the integration with the latest stable version of Home Assistant via websocket. Devices show up as orphaned and entities unavailable.
When reverting to 1.3.0 (zwave-js/server 1.0.0-beta.8), things work as expected.
Steps to reproduce the behavior:
This issue might be more appropriate in the upstream https://github.com/zwave-js/zwave-js-server repo, but I've submitted here as this I believe it is applicable.
My Z-Wave setup is also broken after updating from zwavejs2mqtt 1.3.0 -> 1.4.0 in latest Home Assistant version. All my entities are in an "unavailable" state.
I can confirm
You gotta wait for the HA beta release in a few hours since the WS 1.0.0 is already in zjs2m.
My zwave is also down now, any workaround?
My zwave is also down now, any workaround?
I'm using image: zwavejs/zwavejs2mqtt:sha-fec72b7 in my compose file to revert to 1.3.0
The HA beta images are already building, should be available pretty soon.
My zwave is also down now, any workaround?
I'm using
image: zwavejs/zwavejs2mqtt:sha-fec72b7in my compose file to revert to 1.3.0
Thanks, worked for me
The HA beta images are already building, should be available pretty soon.
Not going to beta with my main setup :) Thanks!
@aneisch, @towerhand Thank you for explaining why I was having problems. And thank you for the downgrade id!
_I've been banging my head against the wall all day today. I was having problems so I poked around and ended up deleting some of my devices so I decided to start from scratch._
Please do NOT update to zwavejs2mqtt 1.4 if you're running the stable version of HA due to a version incompatability.
Next version of HA (beta released today) 2021.3 will be compatible again.
Thanks!
@robertsLando any chance you can add that disclaimer to the 1.4.0 release notes to help out some future folks?
Please do NOT update to zwavejs2mqtt 1.4 if you're running the stable version of HA due to a version incompatability.
Next version of HA (beta released today) 2021.3 will be compatible again.
Thanks!
I am now running core-2021.3.0b0 on docker with zwavejs2mqtt at 1.4 with the same issue.
Yeah, just found this out the hard way. Also tried the beta docker image which didn't communicate, additionally after reverting back both HA and zwavejs2mqtt I have a ton of excess orphan entities attached to my devices now. Thankfully the original ones are still there.

I just updated HA docker to run :beta and I also ended up with the orphaned etries; but it looks like the orphaned entres are the originals, and I have gotten new entries that works... I.e. I need to rename all my entries again.
To the developer: this is annoying, but it is annoying in the same way that a classic car breaks down; we all know what we signed up for when we jumped on this extreamly new project. Keep up the good work, at this stage we like your speed more than the convenience of stable stuff 馃槀
Will add this disclaimer:
Please do NOT update to zwavejs2mqtt 1.4 if you're running the stable version of HA due to a version incompatability.
Next version of HA (beta released today) 2021.3 will be compatible again.
Looks like a PR was merged to fix the broken migration https://github.com/home-assistant/core/pull/47031
New Beta update now, now i also get vocer Up/stop/Down buttons! Awesome!
Now I have twice of all, dead entities. Is there any ez way to remove the dead ones and avoid renaming the new ones manually?
Most helpful comment
My Z-Wave setup is also broken after updating from zwavejs2mqtt 1.3.0 -> 1.4.0 in latest Home Assistant version. All my entities are in an "unavailable" state.