Domoticz upcoming beta/release and OpenSSL 3.0

[Varazir]

Got zwave to work as well.

[acaonweb]

brand new raspbian os, bookworm
fresh Domoticz install

Code: Select all

/home/pi/domoticz/domoticz: error while loading shared libraries: libssl.so.1.1

now????

[janpep]

Code: Select all

/home/pi/domoticz/domoticz: error while loading shared libraries: libssl.so.1.1

now????

Did you install the beta?
I did a fresh install here also on new installed bookworm (on Raspberry pi 3B+). No problem.
Also installed the beta on my Ubuntu 24.04 (Virtual machine under Synology). No problem.

[FireWizard]

Hi, @acaonweb,

now????

And now.....?

As you have probably installed the latest Domoticz stable 2025.1, you have 2 options.

1. Either install libssl1.1 in Bookworm, so that Domoticz 2025.1 stable and any Domoticz beta, earlier than May 15, will run fine.
2. Install Domoticz, latest beta, so that all future beta's and stable, later than 2025.1 will run fine.

To install libssl1.1 do:

Code: Select all

sudo apt install libssl1.1

In this case, you should also install:

Code: Select all

sudo apt install libusb-dev

To use the latest beta do the following:

As you have Domoticz already installed it is sufficient to update to beta

Code: Select all

cd ~/domoticz
sudo ./updatebeta

Regards

[acaonweb]

Hi, @acaonweb,

now????

And now.....?

As you have probably installed the latest Domoticz stable 2025.1, you have 2 options.

1. Either install libssl1.1 in Bookworm, so that Domoticz 2025.1 stable and any Domoticz beta, earlier than May 15, will run fine.
2. Install Domoticz, latest beta, so that all future beta's and stable, later than 2025.1 will run fine.

To install libssl1.1 do:

Code: Select all

sudo apt install libssl1.1

In this case, you should also install:

Code: Select all

sudo apt install libusb-dev

To use the latest beta do the following:

As you have Domoticz already installed it is sufficient to update to beta

Code: Select all

cd ~/domoticz
sudo ./updatebeta

Regards

thanx for your help.. I'm investigating on migrate to docker, so I'm trying to
1) create a docker container (check)
2) create a new fresh install on a new SD (to do, thank for the tips above)
3) disable for a while the running service: it's ok to disable it with: sudo systemctl disable domoticz ? and enable again sudo systemctl enable domoticz ??

[FireWizard]

HI @acaonweb,

You asked:

3) disable for a while the running service: it's ok to disable it with: sudo systemctl disable domoticz ? and enable again sudo systemctl enable domoticz ??

Yes you can do that, but stop Domoticz first

Code: Select all

sudo systemctl stop domoticz

or

Code: Select all

sudo service domoticz stop

Regards

[acaonweb]

Thanx for your suggestion

[lostusr]

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)"

Actually I would like to install an older version, but at the moment I got no idea how to get back... maybe extract from an privious operating SD-card, if possible at all...

All started with an backup-restore wich is not putting back missing mqtt-sensor-datas which for sure are in there as it worked just few hours before. Thought reinstall would be worth an try, but holly shit...

[waltervl]

You can always start building your own Domoticz yourself, no problem there. If you want to use the ease of a pre build version just follow the instructions and don not find all kind of shortcuts.

The easiest way if you do not want to build something yourself and want to stay on bullseye is to use docker.

[gizmocuz]

Could you tell me the output of the following bash command

Code: Select all

openssl version -v | awk '{print $2}' | sed 's/\..*//'

[lostusr]

Unfortunately not now, but wil do later. My try & error raspi is from a device at work and it's going somewhere else for the next aprox. 3 weeks.
At my private one I put all together and just touch it again as I fixt my list of open points.

But thanks for the hints as I'm not so firm with linux!

[domcars0]

There is still native GPIO support in Domoticz
SysFS has been deprecated for years

What are you controlling?!Can this be done via an ESP or a Zigbee device?

Hi,
It's strange, cause when I want to add a new Raspberry GPIO hardware in my Domoticz 2025.1 on my Pi 3b with Bookworm this message appears in log console:

"2025-06-11 10:05:38.671 Status: Classic GPIO: This hardware is deprecated. Please transfer to the new SysFS hardware type!"
But there is no more SysFS GPIO with bookworm
???

[TiXav]

I would like to upgrade (not docker), and I made inventory of my system and find the way to make my future system working same/closed to today, I noticed the same thing as you about the GPIO, Have you found a solution since your last message?

[lostusr]

Could you tell me the output of the following bash command

Well:

Code: Select all

pi@openWB2:~ $ openssl version -v | awk '{print $2}' | sed 's/\..*//'
3

[lostusr]

You can always start building your own Domoticz yourself, no problem there. If you want to use the ease of a pre build version just follow the instructions and don not find all kind of shortcuts.

The easiest way if you do not want to build something yourself and want to stay on bullseye is to use docker.

Thanks for the hints. So I tried my own build, but next error occured:

Code: Select all

CMake Error at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  Could NOT find Lua (missing: LUA_LIBRARIES LUA_INCLUDE_DIR) (Required is at
  least version "5.3")

So when I've mood the next time I might get firm with docker ... hope that's more try than error...

[waltervl]

Best is to update your system to latest OS....

[waltervl]

Heads Up! Stable 2025.2 is coming in this theatre very soon!! So be prepared if you run on an old OS!
Use docker or update your OS to the latest version available.

[Backbone]

Too late....
You first click update after a new version message pops up.
Then after the fail you start to search why it fails and land here after some google searches.

Time for a new install and restore a backup.

Paco

[Zuikkis]

Too late....
You first click update after a new version message pops up.
Then after the fail you start to search why it fails and land here after some google searches.

Time for a new install and restore a backup.

Paco

Same..

Except that I'm now upgrading my system so domoticz can run.

There has been a new beta released that has a modification in the updatebeta script that checks for OpenSSL 3.
If you update now, you will not be able to upgrade to a newer version until you meet the new system requirements (see it as a safety net)

just for you to know that apparently there is no such check from upgrading from stable 2025.1.. It happily installed 2025.2 and then failed to start because of missing OpenSSL3. I'm sure many users will find themself in this same situation.

[lost]

just for you to know that apparently there is no such check from upgrading from stable 2025.1.. It happily installed 2025.2 and then failed to start because of missing OpenSSL3. I'm sure many users will find themself in this same situation.

The change comes from this commit 5 months ago:
https://github.com/domoticz/domoticz/co ... 6d4dad2912

So this was done a bit after last stable release on may 5, unfortunately.

I would say this is same consequence (domoticz unable to restart after upgrade) as previous armV6 builds removal, that was not checked in previous stables update scrips that could then go till the end on an architecture that was no more supported, with domoticz then unable to restart.

As this is not easy to always foresee such changes from one stable to another (let's not talk about several versions jump), only way to fix this for the future would be a change in the update process to 1st extract the update script of just downloaded archive to be installed & execute this up to date script!