Moving from Docker setup to HAOS server

Configuration Z-Wave
1

I am currently running Z-Wave JS UI under Docker, which is connected to Z-Wave JS integration on my HAOS server with WS.
What’s the best approach to move the Docker instance over to the HAOS server, keeping the Z-Wave JS UI features?

Thanks!

2

You can use the Backup and Restore functionality from the Z-Wave JS UI Store page.

3

Thank you! I had missed the gear icon for backup & restore. Will I need to change the Aeotec Gen 5 stick mapping in the config to /dev/serial/by-id/usb-06… config? I want to avoid creating duplicate entities if possible

I already have the Z-Wave JS integration install, but it currently points to the Docker server, so I guess I will need to change that to ws://localhost:3000?

Finally, I am bit confused between the Z-Wave JS supervisor add-on and the Z-Wave JS UI. I’m used to the UI on Docker, so I would like to have that on HAOS if possible.

Thanks!

4

No, using by-id path is persistent, HAOS supports it as well. For a Aeotec Gen5, you better disable soft-reset in the ZUI Z-wave settings if you are using HAOS under a Virtual Machine.

I already have the Z-Wave JS integration install, but it currently points to the Docker server, so I guess I will need to change that to ws://localhost:3000?

I would first disable the integration when you make the switch, to avoid any churn. Then you can skip to step 4 in these instructions: https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on, to reconfigure using the URL the add-on docs specify.

Finally, I am bit confused between the Z-Wave JS supervisor add-on and the Z-Wave JS UI. I’m used to the UI on Docker, so I would like to have that on HAOS if possible.

If you want to continue with the same experience you should use the Z-Wave JS UI add-on, which I assumed you were going to. Otherwise, the restore method using the official add-on would require different instructions.

5

Fantastic! Here are the steps I followed for future reference:

  1. Disabled the Z-Wave JS Integration.
  2. Installed the Z-Wave JS UI Community Add-on.
  3. Moved the Aeotec controller to the HAOS Server.
  4. Started the Z-Wave JS UI add-on and restored the backup from the Docker instance.
  5. Restarted the Z-Wave JS UI add-on and got an error complaining that it couldn’t find the controller.
  6. Went to Settings, Z-Wave and selected the controller from the Serial Port drop-down list. All devices appeared after a few seconds.
  7. Tried to re-add the Z-Wave integration as per item 4 you linked to, but got an error saying it was already configured. So, I just enabled the integration and it picked up the connection setting automatically.

Many thanks for your help and prompt replies :+1:

Pat

2 Likes
6

Was the path different in the Docker setup? E.g. you were mapping the host path to /dev/zwave?

Yep, a bit confusing but that’s normal. Just confirms the configuration is using the same Z-Wave network, thus an indication of success actually.

7

Yes, I was mapping the by-id port in docker-compose to /dev/zwave, so that is what was restored. The Serial Port drop-down listed the correct by-id port which was nice.

Yes, it was just being too clever for me :slight_smile: Nice to see how well it all worked though. I had over-thought the process, it literally only took a couple of minutes to do the transfer.

1 Like