Because it is the Z-Wave integration. It was previously the “Z-Wave JS” integration, back in 2021.
If you follow the documentation as suggested, which is
https://github.com/hassio-addons/addon-zwave-js-ui/blob/aff4733b6371e97122a922c984bf523e507aa3e9/zwave-js-ui/DOCS.md#setting-up-the-home-assistant-z-wave-js-integration (section “Now it is time to set up Home Assistant:”), then you shouldn’t have any problems.
Thank you learned quite a bit doing this. I did not realize that addons were running in Docker. I am running HAOS, so I did not expect Docker to be part of the equation
Ok, thanks, I have it running. My mistake with the documentation was not following it to the letter. I read in the documentation that it was not advisable to use MQTT, so when I saw that I was supposed to add ws://a0d7b954-zwavejs2mqtt:3000, I assumed this was for an MQTT installation server, not the WS server. I then went down a long and misleading path with the Copilot Ai which did not understand this part either. I spent a lot of time on this, but it taught me not to rely so much on AI, which is plagued with old information. I also watched several videos, and again, none of them were current enough for the job. Cheers
No wonder I and others were confused,
Zwave JS UI is ZwaveJSMQTT. The name changed because MQTT confused people… case in point.
You don’t need to use the MQTT portion of Zwave JS UI. You can use websockets for everything. You can also turn on the MQTT stuff if you want without using it. I had both running for a long time to gain extra functionality. Now that websockets is basically up to speed with the MQTT side, there’s no reason to have MQTT enabled unless you want to use MQTT. - from petro in zwave js ui and network graph