Which upgrade path recommended from 2022-1/Buster?

[Domoberry]

Hi Forum,
After getting zwave-js-ui working to replace OZW, I have paved the way for the next upgrade steps.
I would appreciate the forum's view with respect to the optimal sequence wanting go from:
- today: 2022.1 on RPI3b Buster
- target: 2023.1 on RPI3b Bullseye
First 2022.1 -> 2022.2 -> 2023.1 then Buster -> Bullseye or another sequence? Python risks?
(Is it correct that post on 'upgrading to 2022.2 are not visible anymore and should I hence move from 2022.1 directly 2023.1?)
Best to setup username/password and trusted networks now?
I'm also reading the various related posts, but the answer might be simple..
For sure step 0 is making a backup image of the SD card
On an RPI3b Buster, I'm currently I'm using zwave-js-ui (docker compose) with MQTT AD (mosquitto) , some mod-bus devices, normal MQTT client (for Tasmota devices), Nefit EMS-ESP, Nefit Easy /Nefit server, P1 smartmeter USB, Hue, Nest (old interface), Solar Edge via WebAPI and some LUA and DzVents scripts. Running Python 2.7.16. All runs quite well as far as I can see.

[Domoberry]

As usual... asking the question is part of answering it.
In this case, I just went ahead 'no risk no fun' and upgraded on Buster from Domoticz 2022.1 to 2023.1.

A Smooth Ride & Kudos for the team !!

- read the 2023.1 change log and the main post on this forum (https://domoticz.com/forum/viewtopic.php?p=299227)
- did the usual update/upgrade on the existing RPI system
- created the various Domoticz backups (database, RPI folder, and RPI SD card)
- updated to Domoticz 2023.1 using the GUI
- need to enter username and password
- clear browser cache (https://www.domoticz.com/wiki/Browser_Cache
- added local network (192.168.0.*) as trusted network in Domoticz (no need to enter password - if ok with your use case) (https://www.domoticz.com/wiki/Security
- add the needed Domoticz menus for user 'admin' (and other users if created)
- specific in my case:
- correct the port for the Modbus hardware (it was wrong for some reason)
- P1 USB smart meter and Solar Edge web interface had some new devices

Next is Bullseye upgrade.

[TurboX]

Hello @Domoberry,

I have the same thing to do but on Pi4. I can't update ZwaveJSui anymore as it require Bullseye.
I had firstly tried to update buster to bullseye but it was a disaster.

From your experience I will try to update Domoticz, then bullseye and then ZwaveJSui.
I'm not really confident

[Domoberry]

I did zwave-js-ui using Docker compose on Buster with Domoticz 2022-1. Which was a challenge (ar least for me), but I got it eventually running ok; it actually still is running per today. I still need to do the Buster to Bullseye. People on the forum recommended however to do Bullseye before zwave-js-ui on docker compose.
Now reading the various posts on the Buster/Bullseye upgrade and decide on best applicable approach

[mgugu]

I have the same thing to do but on Pi4. I can't update ZwaveJSui anymore as it require Bullseye.

You can still use buster and continue to update zwavejs-ui provided you install libseccomp2:

Code: Select all

sudo apt update
sudo apt install libseccomp2 -t buster-backports

[TurboX]

Oh ! Thanks @mgugu, i will try that.

[TurboX]

Hello,

Unfortunately after apt upgarde/updateI have this error:

Code: Select all

E: The value 'buster-backports' is invalid for APT::Default-Release as such a release is not available in the sources

[mgugu]

Hello,

Unfortunately after apt upgarde/updateI have this error:

Code: Select all

E: The value 'buster-backports' is invalid for APT::Default-Release as such a release is not available in the sources

You can also use dpkg (I used that):

Code: Select all

wget http://ftp.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.4-1+b1_armhf.deb
sudo dpkg -i libseccomp2_2.5.4-1+b1_armhf.deb

[TurboX]

Hello,

Sorry for very late reply but as each time I try do update something it fail I was waiting for the end of the heating at home and a large time availabilty in case of problem and Today was THE day.

So, I have try your command but it fails. The corrected command now is :

Code: Select all

wget http://ftp.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.4-1+b3_armhf.deb
sudo dpkg -i libseccomp2_2.5.4-1+b3_armhf.deb

After that in the Zwavejs portainer stack , I have just rename the container and "update" the stack. It replace the old container with the new one up to date .

Code: Select all

version: '3.7'
services:
  zwavejs2mqtt:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=XXXXXXX
      - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
      # Uncomment if you want logs time and dates to match your timezone instead of UTC
      # Available at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
      #- TZ=America/New_York
    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-0658_0200-if00:/dev/zwave'
    volumes:
      - zwave-config:/usr/src/app/store
    ports:
      - '8091:8091' # port for web interface
      - '3000:3000' # port for Z-Wave JS websocket server
networks:
  zwave:
volumes:
  zwave-config:
    name: zwave-config

Then as I feel a lucky day, I have update my ZigbeeforDomoticz plugin and ... Domoticz 2022.1 to 2023.1 It's incredible all works fine !
Now the only thing to do is to switch to Bullseye but I don't know how to start so I will be later.

Thanks @mgugu !

[gizmocuz]

So yes, using docker compose for mqtt/zigbee2mqtt/zwavejsui is a very good idea (and highly recommended)
One thing I would change in your docker-compose.yml is your volume.
If you use

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

(notice the ./)

It will create a folder 'zwave-config' in your docker compose project folder where everything is stored.
Backup? Just make a backup of this folder, restore or test another version? restore or make a copy

Migrate to a new machine, copy your docker folders

Installing docker compose is very easy

Code: Select all

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