Domoticz

Thuis wrote: Tuesday 16 December 2025 19:58 Oh well, i changed the script a bit, so it will not look if domoticz service is running, but it just stops it anyway, if it is running or not, this works...

Did you make a PR for this so everyone can make use of it? Else you can change this after every update....

Hi, @ waltervl, I should have been a bit clearer when I said a stop / start, that is indeed what I had to do, like you a restart does not work for me either.

A PR? Yes i like to do that so everyone can use it, but i have no idea how to do this, I am at github, then i click new pull request, because i think that is what i need to do, but the button is grayed out. It says i can compare branches? So im stuck there. Then i read "Contributing to Domoticz" but then i see someting about new hardware and it brings me to the wiki. I see Please base your bug fixes against the development branch. Please also use a descriptive commit message So in short, i have no clue how to PR. I never used it... Tell me

So i made a fork, changed the updatebeta, but yes, i have no idea what i am doing. So i better stop.

A short description of the pull-request creation process :

1. Fork the original repository you'd like to make updates for.

2. Go into your own forked Repository and copy the Branch you like to make an update for into a new Branch, so in this case select the Development branch: 3. Go to the main page and select the newly created Branch. 4. Update the file(s) that need modification and commit the change.

5. On the main page you now see the Contribute option. Click Contribute & Open Pull Request: 6. Add title & Description
Check the Target Repo : Domoticz/Domiticz - Development
Check source Repo: YOU/domoticz - Fix_Update_Process
Click on "Create Pull Request" That's it.


The reason for creating a new Branch is that this allows it to be deleted after the PR is processed, which is an option when merge is done.
On top of that, you shouldn't update the Development branch itself as that will sync with the updates done in Domoticz/Domoticz and else could create conflicts when you want to update you forked version.

Thanks, i tried my best, lots of steps and if you never used it, like me, it is a bit overwhelming, so thank you very much for pointing me in the right direction. I hope all is received in good order and everyone can use it...

Thuis wrote: Wednesday 17 December 2025 15:36 Thanks, i tried my best, lots of steps and if you never used it, like me, it is a bit overwhelming, so thank you very much for pointing me in the right direction. I hope all is received in good order and everyone can use it...

I totally agree and felt the same way when I started using Git, coming from a simple SVN versioning setup.
That's why I spent a little time explaining it to you.
I would never want to go back and use it also for all my domoticz scripting to keep a log of all changes I made over time and track them in a local gitbucket server.

waltervl wrote: Tuesday 16 December 2025 20:55 Did you make a PR for this so everyone can make use of it? Else you can change this after every update....

I'm probably indirectly at the source of this issue, as I did a PR on this weeks ago:
https://github.com/domoticz/domoticz/pull/6462

But this was much closer to previous script than what was finally changed by Gizmocuz: He asked me to test this but I don't have a beta test system anymore and this was finally IMHO over-engineered vs my quite simple & straightforward proposal (zero-IA inside) I already tested (up to what can be tested without possibility to do the full path including nominal beta archive/download).

IMO, best would be to revert changes for now if no-one available to fix this. The recent PR does many shortcuts, just bypass the changes dedicated to have up-to-date requirements checks that was the reason for change, and would just be unsafe for many users.

last updatebeta overwrites "domoticz.sh" and "updatebeta"
(lost my changes like user and program directory and the use of sudo)
local ENV file maybe?

I think when @gizmocuz is back from his trip it will be solved. We have to be pcient. The PR of @Thuis seems to be a littble bit too much of a simplification. The script has to work on various linux distros.

As the update scripts gets updated by the update script it is important to keep trying to update from a stable version as the majority of the users are going to do this....

Yes it is better not letting me do PR, haha.
Better wait indeed. Thanks anyway

In beta 17003 I now always force Domoticz to stop.
This should hopefully solve the problem, but this can only be testen when there is a new update...

Spoiler: show

.........................................>> Installation complete.
>> Domoticz service does not exist - skipping service start
>> You will need to start Domoticz manually
>> Update completed successfully!
$:~/domoticz$ sudo systemctl start domoticz.service
$:~/domoticz$ sudo systemctl status domoticz.service
● domoticz.service - domoticz_service
Loaded: loaded (/etc/systemd/system/domoticz.service; enabled; preset: enabled)
Active: active (running) since Tue 2026-01-06 08:53:16 CET; 9s ago
Main PID: 133768 (domoticz)
Tasks: 44 (limit: 9174)
Memory: 144.7M (peak: 179.8M)
CPU: 8.447s
CGroup: /system.slice/domoticz.service
└─133768 $/domoticz/domoticz -wwwbind 192.168.10.20 -www 8080 -sslwww 0 -log /var/log/domoticzlog/domoticz.log -loglevel normal,status,error

Jan 06 08:53:21 domoticz[133768]: 2026-01-06 08:53:21.042 Catt Notify System: CATT Complete Plugin started successfully.
Jan 06 08:53:21 domoticz[133768]: 2026-01-06 08:53:21.568 (RM2 - Opdrachten) Updating device from 0:'Off' to have values 0:'Off'.
Jan 06 08:53:21 domoticz[133768]: 2026-01-06 08:53:21.571 (RM2 - Opdrachten) Updating device from 0:'Off' to have values 0:'Off'.
Jan 06 08:53:22 domoticz[133768]: 2026-01-06 08:53:22.451 dzVents: stroom 7.14 A
Jan 06 08:53:22 domoticz[133768]: 2026-01-06 08:53:22.451 dzVents: spanning 234.7 V
Jan 06 08:53:22 domoticz[133768]: 2026-01-06 08:53:22.453 dzVents: Berekend vermogen van de Airco 1675.76 W

Yes i am sorry i did not get this github thing to work, there are so many option and i never used it so i just deleted it, sorry that i could not help. But this seems to work. However the domoticz.service does exist, but hey, manually starting it is ok too i guess... Thanks for the changes ./updatebeta works again for updating it to the latest beta.

gizmocuz wrote: Tuesday 06 January 2026 1:49 In beta 17003 I now always force Domoticz to stop.
This should hopefully solve the problem, but this can only be testen when there is a new update...

Why does webgui update does not stop and start the service correctly and cli update with ./updatebeta (or ./updaterelease) does it correctly?

updating from beta 16997 to beta 17003 still fails over webgui (not sure the change is in it.)

waltervl wrote: Wednesday 07 January 2026 0:00 updating from beta 16997 to beta 17003 still fails over webgui (not sure the change is in it.)

Updating from 17003 to 17030 also did not fix this.....Same error.

Updating from 17030 to 17031 don't work from webui(reaches 100% but the update does not occur)...works only with sudo ./updatebeta

pfloryann wrote: Thursday 15 January 2026 9:21 Updating from 17030 to 17031 don't work from webui(reaches 100% but the update does not occur)...works only with sudo ./updatebeta

sudo service domoticz restart
should also fix it after an error after the webgui update (as a workaround)

In latest beta the webgui update issue has been fixed.

Issue from build 17051 to 17053 ...on github the tichet was closed

Yes, you need to be on the last beta to have the web update working again.
So it could you need to use the manual method one more time