Another quick question on the control panel, while reading the GitHub page info on this I saw this image:
when referring to some componant management that appeared to give some good information under the Home Assistant tab. But my control panel lacks in this department as I don’t even have that tab. Is this from a different version or did I set it up differently which caused this. I’ve been going into the integration to get a lot of this detail.
The home assistant tab is for MQTT, which you shouldn’t be using. Also, that screenshot is out of date.
Good to know, thanks for the quick response.
If you’re not running hass.io and don’t have the community add ons, is the only other way to go to run the docker container? If so, is there anything I need to install in my HA instance? Just the MQTT integration and point it at the MQTT broker running in ZwaveJS2MQTT?
yes
or you can go the hard way and install the zwavejs server directly on the host. But who wants to do that when the container offers you everything you need?
it depends.
you cab run the zwavejs2mqtt in two ways - via mqtt or via websockets.
if you run via mqtt you need an mqtt broker and you need to configure HA and zwavejs2mqtt to talk to that broker. and setting up mqtt discovery is a benefit as well.
if you run it via websockets then you will need to enable that in the zwavejs2mqtt control panel. THen in HA you need to configure the zwavejs integration to communicate to the zwavejs2mqtt websocket server.
Or you could do both if you really wanted to but it’s unnecessary and could get confusing since zwavejs2mqtt would create two of everything in HA - one for MQTT and one for websockets.
Most people seem to run websockets.
I followed the guide and now have a nicely functional ZWaveJS2MQTT based setup. Thanks @petro for the guidance.
But I noticed a weird behaviour this morning that I’m wondering if anyone else is seeing. If I stop the ZWave2MQTT Addon for any reason (for example, to upgrade to the latest version like I did this morning when 0.15.0 was released), then for some reason the “official” ZWave JS Addon gets automatically installed, starts, and takes over the ZWave USB dongle. That obviously means that the ZWaveJS2MQTT Addon is blocked from using it when it starts up a few seconds later (e.g. after the update).
Fixing it is as simple as stopping the official ZWave JS Addon, uninstalling it again, and then restarting the ZWaveJS2MQTT Addon, but it’s really annoying, and it’ll just pop up again the next time I stop/restart the ZWaveJS2MQTT Addon.
Is anyone else seeing this? I checked, and the ZWave JS integration seems to be configured properly to use the ws://a0d7b954-zwavejs2mqtt:3000 server. So I’m not sure what keeps trying to default to the ZWave JS addon.
Suggestions would be much appreciated.
Nevermind. I figured it out. For anyone out there who’s also seeing this, here’s how I fixed it.
(Be sure to take a snapshot before doing anything)
I uninstalled the ZWave JS integration and reinstalled just as a test, making sure to uncheck the “use official addon” box like it says in big bold letters in the documentation. I was pretty sure I did that the first time around as well but I guess I fat-fingered it because this install didn’t see the same issue I described above.
But, I had already spent hours configuring device and entity names and associated automations for all my ZWave devices, and reinstalling the Integration would wipe all that out. So I reverted to my most recent snapshot, and then opened up the /config/.storage/core.config_entries file using the File Editor plugin. Look for the section with the domain “zwave_js”, and change the “use_addon” and “integration_created_addon” lines to both be “false”. Then save and restart HA. Problem solved.
-A
