QUESTION - Migrating to Z-Wave JS UI Add-On - Devices Unavailable

ISSUE:

Attempting to migrate from the official Z-Wave JS to UI version using instructions here and here. Installation proceeds normally and devices are discovered. There are no errors in the logs. However, the devices show as “unavailable” in my lovelace dashboard.

QUESTION:
Do the device entity names change in the UI version, or should that information be preserved? More to the point, do I need to go through all my automations and lovelace cards and update them, or should all that just work after the migration? It’s the difference between an onerous day+ long project and a quick 10 minute setup.

They’ll be preserved

no, they should just work. But you’re switching to a “new” controller, so you’ll have to wake everything up again.

Is Zwave JS UI running?

1 Like

Yes. Zwave JS UI is running (green light). I watched the debug log as the devices were discovered. It took about 10-20 minutes and then stopped after devices were discovered. I also switched back and forth to the device list as it updated, and could see the devices updating. So, I believe it’s working. I did disable the official Z-Wave JS, according to the instructions on the HA setup page. But, on the JS UI Github setup page, they didn’t mention doing that. So, I’m not exactly clear whether I’m supposed to leave the official JS running.

They make it pretty clear what you have to do with the other addon

1 Like

Yes. That’s exactly the line I saw in those instructions. Okay… I’ll go ahead and uninstall it. I’m pretty sure I didn’t get step 4 right either. I don’t have the option to add the UI again in my add-ons. I can stop it and start it.

Step 4 is re-configure the integration (by adding it again), not the add-on. Nothing will work until you reconfigure the integration to connect to ZUI.

1 Like

You’re not fully reading the bullet. It’s not talking about the addon, it’s talking about the integration.


The addon runs the stick. The addon is in the addons area.

Open your Home Assistant instance and show your Supervisor dashboard.


The integration talks to the addon. The integration is in the integration area.

Open your Home Assistant instance and show your integrations.


Make note of add-on vs integration when it’s talking about it in those bullets.

1 Like

Damn it. I clicked “delete” under the Z-Wave JS integration instead of “uninstall” in the add-on. Now all those devices are completely gone, not just unavailable. Did I just delete them from my stick? I did backup the stick yesterday. And, have a full HA system backup from this morning.

No. You removed them from HA. Unless you have a backup, just install the integration as described in the add-on docs. You’ll have to rename everything as it was before.

1 Like

I have an AM full system backup. Will restore from there.

After restoring HA from a backup and re-installing the UI add-on, all is well. Turns out… not explicitly botching every step along the way seems to work. Thanks guys! :crazy_face:

Hi I followed the instructions:

  1. Disabled the existing Z-wave.
  2. Copied over all keys, S0 legacy key, access control key… etc
  3. Installed and started the z-wave js addon, added it to the side bar, when into options and copied over the network keys plus set the right tty device.
  4. Now it says to “add the z-wave integration” again - so I’m guessing I try to add a new one (with the old integration disabled), I uncheck the supervisor option, it then asks me for a websocket address, it is defaulted to ws://localhost:3000. I try to click submit but it cannot connect.

I go to the z-wave js options and see that the ws is already enabled, on port 3000, I changed the host to localhost and to 127.0.0.1, but still it cannot connect. How do I proceed?

I managed to get it to work by setting 3000 in the Network configuration option of the Add on.

It caused the addon to restart.

What does option actually do that’s different from the setting of the port of the Zwave server.

I had to go to http://homeassistant.local:8123/hassio/addon/a0d7b954_zwavejs2mqtt/config to set it.

But I don’t understand the option.