Update docker (as a service) zwave-js-ui

[dxfoxd]

I'm using the docker container service for zwave-js-ui and recently the Home Assistant displayed a message that the "The version of Z-Wave JS Server you are currently running is too old for this version of Home Assistant. Please update the Z-Wave JS Server to the latest version to fix this issue.". I'm using zwave-js-ui: 8.8.4.4f4cd65.

My compose.yml had the following section for this container

 zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=[removed]
      - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
      - TZ=Europe/Amsterdam
    networks:
      - zwave
    devices:
      # Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
      # Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
      - /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_e63df2d83e94eb11adbf36703d98b6d1-if00-port0:/dev/zwave
    volumes:
      #- zwave-config:/usr/src/app/store
    # Or by using local folder
    - ./store:/config/zwave
    ports:
      - "8091:8091" # port for web interface
      - "3000:3000" # port for Z-Wave JS websocket server
networks:
  zwave:
volumes:
  zwave-config:
    name: zwave-config

Tried to update using

sudo docker stop zwave-js-ui
sudo docker pull zwavejs/zwave-js-ui:latest
sudo docker start zwave-js-ui

The pull perfectly downloads and extracts the files, but after starting the container again I still notice the same (old) version number. I believe I'm missing something here, but hours of searching did not bring the solution. I saw an old post stating that I need to remove the old container, but doesn't this also remove all my device settings?

Peter

[kpine]

Need to update via compose.

docker compose pull
docker compose up -d

(or docker-compose for the older version)

https://www.howtogeek.com/devops/how-to-upgrade-docker-containers-to-apply-image-updates/

[dxfoxd]

Right, followed this guide, and now all my devices are gone .... I made a backup before, but when trying to restore no backup files are to be found. Any idea how I can revert this?

[kpine]

What does "all my devices are gone" mean? The network is stored on the controller, so they aren't lost.

You should know where your config files are stored. According to your compose yaml file, it's in the ./store directory, which is relative to the location of the compose file.

[robertsLando]

He used - ./store:/config/zwave as volume, that makes no sense as store data inside container are in /usr/src/app/store

The correct volume would be:

• ./store:/usr/src/app/store

Now the only way is to correct the volume dir in docker compose and restore the backup inside the local store dir

Just to be clear @kpine suggestion about container upgrade is correct, the problem is just you used a wrong volume on your docker-compose @dxfoxd

[dxfoxd]

Thx both! I appreciate your help.

I don’t know what triggered the restore, but yesterday all my devices start showing up after I populated the config with the old security keys. Checking the zwave-js-ui container folder /usr/src/apps/store, only default files were available, custom node names and locations were missing (the file nodes.json was empty).

I really want to prevent loosing my configuration next time, your analysis was right though, I want to have the settings folder OUTSIDE the container or synced with the container. Like I do with HA I want to include the zwave-js-ui config path in a general backup process. Like HA, all configuration is stored outside the container.

In my configuration the folder /config/zwave is created (in folder /home/pi/), but nothing is stored there.
Would I accomplish this by using

volumes:
  - ./config/zwave:/usr/src/app/store

?

[robertsLando]

Would I accomplish this by using

Yeah