Trying to switch to zwavejs2mqtt from official zwavejs

Hi,

I am following the official guide here to switch Z-Wave - Home Assistant

I disabled (not uninstalled) the integration then for step 3 it says “Install and configure the Z-Wave JS to MQTT add-on, including setting the location of your Z-Wave device and the network security keys.”

I installed the addon but cannot find how to configure it, under configuration tab it states " This add-on does not expose configuration for you to mess with… ". So, I tried start the addon figuring maybe it has a web interface but it does not start and keeps going back to stopped, logs below.

Any ideas, are these docs I am following correct?

Thanks!

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Z-Wave JS to MQTT
 Fully configurable Z-Wave JS to MQTT gateway and control panel; based on Zwavejs2Mqtt
-----------------------------------------------------------
 Add-on version: 0.45.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.4  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.8.2
 Home Assistant Supervisor: 2022.08.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/configuration.sh
cont-init: info: /etc/cont-init.d/configuration.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun zwavejs2mqtt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[12:35:35] INFO: Starting the Z-Wave JS to MQTT...
2022-08-11 12:35:40.110 INFO APP: Version: 6.15.2
2022-08-11 12:35:40.120 INFO APP: Application path:/opt
 ______                       _     ___                  _   _   
|___  /                      (_)   |__ \                | | | |  
   / /_      ____ ___   _____ _ ___   ) |_ __ ___   __ _| |_| |_ 
  / /\ \ /\ / / _` \ \ / / _ \ / __| / /| '_ ` _ \ / _` | __| __|
 / /__\ V  V / (_| |\ V /  __/ \__ \/ /_| | | | | | (_| | |_| |_ 
/_____|\_/\_/ \__,_| \_/ \___| |___/____|_| |_| |_|\__, |\__|\__|
                            _/ |                      | |        
                           |__/                       |_|        
2022-08-11 12:35:40.180 WARN STORE: scenes.json not found
2022-08-11 12:35:40.185 WARN STORE: nodes.json not found
2022-08-11 12:35:40.193 WARN STORE: users.json not found
2022-08-11 12:35:40.274 INFO APP: Listening on port 44920 host 0.0.0.0 protocol HTTP
2022-08-11 12:35:40.514 INFO MQTT: MQTT is disabled
2022-08-11 12:35:40.525 WARN BACKUP: Store backup is disabled
2022-08-11 12:35:40.528 WARN BACKUP: Nvm backup is disabled
[12:35:40] INFO: Starting NGinx...
2022-08-11 12:35:40.534 WARN ZWAVE: Zwave driver not inited, no port configured

Maybe I don’t want to switch, seems those official docs miss out something vital anyway:

So I would need to reinterview all my battery devices, of which I have quite a few…

I can see there is a way of copying the cache files.

My main query here, I have renamed most of my zwave device names and entities to make them more meaningful to me - if I follow the official guide to migrate, then re-interview my battery devices, will they keep the same device and entity names??

Can anyone help with my issues?

The logs look fine to me. You need to go into the z2m Web UI and configure the USB path for the controller, along with the network keys.

But as per my first post the adding just stops running and I can’t get to any Web ui ?

The log you posted doesn’t show it stopping. Do you have more logs? What happens when you click the Web UI button?

Well I tried installing again and this time it stays started so I got access to the Web UI and configured it.

And none of my devices have changed their names which is great, just need to wake my battery devices.

Thanks.

For future reference, you get that error sometimes and you just need to refresh your cache. Most of the time just hold ctrl and refresh.

I did try multiple times, the add-on would start and then stop almost straight away for no apparent reason.

Anyway all good now and thanks for the tip.

It never stopped (the logs show that). I think you just were unfortunate to hit a UI bug.

1 Like