Want to migrate HA w/Zwave-js from Rpi to Docker image

[tamorgen (Tim)]

Good day all,
I’m considering migrating my Home Assistant installation from a RPI5 to a Intel NUC that I’ve move a bunch of my other home apps to. I know the main process of installing HA on a NUC is straight forward with Docker, however, from my understanding Add-Ons cannot be migrated. Add-ons, such as Zwave-JS.

My understanding is I would need to install a docker container of Zwave-JS on my NUC. Is there a way to do this and keep all my existing Zwave devices, without having to go through the whole discovery process again? Having to do this would be a major undertaking and I don’t want to have to rewrite all my automations and dashboards.

Thanks for any advice in advance.

[juergenjw (Jürgen W.)]

I’m running zwave-js in a docker container and my docker-compose.yml file is a s follows:

services:
  zwavejs2mqtt:
    container_name: zwavejs2mqtt
    image: zwavejs/zwavejs2mqtt:latest
    restart: unless-stopped
    privileged: true
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=mysupersecretkey
      - TZ=Europe/Berlin # uncomment and edit to match you timezone if you want logs time and dates to match your timezone instead of UTC.
    networks:
      - zwave
    devices:
      - /dev/ttyACM0:/dev/ttyACM0
    volumes:
      - /media/data/docker-volumes/zwave2mqtt:/usr/src/app/store
    ports:
      - 8091:8091 # port for web interface
      - 3000:3000 # port for zwave-js websocket server
networks:
  zwave: null

I don’t know how your HA add-on is storing the device information, but on my volume mapping …zwave2mqtt i have several directories and files that i would try to migrate.

You might try to find these files on your installation.

[freshcoast]

If you are currently using the core Z-Wave JS add-on, you can follow the migration guide, but instead of using the add-on you’d be using your own installation via Docker. https://zwave-js.github.io/zwave-js-ui/#/getting-started/docker

The export and import of the existing Z-Wave JS driver cache would be the same, as well as the re-configuration of the integration (pointing to your Docker installation URL, instead of the add-on). Those are the important steps for preserving your existing configuration.

Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community)

Introduction This guide describes how to switch from the Z-Wave JS official add-on to the Z-Wave JS UI HA Community add-on, without losing any downtime caused by the re-interviewing of nodes. In this guide, Z-Wave JS UI will henceforth be abbreviated as ZUI. Who is this guide for? This guide is for HAOS add-on users who have already installed the official Z-Wave JS add-on and the companion Z-Wave integration, and desire extra functionality that isn’t provided by HA, such as: Adding and remov…

If you are currently using the community Z-Wave JS UI add-on, you can simply use the Backup and Restore functionality on the Store page.