Domoticz

i converted my pi 3B with this wiki https://wiki.domoticz.com/Zwave-JS-UI
I get a message that there is a new version of zwave-js-ui, I am now running 9.26.0 and the message shows this version as 9.28.0
how does my zwave-js-ui go to this version?

I assume you installed this with docker compose?
If yes, you can update (if you need to...) when you go to the docker compose folder (for example /opt/zwavejs) and issue the below command:

docker compose pull && docker compose up --force-recreate --build -d && docker image prune -f

ok thanks
is this necessary to update to a newer version?
and why is this so difficult?

teo1966 wrote: Tuesday 17 December 2024 15:46 is this necessary to update to a newer version?

in general: don't fix if it ain't broken. but a new version might support newer devices.

teo1966 wrote: Tuesday 17 December 2024 15:46 and why is this so difficult?

What's so difficult about that single line?

I made 1 docker compose file for my containers (influxdb, grafana, zwave-js-ui, homebridge an home assistant)

And this single commmand (docker compose pull && docker compose up --force-recreate --build -d && docker image prune -f) updates all docker containers...

teo1966 wrote: Wednesday 11 December 2024 20:53 i converted my pi 3B with this wiki https://wiki.domoticz.com/Zwave-JS-UI
I get a message that there is a new version of zwave-js-ui, I am now running 9.26.0 and the message shows this version as 9.28.0
how does my zwave-js-ui go to this version?

my mistake, i used this manual from andrehj see
viewtopic.php?t=39292&start=120
the command docker compose pull && docker compose up --force-recreate --build -d && docker image prune -f
doesn't work, I don't think docker is being used

Then google how to update a snap container that runs as an service. A snap container should update automatically but not when running.

found this
https://snapcraft.io/docs/managing-updates

To see your version and the available updates use :

sudo snap info zwave-js-ui

To do the update to the latest stable version use :

sudo snap refresh zwave-js-ui

harrykausl wrote: Thursday 19 December 2024 17:51 To see your version and the available updates use :

sudo snap info zwave-js-ui

To do the update to the latest stable version use :

sudo snap refresh zwave-js-ui

thank you for the help

pi@raspberrypi:~ $ sudo snap info zwave-js-ui
name: zwave-js-ui
summary: Full-featured Z-Wave Control Panel and MQTT Gateway.
publisher: Giaever.online (giaever-online)
store-url: https://snapcraft.io/zwave-js-ui
license: MIT
description: |
**Zwave JS UI**: Fully configurable Zwave to MQTT Gateway and Control Panel.

**IMPORTANT:** Read about the different release-cycles in the end section «releases in `latest`».

**If you're happy with this snap package, please consider to make a donation**

Full-featured Z-Wave Control Panel and MQTT Gateway compatible with all known 500 and
700 series Z-Wave controller hardware adapters, Z-Wave JS runs on almost anything with
a little bit of computing power and a serial port.

**Main features**
- Control Panel UI: Directly control your nodes and their values from the UI, including:
- Nodes management: Add, remove, and configure all nodes in your Z-Wave network
- Firmware updates: Update device firmware using manufacturer-supplied firmware files
- Groups associations: Add, edit, and remove direct node associations
- Z-Wave JS Exposed: Provides full-access to Z-Wave JS's APIs
- Full-Featured Z-Wave to MQTT Gateway: Expose Z-Wave devices to an MQTT broker in a
fully configurable manner
- Secured: Supports HTTPS and user authentication
- Scene Management: Create scenes and trigger them by using MQTT apis (with timeout
support)
- Debug Logs in the UI: See debug logs directly from the UI
- Access Store Files in the UI: Access the files are stored in the persistent store
folder directly from the UI
- Network Graph: Provides a beautiful map showing how nodes are communicating with the
controller
- Supports the Official Home Assistant Integration: Can act as the backend driver for
the official Home Assistant integration, using the same driver and socket server as
the official addon
- Supports Home Assistant Discovery via MQTT: In lieu of the official integation, can
be used to expose Z-Wave devices to Home Assistant via MQTT discovery.
- Supported by Domoticz (beta 2021.1): Using MQTT Autodiscovery.
- Automatic/Scheduled backups: Scheduled backup of NVM and store directory. It's also
possible to enable automatic backups of NVM before every node inclusion/exclusion/
replace, this ensures to create a safe restore point before any operation that can
cause a network corruption.

