Domoticz upcoming beta/release and OpenSSL 3.0

[waltervl]

Docker is not that resource heavy at all. So running Domoticz in a Docker container is no problem.
And if you use docker compose updating all containers can be done in one single command line as indicated on the docker wiki page.

[gizmocuz]

And you can also install 'Dockge' (in a docker compose container of course!) where you can central manage all your docker compose containers, as well as creating them.

As Walter mentioned, docker is not that resource heave at all, it runs almost natively. (not on a mac)

It also keeps your system clean, you can backup/transfer it easily to another machine, and there are no system dependencies.

Setup of a application (if it is Domoticz, pihole, plex or whatever) is done in minutes!

And almost any application has a docker variant and documentation how to setup.

Give it a few hours to train yourself with it, start with compose files first, next use DockGE, try starting simple
Learn how to convert docker command line to docker compose files (you can do this with DockGE as well)
Maybe start with installing DockGE

To install docker compose issue

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

[Varazir]

And you can also install 'Dockge' (in a docker compose container of course!) where you can central manage all your docker compose containers, as well as creating them.

As Walter mentioned, docker is not that resource heave at all, it runs almost natively. (not on a mac)

It also keeps your system clean, you can backup/transfer it easily to another machine, and there are no system dependencies.

Setup of a application (if it is Domoticz, pihole, plex or whatever) is done in minutes!

And almost any application has a docker variant and documentation how to setup.

Give it a few hours to train yourself with it, start with compose files first, next use DockGE, try starting simple
Learn how to convert docker command line to docker compose files (you can do this with DockGE as well)
Maybe start with installing DockGE

To install docker compose issue

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

Docker is not that resource heavy at all. So running Domoticz in a Docker container is no problem.
And if you use docker compose updating all containers can be done in one single command line as indicated on the docker wiki page.

Going to buy new SD card and install raspbian os on it.
Domoticz backup folder going to be the Storage outside the docker so I can mount it to my NAS as now I guess.

[WilcoEHV]

Hi,
After reading this post i found out i'm on Raspberry OS 11 (Bullseye).
I want to upgrade and found this on raspberrypi.com;

Upgrade your operating system to a new major version
To update the operating system to a new major release on your Raspberry Pi, image a second SD card with the new release. Use a USB SD card reader or network storage to copy files and configuration from your current installation to the new SD card. Then, swap the new SD card into the slot on your Raspberry Pi, and boot.

Is there any way to upgrade from the command promt (and how)?
If it has to be done as described above; do i need to drag all the contents of the old sd card to the new sd card?
If not; what files?

[waltervl]

There is an OS update instruction link for RPi in the last sentence of the first post of this topic.

[Toulon7559]

Sure some functions will depend on a related version of OpenSSL.

But plenty of userprograms probably[?] will never touch it.

is a hint possible what kind of functions will certainly need the shift to OpenSSL3.0, and which not?
Or a hint to some description dealing with that aspect?

[waltervl]

Sure some functions will depend on a related version of OpenSSL.

But plenty of userprograms probably[?] will never touch it.

is a hint possible what kind of functions will certainly need the shift to OpenSSL3.0, and which not?
Or a hint to some description dealing with that aspect?

The thing is Domoticz 2025.1 beta needs openssl3 if you use it or not.... So if you want to use Domoticz 2025.1 beta and later 2025.2 stable you need an OS that has openSSL3 or use a Docker container. It is that simple.

[roblom]

I accidentally pressed update and due to the missing openssl 3 the update failed but now Domoticz won't start anymore.
I'm using a Raspberry Pi 2 model b and if I'm right this isn't able to ruin the required Debian version which includes openssl 3. Is that correct?
If so, is it possible to revert back to the previous Domoticz (and if so, how?) Because I need some time to buy new hardware and install the required Debian version on it.

[waltervl]

Luckily Domoticz creates a full backup when updating so you can restore to the old situation. See the wiki for instructions: https://wiki.domoticz.com/Raspberry_Pi# ... ect_update

[gizmocuz]

@roblom,

Why would you say that you can't use the latest Raspbian? I am sure you had a look here

https://www.raspberrypi.com/software/operating-systems/

"All Raspberry Pi models"

And you also followed the link from the first post to update your system?

[roblom]

Please note that I'm no programmer and only have basic skills regarding this. So the page from the link on the first post here does look far from easy for me.

