Domoticz upcoming beta/release and OpenSSL 3.0

[willemd]

Hi,

it's not done with just openSSL 3:

Code: Select all

pi@openWB2:~ $ openssl version
OpenSSL 3.3.2 3 Sep 2024 (Library: OpenSSL 3.3.2 3 Sep 2024)
pi@openWB2:~ $ sudo bash -c "$(curl -sSfL https://install.domoticz.com)"
OpenSSL version 3 required!

VERSION="11 (bullseye)"

I ran into the same problem ...but also found a solution

problem was:
So I tried to install domoticz and got a message that it needed OpenSSL version 3 (and the system had version 1)
Then I followed one of the installation guides available on the internet and that worked fine.
I checked the result after reboot with "openssl version" command and it showed version 3.
Then I tried to install domoticz again but got the same message that it needed version 3.

solution:
I noted the standard domoticz installation is a "sudo" command and I checked "sudo openssl version" and then it still showed version 1.
So I concluded the new OpenSSL was not in the PATH for sudo and that is why domoticz installation failed.
I added "/usr/local/ssl/bin" to the PATH in /etc/sudoers and then it worked.

[jannl]

Did you install openssl as root? Did you remove opsenssl 1?

[TiXav]

this is just a a helping hand for those who have not migrate yet (like me) due to gpio not accessible in bookworm (sysfs does not exist anymore on a fresh install), I found this https://github.com/flyte/mqtt-io
that works well for me (still on bulleye),this software exposes GPIO (and more like serial... even I don't use it...) throught MQTT, then I use MQTT mapper plugin domoticz side : The goal is to use domoticz in docker version, and not moving to bookworm soon. (Domoticz is not the only one software on my Pi3B)
I use it for inputs: front & back garage doors... outputs : gate control, Electric heating control... this software is started by .sh script started by crontab (user:pi NOT root) @boot.
Now I hope that mqtt broadlink plugin will continue to work well with the new version of domoticz

[waltervl]

this is just a a helping hand for those who have not migrate yet (like me) due to gpio not accessible in bookworm (sysfs does not exist anymore on a fresh install)....

You can still work with gpio on newer OS, see for example topic viewtopic.php?f=4&t=44077
And
viewtopic.php?t=43984

[pgas37]

I was browsing through this topic and it made my head spin.

What a hassle and set of steps to run version 2025-2 under Bookworm later on.

Maybe a really stupid question, but isn't it possible to use the RPI Imager to put a new OS-bookworm version on a sd-card, then run the Domoticz setup procedure, and afterwards restore a backup?

thanks
Paul

[gizmocuz]

It is quite easy to backup your database/settings/domoticz folder and it is also easy to install trixie on your raspberry and domoticz again

It is also easy to install and use Domoticz via docker compose, so you will not have issues like this

There are also numerous posts here explaining quite good how to upgrade your system.

Google can also help here. With a few copy/paste lines you can upgrade your system to trixie

[pgas37]

Gizmocuz,

That's easier said than done for the inexperienced UNIX-user.
The recommended manual immediately causes problems because the example command outputs are different then mine, and you're unsure whether it's correct or not, and whether you can continue.
Docker is also recommended. I have a Pi running with DomoServer, MQTT for Zwave, SolarEdge Modbus, the web API, and a few other things. Writing a new SD card and reinstalling everything will probably run into Python problems again, just like in the past. I'm not looking forward to that.
Is it possible to import the entire installation into a Docker container, or do I need to create separate containers for Zwave, etc.? If possible please advice the steps to taken.

thanks

[ricorico94]

I noted the standard domoticz installation is a "sudo" command and I checked "sudo openssl version" and then it still showed version 1.
So I concluded the new OpenSSL was not in the PATH for sudo and that is why domoticz installation failed.
I added "/usr/local/ssl/bin" to the PATH in /etc/sudoers and then it worked.

I tried to upgrade from 2024.4 to 2026.6 under Bullseye and Ifaced indeed this error about OpenSSL.
I still face problems after the .updaterelease but at least here are steps I followed not described in detail by Willemd, if it can help someone..

I first followed these steps (based on google AI search..)

Spoiler: show

Option 1: Compile OpenSSL 3 from Source

Compiling installs OpenSSL 3 to a custom prefix (e.g., /usr/local/ssl) so it doesn't break system packages that depend on OpenSSL 1.1.1.
1. Install build dependencies:bash
sudo apt update
sudo apt install build-essential wget tar checkinstall

2. Download and extract OpenSSL 3 source code:bash
cd /usr/local/src
sudo wget https://www.openssl.org/source/openssl-3.1.0.tar.gz
sudo tar -zxf openssl-3.1.0.tar.gz
cd openssl-3.1.0
(Note: You can check OpenSSL Source for a newer 3.x patch version if needed).

3. Configure, compile, and install:bash
sudo ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib
sudo make -j$(nproc)
sudo make install

4. Configure library paths:bash
echo "/usr/local/ssl/lib" | sudo tee /etc/ld.so.conf.d/openssl-3.conf
sudo ldconfig

5. Verify the installation:bash
/usr/local/ssl/bin/openssl version

(To use this custom version in your applications, you will need to point your app's build or run configuration to /usr/local/ssl rather than overwriting the system's /usr/bin/openssl).

At that point, the .updaterelease was still showing error an indeed the "sudo openssl version" is still shwing v1.
Then I used this site : https://www.linux-fra.com/?p=19815 to understand how to ajust the path.
That done, the .updaterelease does not show error.
However, domoticz does not retsart properly (at least in my case, systemctl shows domotics as active, but I can't access the webpage even after deleting the .db database).

[JayDotR]

I ran into the similar issue, and fortunately a micro sd card error forced me to take the wise decision to reinstall the OS from scratch, go to trixie (if i am right, 2 versions newer as bullseye).

Some libraries to adjust, restore my plugins folders without the __pycache__, restore the db and it went fine like hell.

At least the OS is fully patcheable now again ..