**Additions with the snap**
- Command to read the log from the terminal independent of if you're logging to file
or not
- Plugs for the `code-server` snap, if you want a full-fledged editor experience for
the «store-folder»

**Auto-connections**
- `raw-usb`: To access USB devices, such as Z-wave controller dongles
- `hardware-observe`: To observe your system for devices, to easily find them in the UI

**Note:** None of these connections are necessary to run the app, so you can disconnect
them as you like, but please note that it might change the experience within the software.

**Issues**

If your issue is with
- the UI/front-end, report them at https://github.com/zwave-js/zwave-js-ui/issues
- the driver, report them at https://github.com/zwave-js/node-zwave-js/issues

Make sure you have set the log level to `DEBUG` for the respective unit and that you are
logging to file, and attach it with your issue.

If you're not sure, just report it within any of the above, but attach logs for both
packages. It will be transferred if you reported it within the wrong tracker.

**Issues with the snap package**

Report it with https://github.com/giaever-online-iot/z ... -ui/issues

**Releases in `latest`**

This is how we use the different of channels in the `latest` track,
to give the user a chance to choose how often they want updates.

- `latest/stable`: Latest version of the last *major* release. Will
only update once per major release and most likely by the end of
that release cycle. E.g when there is a new version `b.a.a` then
version `a.b.c` will be will be available.

- `latest/candidate`: Latest minor or patch release of latest major
release. E.g when version `a.b.c` changes to `a.b.d` or `a.c.a`, then
version `a.b.d` or `a.c.a` will be available. Consider this rolling
releases.

- `latest/edge` and `latest/edge/dev`: Every build (including tests) might be pushed to these
channels.
commands:
- zwave-js-ui.disable
- zwave-js-ui.enable
- zwave-js-ui.exec
- zwave-js-ui.help
- zwave-js-ui.restart
services:
zwave-js-ui: simple, enabled, active
snap-id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
tracking: v9.26/stable
refresh-date: 27 days ago, at 12:12 CET
channels:
v9.27/stable: v9.27.8 2024-12-03 (515) 147MB -
v9.27/candidate: ↑
v9.27/beta: ↑
v9.27/edge: ↑
latest/stable: v9.27.8 2024-12-18 (515) 147MB -
latest/candidate: v9.28.0 2024-12-18 (518) 148MB -
latest/beta: ↑
latest/edge: v9.28.0 2024-12-12 (518) 148MB -
v9.26/stable: v9.26.0 2024-11-11 (499) 145MB -
v9.26/candidate: ↑
v9.26/beta: ↑
v9.26/edge: ↑
v9.25/stable: v9.25.0 2024-11-11 (496) 145MB -
v9.25/candidate: ↑
v9.25/beta: ↑
v9.25/edge: ↑
v9.24/stable: v9.24.0 2024-11-07 (493) 145MB -
v9.24/candidate: ↑
v9.24/beta: ↑
v9.24/edge: ↑
v9.23/stable: v9.23.0 2024-10-14 (485) 143MB -
v9.23/candidate: ↑
v9.23/beta: ↑
v9.23/edge: ↑
v9.22/stable: v9.22.0 2024-10-14 (481) 143MB -
v9.22/candidate: ↑
v9.22/beta: ↑
v9.22/edge: ↑
v9.21/stable: v9.21.1 2024-10-14 (473) 142MB -
v9.21/candidate: ↑
v9.21/beta: ↑
v9.21/edge: ↑
v9.20/stable: v9.20.0 2024-10-14 (476) 142MB -
v9.20/candidate: ↑
v9.20/beta: ↑
v9.20/edge: ↑
v9.19/stable: v9.19.0 2024-09-29 (459) 142MB -
v9.19/candidate: ↑
v9.19/beta: ↑
v9.19/edge: ↑
v9.18/stable: v9.18.1 2024-09-08 (453) 142MB -
v9.18/candidate: ↑
v9.18/beta: ↑
v9.18/edge: ↑
v9.17/stable: v9.17.0 2024-08-31 (447) 142MB -
v9.17/candidate: ↑
v9.17/beta: ↑
v9.17/edge: ↑
v9.16/stable: v9.16.4 2024-08-08 (445) 142MB -
v9.16/candidate: ↑
v9.16/beta: ↑
v9.16/edge: ↑
v9.14/stable: v9.14.6 2024-07-17 (424) 141MB -
v9.14/candidate: ↑
v9.14/beta: ↑
v9.14/edge: ↑
v9.13/stable: v9.13.4 2024-06-17 (399) 139MB -
v9.13/candidate: ↑
v9.13/beta: ↑
v9.13/edge: ↑
v9.12/stable: v9.12.0 2024-05-30 (384) 139MB -
v9.12/candidate: ↑
v9.12/beta: ↑
v9.12/edge: ↑
v9.11/stable: v9.11.1 2024-05-30 (362) 138MB -
v9.11/candidate: ↑
v9.11/beta: ↑
v9.11/edge: ↑