I thought that the RPi 2b had an ARM processor that only support a Debian version that was to old to work with Domoticz. But looking at your reaction it seems that's incorrect.

So update everything seems the way to go but for me this takes days and a lot of help to finish. That's why I'm interested in a way to install the previous version of Domoticz so my solar generation logging is working again and I can plan and prepare the update.

[akamming]

If you are already running zigbee2mqtt and Zwave-JS-UI (and probably mosquitto) as docker containers it s only a small step to also run Domoticz in a Docker container.
https://wiki.domoticz.com/Docker

Only it will be more resource heavy on the system with another container.
Then I would like my systems to have central update like running sudo apt update && sudo apt upgrade
With Docker I need to google the commands how to update the docker as well.

I created a bash script to update all my github plugins before I started to use docker.

i have 1 update script, which updates the system and all docker containers, which makes it very easy for me to update everything to latest version:

Code: Select all

echo "Updating package lists"
sudo apt update
echo "upgrading all packages"
sudo apt dist-upgrade --autoremove -y
echo pulling new docker images
cd ~/docker
docker compose pull
echo stopping and removing containers
docker compose down
echo recreating and starting containers
docker compose up -d
echo cleaning up unused space
docker system prune -f

requisite is that the docker dir contains one docker-compose.yaml file with the config of all your docker containers

you can extend by adding "git pull" commands for all your plugins which you got from github

[gizmocuz]

You can do all of that with one line

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

[acaonweb]

I'm not so happy in the way that this update modality was managed.

For each update, the non-compatibility of the new version with the host operating system has always been defined.
not in this case, Many people noticed this problem only because the update didn't work.

I have Buster on my raspberry and I have never updated it simply there was no reason, moreover it is not said that it is always possible to do it, maybe there is new hardware to buy, or there could be problems on other services present.

Now, reducing everything to a solution like "use docker", is not really the right way to manage this incompatibility, because even docker is not exempt from problems, since the present documentation is very basic.

Having said that, I will try to update raspbian (operation not simple because you have to update to subsequent steps, in my case Buster, then Bullseye and finally bookworm)

However, if this basically won't work, forcing me to reinstall everything (not just DOmoticz) on a clean raspbian installation, then if I have to redo everything again, I'll be forced to consider other home automation solutions, I should still start from scratch...

[Varazir]

I hate docker, I installed docker and all dockers I needed. Copied the config from my old installation and nothings works.....

zigbee2mqtt can't find my devices.
Domoticz data folder don't have the backup folder or the www so I can add my custom files for zwave-js-ui and zigbee2mqtt
I logged in with default login and then did a restore, I selected the db file that was created today by my old installation.
Now I can't login........

domoticz | 2025-05-31 11:56:53.715 Status: Domoticz V2024.4 (c)2012-2024 GizMoCuz
domoticz | 2025-05-31 11:56:53.715 Status: Build Hash: 731719420, Date: 2024-01-30 09:16:34
domoticz | 2025-05-31 11:56:53.715 Status: Startup Path: /opt/domoticz/
Error: Database incompatible with this Domoticz version. (You cannot downgrade to an old Domoticz version!)

WHY ?

Code: Select all

	domoticz:
	    container_name: domoticz
		image: domoticz/domoticz:beta
		restart: unless-stopped
		volumes: 
		    - ./domoticz/data:/opt/domoticz/userdata
		environment:
            - TZ=Europe/Stockholm
		ports:
		    - 80:8080
			- 443:8443

[acaonweb]

You can do all of that with one line

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

Nice to know, could you provide your yaml for your container?
I had a lot of issues, regarding how put my plugins, most important is zigbee2mqtt one and some others, and all my script (dzevents)

Thanx in advance

[Varazir]

I'm not so happy in the way that this update modality was managed.

For each update, the non-compatibility of the new version with the host operating system has always been defined.
not in this case, Many people noticed this problem only because the update didn't work.

I have Buster on my raspberry and I have never updated it simply there was no reason, moreover it is not said that it is always possible to do it, maybe there is new hardware to buy, or there could be problems on other services present.

Now, reducing everything to a solution like "use docker", is not really the right way to manage this incompatibility, because even docker is not exempt from problems, since the present documentation is very basic.

Having said that, I will try to update raspbian (operation not simple because you have to update to subsequent steps, in my case Buster, then Bullseye and finally bookworm)

