With ZWaveJSUI there are two configuration options, either a websocket server, or MQTT discovery. Which should I use to best integrate with Home Assistant?
I’m using ZWJSUI, Mosquitto and NodeRED on one machine for the “brains” of my home automation and Hass is on a separate machine. Hass is up and running, connected to the broker but I was looking for an easy way to populate my zwave devices in Hass.
Thanks!
I guess that would depend on each instance. I personally use the WebSocket server, even though I have an MQTT broker installed. Less dependencies at least. I’d guess that when originally created most people used MQTT, but now more people use WebSocket. No way for me to know for sure, however.
I have both enabled, but I’ve disabled auto discovery for the MQTT bridge. This way, all the devices & entities appear under the Z-Wave integration, but I have the option of sending control commands over mqtt messages. Mainly this gives my WiFi devices, such as Tasmota, some “direct” control over Z-Wave.
For a while after zwave-js debuted, a lot of functions were only accessible via mqtt but I think the websockets have since reached feature parity with new actions/services. One exception is if you’re using scenes inside ZUI (and I’m not sure why you would), they may still be only controllable over mqtt.
Because ZWave Miulticast
Although even over sockets calls try to use multicast if possible.
Op should be fine with Websockets unless they have one of these fringe cases.