installed: v9.26.0 (499) 145MB -


pi@raspberrypi:~ $ sudo snap refresh zwave-js-ui
snap "zwave-js-ui" has no updates available
pi@raspberrypi:~ $

I remember the days of "Update Now" buttons in the UI.

Since you did not install docker compose the normal way (see our wiki) and using snaps? This indeed complicate things
You could make a bash script that you can execute in a docker compose folder to update it.
Very easy this way

And as mentioned, if you don't miss anything, keep it running and don't update if you don't need to.

gizmocuz wrote: Saturday 21 December 2024 19:03 Since you did not install docker compose the normal way (see our wiki) and using snaps? This indeed complicate things
You could make a bash script that you can execute in a docker compose folder to update it.
Very easy this way

And as mentioned, if you don't miss anything, keep it running and don't update if you don't need to.

have you een howto from snap to docker compose ?

This is how you should install docker compose

sudo apt-get update && sudo apt-get upgrade

curl -fsSL test.docker.com -o get-docker.sh && sh get-docker.sh
sudo usermod -aG docker ${USER}
sudo systemctl enable docker
sudo reboot

If I want to switch to Docker on my PI3b, I can have it installed at the same time and keep the data and then remove Snap

You are on the latest/stable channel which tracks the "Latest version of the last *major* release" so you are on the right release for it.

If you want the "Latest minor or patch release of latest major release" then switch the channel:
The different channels are described in the output of `sudo snap info zwave-js-ui` (see your own post above)

with this command sudo snap refresh zwave-js-ui --channel=latest/candidate I went from 9.26.0 to 9.31.2 without any problems
I now saw the message new version available 10.1.3 this command no longer works sudo snap refresh zwave-js-ui --channel=latest/candidate anyone an idea how to adjust this command

Version 10.1.3 is currently on the latest/edge channel. You can just wait until it makes it to latest/candidate or if you want to switch now:

sudo snap refresh zwave-js-ui --channel=latest/edge

Keep in mind that the earlier channels are not considered stable yet but this is how the community helps find bugs.

I wanted an update again, but it's not working. Does anyone have any ideas?


pi@raspberrypi:~ $ sudo snap info zwave-js-ui
name: zwave-js-ui
summary: Full-featured Z-Wave Control Panel and MQTT Gateway.
publisher: Giaever.online (giaever-online)
store-url: https://snapcraft.io/zwave-js-ui
license: MIT
description: |
**Zwave JS UI**: Fully configurable Zwave to MQTT Gateway and Control Panel.

