Domoticz

x@rpi5:~ $ cd /opt/domoticz
x@rpi5:/opt/domoticz $ sudo ./updaterelease
sudo: ./updaterelease: command not found
x@rpi5:/opt/domoticz $ ls
backups domoticz_crash.log domoticz.db-wal License.txt server_cert.pem
domocookie.txt domoticz.db dzVents plugins updatedomo
domoticz dom-shm oticz.db History.txt scripts www

hmm..that looks like an active running domoticz

Seems some mixup with ~/domoticz and /opt/domoticz that conflicts with the update script.... Did you know how you installed Domoticz?

Perhaps run in /opt/domoticz the following command. But also make some backups first, especially from your various Domoticz folders.

Ha, lekker! Werkt !

Yes, works, thnxs! Installed it with sudo bash -c "$(curl -sSfL https://install.domoticz.com)" but had some issues with an older SSL.
Then i tried to compile it, that went wrong.. so changed the SSL to vers 1.x and did run the standard command.

And indeed, i see 2 domoticz, one in /opt/ and one in home/user/domoticz.



2025-10-13 19:13:28.725 Status: Domoticz V2025.2 (c)2012-2025 GizMoCuz
2025-10-13 19:13:28.725 Status: Build Hash: e63981b18, Date: 2025-10-13 11:42:57
2025-10-13 19:13:28.725 Status: Startup Path: /opt/domoticz/

waltervl wrote: Monday 13 October 2025 17:11

PeJeWe wrote: Monday 13 October 2025 17:06 I have updated my rpi to bookworm and have domoticz up and running again.
maybe in the update script a warning that the debian version is to old???

I think that is not possible as the script is already on your system.
How did you update your RPI to bookworm, what instructions did you use?

I changed the bullseye to bookworm in the apt-get update list
Then i did a full upgrade.

PeJeWe wrote: Monday 13 October 2025 19:17

waltervl wrote: Monday 13 October 2025 17:11 I think that is not possible as the script is already on your system.
How did you update your RPI to bookworm, what instructions did you use?

I changed the bullseye to bookworm in the apt-get update list
Then i did a full upgrade.

Thanks, so basically the procedure as described in the link I mentioned before: https://www.cyberciti.biz/faq/update-up ... -bookworm/

Hi
I am running on Ubuntu 24.02 and tried the standard update way and the ./updaterelease version.
Neither worked for me.
Than I tried the git pull way and make. That did not work as well.
I noticed, when checking the status, No address was show, like 8080 and 433.(what ever you use)
The only thing what was shown, was a blue page.
This line was missing after updating Domoticz:
─17769 /home/username/domoticz/domoticz -daemon -www 8090 -sslwww 445
I use different addresses, there too many programs want o use 8080 on my server.
Maybe this info help a little,

gerard1 wrote: Monday 13 October 2025 20:31 Hi
I am running on Ubuntu 24.02 and tried the standard update way and the ./updaterelease version.
Neither worked for me.
Than I tried the git pull way and make. That did not work as well.
I noticed, when checking the status, No address was show, like 8080 and 433.(what ever you use)
The only thing what was shown, was a blue page.
This line was missing after updating Domoticz:
─17769 /home/username/domoticz/domoticz -daemon -www 8090 -sslwww 445
I use different addresses, there too many programs want o use 8080 on my server.
Maybe this info help a little,

Did you on your initial installation change the used ports through the install script or later changed in /etc/init.d/domoticz.sh as indicated on the wiki? With this method an update should always stay on these ports as an update does not touch this file.

Updated on Ubuntu server 24.04.3 using ./updaterelease without issue. Bare metal install, no docker.

OpenSSL 3.0.13 is already installed and I had manually installed libssl1.1 for the previous versions.

Thanks to all involved with the development!

Is there a way to get rid of the green popup announcing the new version?
I am the type that waits a few days before updating.

It's better to disable online update checks altogether. It comes out once a year, and every time this window pops up, we automatically click “update” in the hope of getting a new and improved system, but what we get is a complete crash of Domoticz. It's better to visit this forum, read up on it, and then update.

MYXOMOP wrote: Tuesday 14 October 2025 13:07 It's better to disable online update checks altogether. It comes out once a year, and every time this window pops up, we automatically click “update” in the hope of getting a new and improved system, but what we get is a complete crash of Domoticz. It's better to visit this forum, read up on it, and then update.