However, if this basically won't work, forcing me to reinstall everything (not just DOmoticz) on a clean raspbian installation, then if I have to redo everything again, I'll be forced to consider other home automation solutions, I should still start from scratch...

Ya, I managed to get docker running on my old installation but it crashed when I tried to update to bookworm( I thought I hade to). I could have installed the domoticz docker version. Old installations runs but I can't access ssh and the pi/root account is locked due to failed upgrade to bookworm.

I hade a old installation where I started to setup docker for all services. Zigbee are all saved in a text file, zwave are stored on the zwave device and all settings in domoticz is saved the db file so I thought it wouldn't be that big of hassel, but fun fact no... it's just not playing nice. I have been trying to get to work for the last hour or 2.

[Varazir]

Hmm, ran this and now it's a bit better.

Code: Select all

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

zigbee2mqtt crashing on me

Code: Select all

[2025-05-31 12:13:20] debug:    zh:adapter:discovery: Connected devices: [{"path":"/dev/ttyAMA0"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyUSB0","manufacturer":"1a86","pnpId":"usb-1a86_USB_Serial-if00-port0","vendorId":"1a86","productId":"7523"}]
[2025-05-31 12:13:20] error:    z2m: Error while starting zigbee-herdsman
[2025-05-31 12:13:20] error:    z2m: Failed to start zigbee-herdsman
[2025-05-31 12:13:20] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-05-31 12:13:20] error:    z2m: Exiting...
[2025-05-31 12:13:20] error:    z2m: Error: USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration.

Code: Select all

    zigbee2mqtt:
        container_name: zigbee2mqtt
        image: koenkk/zigbee2mqtt
        restart: unless-stopped
        volumes:
            - ./zigbee2mqtt/data:/app/data
            - /run/udev:/run/udev:ro
        ports:
       # Frontend port
            - 8081:8080
        environment:
            - TZ=Europe/Stockholm
        devices:
       # Make sure this matched your adapter location
           - /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:/dev/ttyACM0

Code: Select all

pi@domoticz:~ $ ls /dev/serial/by-id/*
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
pi@domoticz:~ $

zwave crashing as well

Code: Select all

2025-05-31 12:35:39.821 CNTRLR   querying Serial API capabilities...
2025-05-31 12:35:39.826 DRIVER » [REQ] [GetSerialApiCapabilities]
2025-05-31 12:35:39.827 SERIAL » 0x01030007fb                                                         (5 bytes)
2025-05-31 12:35:41.431 DRIVER » [REQ] [GetSerialApiCapabilities]
2025-05-31 12:35:41.435 SERIAL » 0x01030007fb                                                         (5 bytes)
2025-05-31 12:35:43.040 DRIVER » [REQ] [GetSerialApiCapabilities]
2025-05-31 12:35:43.044 SERIAL » 0x01030007fb                                                         (5 bytes)
2025-05-31 12:35:44.650 DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                                 from the controller (ZW0200)
                                     at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D
                                 river.ts:7057:23)
                                     at ZWaveController2.queryCapabilities (/usr/src/app/node_modules/zwave-js/
                                 src/lib/controller/Controller.ts:1063:37)
                                     at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                                 /src/lib/driver/Driver.ts:1970:46)
                                     at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive
                                 r/Driver.ts:1696:16)

[Varazir]

zwavejsAD and MQTT works and Domoticz say it's connected to my MQTT broker bit it's not listing any devices and my old devices don't work.....

zigbee works fine now.

[acaonweb]

I'm not so happy in the way that this update modality was managed.

For each update, the non-compatibility of the new version with the host operating system has always been defined.
not in this case, Many people noticed this problem only because the update didn't work.

I have Buster on my raspberry and I have never updated it simply there was no reason, moreover it is not said that it is always possible to do it, maybe there is new hardware to buy, or there could be problems on other services present.

Now, reducing everything to a solution like "use docker", is not really the right way to manage this incompatibility, because even docker is not exempt from problems, since the present documentation is very basic.

Having said that, I will try to update raspbian (operation not simple because you have to update to subsequent steps, in my case Buster, then Bullseye and finally bookworm)

However, if this basically won't work, forcing me to reinstall everything (not just DOmoticz) on a clean raspbian installation, then if I have to redo everything again, I'll be forced to consider other home automation solutions, I should still start from scratch...

I spent hours to update dotobullseye, raspi doesn't connect to my network, no way to understand why, probably I need to configure all from scratch.. I'll try again but starting to investigate on Home Assistant