**IMPORTANT:** Read about the different release-cycles in the end section «releases in `latest`».

**If you're happy with this snap package, please consider to make a donation**

Full-featured Z-Wave Control Panel and MQTT Gateway compatible with all known 500 and
700 series Z-Wave controller hardware adapters, Z-Wave JS runs on almost anything with
a little bit of computing power and a serial port.

**Main features**
- Control Panel UI: Directly control your nodes and their values from the UI, including:
- Nodes management: Add, remove, and configure all nodes in your Z-Wave network
- Firmware updates: Update device firmware using manufacturer-supplied firmware files
- Groups associations: Add, edit, and remove direct node associations
- Z-Wave JS Exposed: Provides full-access to Z-Wave JS's APIs
- Full-Featured Z-Wave to MQTT Gateway: Expose Z-Wave devices to an MQTT broker in a
fully configurable manner
- Secured: Supports HTTPS and user authentication
- Scene Management: Create scenes and trigger them by using MQTT apis (with timeout
support)
- Debug Logs in the UI: See debug logs directly from the UI
- Access Store Files in the UI: Access the files are stored in the persistent store
folder directly from the UI
- Network Graph: Provides a beautiful map showing how nodes are communicating with the
controller
- Supports the Official Home Assistant Integration: Can act as the backend driver for
the official Home Assistant integration, using the same driver and socket server as
the official addon
- Supports Home Assistant Discovery via MQTT: In lieu of the official integation, can
be used to expose Z-Wave devices to Home Assistant via MQTT discovery.
- Supported by Domoticz (beta 2021.1): Using MQTT Autodiscovery.
- Automatic/Scheduled backups: Scheduled backup of NVM and store directory. It's also
possible to enable automatic backups of NVM before every node inclusion/exclusion/
replace, this ensures to create a safe restore point before any operation that can
cause a network corruption.

**Additions with the snap**
- Command to read the log from the terminal independent of if you're logging to file
or not
- Plugs for the `code-server` snap, if you want a full-fledged editor experience for
the «store-folder»

**Auto-connections**
- `raw-usb`: To access USB devices, such as Z-wave controller dongles
- `hardware-observe`: To observe your system for devices, to easily find them in the UI

**Note:** None of these connections are necessary to run the app, so you can disconnect
them as you like, but please note that it might change the experience within the software.

**Issues**

If your issue is with
- the UI/front-end, report them at https://github.com/zwave-js/zwave-js-ui/issues
- the driver, report them at https://github.com/zwave-js/node-zwave-js/issues

Make sure you have set the log level to `DEBUG` for the respective unit and that you are
logging to file, and attach it with your issue.

If you're not sure, just report it within any of the above, but attach logs for both
packages. It will be transferred if you reported it within the wrong tracker.

**Issues with the snap package**

Report it with https://github.com/giaever-online-iot/z ... -ui/issues

**Releases in `latest`**

This is how we use the different of channels in the `latest` track,
to give the user a chance to choose how often they want updates.

- `latest/stable`: Latest version of the last *major* release. Will
only update once per major release and most likely by the end of
that release cycle. E.g when there is a new version `b.a.a` then
version `a.b.c` will be will be available.

- `latest/candidate`: Latest minor or patch release of latest major
release. E.g when version `a.b.c` changes to `a.b.d` or `a.c.a`, then
version `a.b.d` or `a.c.a` will be available. Consider this rolling
releases.