Not so negative please.
What I have noticed strolling around in this forum that in the vast majority of cases where people complain about malfunctioning of the system after updating there is a cause inside the setup of the way domoticz is installed.
I am using domoticz since november 2015 and never had a problem except problems caused by myself.

BTW
I had this setting
Software Updates:
☑ Check for Updates (Not working on windows systems)
and changed it to
☐ Check for Updates (Not working on windows systems)
Release Channel:
Stable

Like many else here I updated to 2025.2 only to find I run Bullseye which doesn't support openssl3 (ever). So why is this update presented in the first place? I used the update button in the web interface and expected everthing to work. I had to use the revert to backup feature (nice one!) to fix it and plan for an update to Bookworm.

The update feature has no warning function. You are free to implement that by creating an PR for this Open Source application.
As usual it is good to first check the new version announcement on the forum before pressing the update button.

skogl wrote: Tuesday 14 October 2025 16:21 Like many else here I updated to 2025.2 only to find I run Bullseye which doesn't support openssl3 (ever). So why is this update presented in the first place? I used the update button in the web interface and expected everthing to work. I had to use the revert to backup feature (nice one!) to fix it and plan for an update to Bookworm.

Reading your post I notice a positive mention about the option to revert to the backup created by the update script.
On the other hand this openssl backward compatibility has been warned for over and over in several topics, in this one to start with.
viewtopic.php?p=325672#p325672

My suggestion for the developers for future releases:
When releasing a new update, have it check for restrictions which may break the functioning of Domoticz somewhere.
Commands like <openssl versio>n or <which necessary_app> could reduce the # of disappointed users.

Problem is that the update script is already on your system, it came with the last release you installed. So a check for the next release is not possible without some extra handling (first download and execute a check script and then download and execute the update).

waltervl wrote: Tuesday 14 October 2025 18:43 Problem is that the update script is already on your system, it came with the last release you installed. So a check for the next release is not possible without some extra handling (first download and execute a check script and then download and execute the update).

Maybe they can adapt the script in the future to check the minimum requirements to run domoticz before updating?

When an update is released, there is no way to get rid of the update banner. So when I saw that pop-up this morning just before going to work I downloaded a backup to my phone, navigating with some difficulty because the pop-up was in the way, and then hit the upgrade button. A "failed to download" message and no more Domoticz.
After work, I started Putty on my PC, updated Bullseye to Bookworm and all is well again.

But still...
Please add a "Remind me later" button to the pop-up.
Please, as others already requested, let the upgrade do some kind of compatibility check.

Apart from that, thanks for your hard work!

I appreciate all responses here and I understand there are different ways to look at this. I'm not a "power user" here and use domoticz with great success to light some lamps up in my house in the evenings and so on so this is the first time I'm in the forums for years.

My background story is that I had a similar experience years ago when an update also required an updated debian and I remember I tried to upgrade but I ended up having to reinstall the entire device to get it to work again (don't think the "backup before update" existed back then - atleast I couldn't find it). So I always look in the update script for things like these but I couldn't find any information about requirements for openssl3 and having to update kernel so I updated in good faith. It didn't occur to me that I had to look in the forum before the update. Maybe it's a good idea to write these things in the update information?

I very much appreciate all work on this app and I agree I should probably engage more but I just wanted so get this off my chest in case it wasn't already a known issue. And next time I update I will absolutely look here in the forum

waltervl wrote: Tuesday 14 October 2025 18:43 Problem is that the update script is already on your system, it came with the last release you installed. So a check for the next release is not possible without some extra handling (first download and execute a check script and then download and execute the update).

Well the obvious solution would be to first offer a update that is compiled for older debian (openssl1) and includes this new update script that refuses to update any further unless openssl3 is present.

However..

May 5th 2025 was the release date of stable 2025.1

May 11th 2025 there was a beta release with this remark:
"There has been a new beta released that has a modification in the updatebeta script that checks for OpenSSL 3."

Only 6 days in between.. surely you knew by 5.5 that 2025.2 would break on old systems? So why not include the check in the stable release as well?

Currently I am having two versions of Domoticz running. One on raspberry pi {not on docker). The other on a thin client T620 (Ubuntu 24) running in a container.

1
I made a big mistake as the raspberry was not yet updated to Bookworm. I updated Domoticz which of course failed. But chatgpt solved my problem by giving me detailled info how to update to bookworm. I know , not the best way but within an hour all was up and running again. In the very near future I will start with fresh Bookworm OS to overcomes possible problems.

2
I noticed that the Domoticz version does not have option to look for updates.
Q: how do I update Domoticz in docker compose?

Bart