After reading a Reddit post about zwavejs2mqtt and its superior interface for managing z-wave environments, I decided to switch from zwavejs to zwavejs2mqtt. I installed and configured this add-on and it is working great, however every time I remove the zwavejs addon, it reinstalls itself on the next HA startup.
Here are the supervisor logs that seem to be relevant:
1-03-08 17:53:17 INFO (SyncWorker_7) [supervisor.docker.interface] Stopping addon_core_zwave_js application
21-03-08 17:53:21 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_core_zwave_js application
21-03-08 17:53:21 INFO (SyncWorker_7) [supervisor.docker.interface] Removing image homeassistant/amd64-addon-zwave_js with latest and 0.1.10
21-03-08 17:53:21 INFO (MainThread) [supervisor.addons.addon] Removing add-on data folder /data/addons/data/core_zwave_js
21-03-08 17:53:21 INFO (MainThread) [supervisor.discovery] Delete discovery to Home Assistant zwave_js from core_zwave_js
21-03-08 17:53:21 INFO (MainThread) [supervisor.addons] Add-on 'core_zwave_js' successfully removed
And upon restart:
21-03-08 18:15:13 INFO (SyncWorker_4) [supervisor.docker.interface] Restarting homeassistant/intel-nuc-homeassistant
21-03-08 18:15:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
21-03-08 18:15:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
21-03-08 18:15:20 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-03-08 18:15:28 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/core_zwave_js
21-03-08 18:15:28 INFO (SyncWorker_5) [supervisor.docker.interface] Downloading docker image homeassistant/amd64-addon-zwave_js with tag 0.1.10.
21-03-08 18:15:32 INFO (MainThread) [supervisor.addons] Add-on 'core_zwave_js' successfully installed
21-03-08 18:15:33 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-zwave_js with version 0.1.10
Is there anything I can do to find out what’s happening here?
Did you remove the Z-Wave JS integration? I believe that automatically installs the add-on when it is added when running on Home Assistant OS. If you don’t remove that then I assume it continues to try to do that every restart.
So I don’t have ZWaveJS2MQTT myself which means I can’t confirm this. But based on what I’m reading about it now (and based on the name) I’m pretty sure the ZwaveJS integration isn’t involved. I believe it talks to MQTT and doesn’t talk to HA directly at all.
EDIT: I’m sorry, I stand corrected. It does want you to install in the integration. I guess its just going to keep reinstalling the other add-on. Sorry, that’s annoying.
This turned out to be it. For anyone finding this thread later on, this happened because I chose to use the addon when I installed the integration. I didn’t want to reinstall the integration and have to reconfigure entity IDs, so I edited the /config/.storage/core.config_entries file and changed this to false. Restarted HA and the addon did not come back.
@CentralCommand The zwavejs2mqtt add-on functions perfectly with the zwavejs integration in HA. MQTT output is disabled by default, so it seems to just have the additional functionality of MQTT which can be enabled (and of course the much more mature Z-wave network tools).
I just had this issue too. I solved by removing the integration and adding it back making sure to not check use add-on. All my Entities kept their names. The line in core.config_entries that I saw change was “use_addon” change from true to false.
I ran into this as well, but you don’t need to remove the integration. Just act like you are adding a new integration, choose z-wave JS and click through the options. It will eventually say it aborted because it was already configured, but the new settings you chose will have been saved.