- `latest/edge` and `latest/edge/dev`: Every build (including tests) might be pushed to these
channels.
commands:
- zwave-js-ui.disable
- zwave-js-ui.enable
- zwave-js-ui.exec
- zwave-js-ui.help
- zwave-js-ui.restart
services:
zwave-js-ui: simple, enabled, active
snap-id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
tracking: latest/edge
refresh-date: today at 10:26 CEST
channels:
v11.1/stable: v11.1.0 2025-08-29 (612) 130MB -
v11.1/candidate: ↑
v11.1/beta: ↑
v11.1/edge: ↑
latest/stable: v11.1.0 2025-08-29 (612) 130MB -
latest/candidate: v11.2.1 2025-08-29 (620) 130MB -
latest/beta: ↑
latest/edge: v11.2.1 2025-08-28 (620) 130MB -
v11.2/stable: –
v11.2/candidate: v11.2.1 2025-08-29 (620) 130MB -
v11.2/beta: ↑
v11.2/edge: ↑
v11.0/stable: v11.0.1 2025-08-09 (609) 130MB -
v11.0/candidate: ↑
v11.0/beta: ↑
v11.0/edge: ↑
v10.11/stable: v10.11.0 2025-08-09 (603) 127MB -
v10.11/candidate: v10.11.0 2025-07-31 (603) 127MB -
v10.11/beta: ↑
v10.11/edge: ↑
v10.10/stable: v10.10.0 2025-07-31 (599) 128MB -
v10.10/candidate: ↑
v10.10/beta: ↑
v10.10/edge: ↑
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
v9.11/candidate: ↑
v9.11/beta: ↑
v9.11/edge: ↑
installed: v10.9.0 (587) 151MB -
pi@raspberrypi:~ $
pi@raspberrypi:~ $
pi@raspberrypi:~ $
pi@raspberrypi:~ $ sudo snap refresh zwave-js-ui
2025-09-10T10:34:20+02:00 INFO Waiting for "snap.zwave-js-ui.zwave-js-ui.service" to stop.
error: cannot perform the following tasks:
- Run post-refresh hook of "zwave-js-ui" snap if present (run hook "post-refresh":
-----
++ zui_settings_file w
++ realpath -e /var/snap/zwave-js-ui/620/settings.json
++ test_perm w
++ read -r F
++ test -w /var/snap/zwave-js-ui/620/settings.json
++ echo /var/snap/zwave-js-ui/620/settings.json
++ return 1
++ return 1
+ ZUI_SETTINGS=/var/snap/zwave-js-ui/620/settings.json
+ '[' 1 -ne 0 ']'
+ echo 'Cannot read/write to settings'
Cannot read/write to settings
+ exit 1
-----)
pi@raspberrypi:~ $ sudo snap refresh zwave-js-ui --channel=latest/candidate
error: cannot perform the following tasks:
- Run post-refresh hook of "zwave-js-ui" snap if present (run hook "post-refresh":
-----
++ zui_settings_file w
++ realpath -e /var/snap/zwave-js-ui/620/settings.json
++ test_perm w
++ read -r F
++ test -w /var/snap/zwave-js-ui/620/settings.json
++ echo /var/snap/zwave-js-ui/620/settings.json
++ return 1
++ return 1
+ ZUI_SETTINGS=/var/snap/zwave-js-ui/620/settings.json
+ '[' 1 -ne 0 ']'
+ echo 'Cannot read/write to settings'
Cannot read/write to settings
+ exit 1
-----)
pi@raspberrypi:~ $ sudo snap refresh zwave-js-ui --channel=latest/edge
error: cannot perform the following tasks:
- Run post-refresh hook of "zwave-js-ui" snap if present (run hook "post-refresh":
-----
++ zui_settings_file w
++ realpath -e /var/snap/zwave-js-ui/620/settings.json
++ test_perm w
++ read -r F
++ test -w /var/snap/zwave-js-ui/620/settings.json
++ echo /var/snap/zwave-js-ui/620/settings.json
++ return 1
++ return 1
+ ZUI_SETTINGS=/var/snap/zwave-js-ui/620/settings.json
+ '[' 1 -ne 0 ']'
+ echo 'Cannot read/write to settings'
Cannot read/write to settings
+ exit 1
-----)
pi@raspberrypi:~ $

see https://github.com/giaever-online-iot/z ... /issues/71

As mentioned above, use it via docker compose.
Much easier to upgrade, and no system dependencies.
This is exactly the reason to use docker compose