Domoticz

Posted: **Wednesday 10 December 2025 12:07**

Anyone had issues with the last 2 beta updates, it runs for the full on screen percentage which is unusual, then says update failed check your internet connection after which domoticz does not repsond, a quick putty session to stop and start the service and all is good and the update has been done. Had this on 2 differnet pi's at 2 different locations.

Posted: **Wednesday 10 December 2025 21:44**

what if you do it from the command line with
sudo ./updatebeta

Do you see error messages? There are some changes made in the update script to have extra checks.

Posted: **Wednesday 10 December 2025 21:47**

Just ran mine through webupdate on my test system (X86 linux) and domoticz did not start after the countdown ended....

Posted: **Wednesday 10 December 2025 21:54**

update through cli went fine

Code: Select all

bolt@bolt-C40:~/domoticz$ sudo ./updatebeta
[sudo] password for bolt: 
>> Starting Domoticz beta Update
>> Script: updatebeta (Directory: /home/bolt/domoticz)
>> Validating environment...
>> Environment validation passed (arch: x86_64, OS: linux)
>> Checking package dependencies...
>> All required packages are already installed
>> Downloading latest beta version...
domoticz_update.tgz 100%[===================>]  16.09M  13.4MB/s    in 1.2s    
>> Download complete. Verifying archive integrity...
>> Archive integrity verified.
>> Checking for updated upgrade script...
>> Found updated script, re-executing...
>> Starting Domoticz beta Update
>> Script: updatebeta (Directory: /home/bolt/domoticz)
>> Validating environment...
>> Environment validation passed (arch: x86_64, OS: linux)
>> Checking package dependencies...
>> All required packages are already installed
>> Running updated script - proceeding with installation...
>> Stopping Domoticz service...
>> Creating backup: backups/domoticz_backup_20251210_215004.tar.gz
>> Backup complete.
>> Installing new version...
.........................................>> Installation complete.
>> Starting Domoticz service (please wait)...
>> Service started successfully.
>> Update completed successfully!

Posted: **Wednesday 10 December 2025 21:59**

Why do a beta update? Unless there is required new functionality or required security updates, it’s not good practice…

Posted: **Wednesday 10 December 2025 22:09**

heggink wrote: Wednesday 10 December 2025 21:59 Why do a beta update? Unless there is required new functionality or required security updates, it’s not good practice…

I do it on a test system...... to test.....
But indeed, do not go for beta if you do not need so. But some users need bug fixing eg like now for Philips Hue

Posted: **Thursday 11 December 2025 8:24**

the updatescript has been changed to make sure we can catch compatibility issues in the feature.

Reading your ./updatebeta output, it seems the new beta is installed, if you refresh the browser, is there actually a new version installed?
If not, and you issue by hand

sudo service domoticz.sh restart

do you see the new version number?

Posted: **Thursday 11 December 2025 10:40**

So recap for me (@gizmocuz to who did you ask this question?):
I updated my beta test environment through web and Domoticz crashed after restart.
Then I updated through ./updatebeta en there you see the log from.

I will wait for the next update and try the webupdate again. I am not sure where the first crash came from as somehow my internet connection seemed buggy too. So it could be an upload issue. Is a webupdate also logged in a domoticzupdate log so you can read back what happened? Now it is trial and error...

I can also restore the original version and try a new webupdate.... Perhaps better to debug this as to exclude possible internet connection issues.

Posted: **Thursday 11 December 2025 16:05**

Sorry, was indeed asking the question to you.

When you did a manually updatebeta run, I hope you got the latest Domoticz?

We can not output the log the console script log in the Domoticz log... but that is also not needed... You also won't see this when you update your nas/router etc.

Maybe because the update script is now run twice.. it thinks it is ready, but is actually not...
At that point it tries to load the new webpage, and that will fail...

Was it a crash? or a web page load issue?

A buggy internet should not cause a issue, as the download archive is validated...

Posted: **Thursday 11 December 2025 16:11**

Made a new beta version (16995) ....

Posted: **Thursday 11 December 2025 19:58**

New try:
- Restored my backup and now running Version: 2025.2 (build 16990) Build Hash: 98c45ad1c Compile Date: 2025-12-03 09:07:49
- New update available, update trough web. Countdown, reached 100 en then error: Error while downloading Update,
check your internet connection or try again later !...

service status shows

Code: Select all

Dec 11 19:46:55 bolt-C40 systemd[1]: Starting domoticz.service - LSB: Home Automation System...
Dec 11 19:46:55 bolt-C40 domoticz.sh[100209]: Time synchronized, starting Domoticz...
Dec 11 19:46:55 bolt-C40 domoticz.sh[100217]: 2025-12-11 19:46:55.143  Status: Domoticz V2025.2 (build 16995) (c)2012-2025 GizMoCuz
Dec 11 19:46:55 bolt-C40 domoticz.sh[100217]: 2025-12-11 19:46:55.143  Status: Build Hash: b5d05e770, Date: 2025-12-11 14:19:14
Dec 11 19:46:55 bolt-C40 domoticz.sh[100217]: 2025-12-11 19:46:55.143  Status: Startup Path: /home/bolt/domoticz/
Dec 11 19:46:55 bolt-C40 domoticz.sh[100217]: domoticz: Domoticz is starting up....
Dec 11 19:46:55 bolt-C40 domoticz[100217]: Domoticz is starting up....
Dec 11 19:46:55 bolt-C40 systemd[1]: Started domoticz.service - LSB: Home Automation System.
Dec 11 19:46:55 bolt-C40 sudo[100202]: pam_unix(sudo:session): session closed for user root

It crashed, see next crash log in spoiler

Spoiler: show: gdb: warning: Couldn't determine a path for the index cache directory.
[New LWP 100223]
[New LWP 100222]
[New LWP 100221]

warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/liblber.so.2

warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libbrotlidec.so.1

warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libbrotlicommon.so.1
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007cb383510813 in __GI___wait4 (pid=100225, stat_loc=0x7ffee1959624, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30

warning: 30 ../sysdeps/unix/sysv/linux/wait4.c: No such file or directory
Id Target Id Frame
* 1 Thread 0x7cb382a1a980 (LWP 100218) "domoticz" 0x00007cb383510813 in __GI___wait4 (pid=100225, stat_loc=0x7ffee1959624, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
2 Thread 0x7cb3808ff6c0 (LWP 100223) "InfluxPush" 0x00007cb383526d07 in __GI___select (nfds=32, readfds=0x7cb3808fe8c0, writefds=0x0, exceptfds=0x0, timeout=0x7cb3808fe8b0) at ../sysdeps/unix/sysv/linux/select.c:69
3 Thread 0x7cb3817fe6c0 (LWP 100222) "PluginMgr" 0x00007cb383526d07 in __GI___select (nfds=14, readfds=0x7cb3817fd9a0, writefds=0x0, exceptfds=0x0, timeout=0x7cb3817fd990) at ../sysdeps/unix/sysv/linux/select.c:69
4 Thread 0x7cb381fff6c0 (LWP 100221) "SQLHelper" 0x00007cb383526d07 in __GI___select (nfds=20, readfds=0x7cb381ffe870, writefds=0x0, exceptfds=0x0, timeout=0x7cb381ffe860) at ../sysdeps/unix/sysv/linux/select.c:69

Thread 4 (Thread 0x7cb381fff6c0 (LWP 100221) "SQLHelper"):
#0 0x00007cb383526d07 in __GI___select (nfds=20, readfds=0x7cb381ffe870, writefds=0x0, exceptfds=0x0, timeout=0x7cb381ffe860) at ../sysdeps/unix/sysv/linux/select.c:69
#1 0x00006054b9c55391 in StoppableTask::IsStopRequested(int) ()
#2 0x00006054b9c207a9 in CSQLHelper::Do_Work() ()
#3 0x00006054ba3dfb23 in execute_native_thread_routine ()
#4 0x00007cb38349caa4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:447
#5 0x00007cb383529c6c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 3 (Thread 0x7cb3817fe6c0 (LWP 100222) "PluginMgr"):
#0 0x00007cb383526d07 in __GI___select (nfds=14, readfds=0x7cb3817fd9a0, writefds=0x0, exceptfds=0x0, timeout=0x7cb3817fd990) at ../sysdeps/unix/sysv/linux/select.c:69
#1 0x00006054b9c55391 in StoppableTask::IsStopRequested(int) ()
#2 0x00006054ba10d49d in Plugins::CPluginSystem::Do_Work() ()
#3 0x00006054ba3dfb23 in execute_native_thread_routine ()
#4 0x00007cb38349caa4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:447
#5 0x00007cb383529c6c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 2 (Thread 0x7cb3808ff6c0 (LWP 100223) "InfluxPush"):
#0 0x00007cb383526d07 in __GI___select (nfds=32, readfds=0x7cb3808fe8c0, writefds=0x0, exceptfds=0x0, timeout=0x7cb3808fe8b0) at ../sysdeps/unix/sysv/linux/select.c:69
#1 0x00006054b9c55391 in StoppableTask::IsStopRequested(int) ()
#2 0x00006054b9d49ab7 in CInfluxPush::Do_Work() ()
#3 0x00006054ba3dfb23 in execute_native_thread_routine ()
#4 0x00007cb38349caa4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:447
#5 0x00007cb383529c6c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 1 (Thread 0x7cb382a1a980 (LWP 100218) "domoticz"):
#0 0x00007cb383510813 in __GI___wait4 (pid=100225, stat_loc=0x7ffee1959624, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
#1 0x00006054b9c02be5 in dumpstack_gdb(bool) ()
#2 0x00006054b9c031f5 in signal_handler(int, siginfo_t*, void*) ()
#3 <signal handler called>
#4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#5 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#6 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7 0x00007cb38344527e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8 0x00007cb3834288ff in __GI_abort () at ./stdlib/abort.c:79
#9 0x00006054b9ade3fa in __gnu_cxx::__verbose_terminate_handler() [clone .cold] ()
#10 0x00006054ba35f6ba in __cxxabiv1::__terminate(void (*)()) ()
#11 0x00006054ba35f725 in std::terminate() ()
#12 0x00006054b9b6f66e in std::_Sp_counted_ptr_inplace<std::thread, std::allocator<void>, (__gnu_cxx::_Lock_policy)2>::_M_dispose() ()
#13 0x00006054b9bdc189 in CMQTTPush::~CMQTTPush() ()
#14 0x00007cb383447a76 in __run_exit_handlers (status=1, listp=<optimized out>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:108
#15 0x00007cb383447bbe in __GI_exit (status=<optimized out>) at ./stdlib/exit.c:138
#16 0x00007cb38342a1d1 in __libc_start_call_main (main=main@entry=0x6054b9ae0c60 <main>, argc=argc@entry=6, argv=argv@entry=0x7ffee195a328) at ../sysdeps/nptl/libc_start_call_main.h:74
#17 0x00007cb38342a28b in __libc_start_main_impl (main=0x6054b9ae0c60 <main>, argc=6, argv=0x7ffee195a328, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffee195a318) at ../csu/libc-start.c:360
#18 0x00006054b9b05f41 in _start ()

Main thread:
#0 0x00007cb383510813 in __GI___wait4 (pid=100225, stat_loc=0x7ffee1959624, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
#1 0x00006054b9c02be5 in dumpstack_gdb(bool) ()
#2 0x00006054b9c031f5 in signal_handler(int, siginfo_t*, void*) ()
#3 <signal handler called>
#4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#5 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#6 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7 0x00007cb38344527e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8 0x00007cb3834288ff in __GI_abort () at ./stdlib/abort.c:79
#9 0x00006054b9ade3fa in __gnu_cxx::__verbose_terminate_handler() [clone .cold] ()
#10 0x00006054ba35f6ba in __cxxabiv1::__terminate(void (*)()) ()
#11 0x00006054ba35f725 in std::terminate() ()
#12 0x00006054b9b6f66e in std::_Sp_counted_ptr_inplace<std::thread, std::allocator<void>, (__gnu_cxx::_Lock_policy)2>::_M_dispose() ()
#13 0x00006054b9bdc189 in CMQTTPush::~CMQTTPush() ()
#14 0x00007cb383447a76 in __run_exit_handlers (status=1, listp=<optimized out>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:108
#15 0x00007cb383447bbe in __GI_exit (status=<optimized out>) at ./stdlib/exit.c:138
#16 0x00007cb38342a1d1 in __libc_start_call_main (main=main@entry=0x6054b9ae0c60 <main>, argc=argc@entry=6, argv=argv@entry=0x7ffee195a328) at ../sysdeps/nptl/libc_start_call_main.h:74
#17 0x00007cb38342a28b in __libc_start_main_impl (main=0x6054b9ae0c60 <main>, argc=6, argv=0x7ffee195a328, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffee195a318) at ../csu/libc-start.c:360
#18 0x00006054b9b05f41 in _start ()
[Inferior 1 (process 100218) detached]

Running sudo ./updatebeta
Runs fine as the same test I did yesterday wih ./updatebeta, domoticz active and on build 16995
service status

Code: Select all

Dec 11 19:55:17 bolt-C40 systemd[1]: Starting domoticz.service - LSB: Home Automation System...
Dec 11 19:55:17 bolt-C40 domoticz.sh[100704]: Time synchronized, starting Domoticz...
Dec 11 19:55:17 bolt-C40 domoticz.sh[100712]: 2025-12-11 19:55:17.671  Status: Domoticz V2025.2 (build 16995) (c)2012-2025 GizMoCuz
Dec 11 19:55:17 bolt-C40 domoticz.sh[100712]: 2025-12-11 19:55:17.672  Status: Build Hash: b5d05e770, Date: 2025-12-11 14:19:14
Dec 11 19:55:17 bolt-C40 domoticz.sh[100712]: 2025-12-11 19:55:17.672  Status: Startup Path: /home/bolt/domoticz/
Dec 11 19:55:17 bolt-C40 domoticz.sh[100712]: domoticz: Domoticz is starting up....
Dec 11 19:55:17 bolt-C40 domoticz[100712]: Domoticz is starting up....
Dec 11 19:55:17 bolt-C40 systemd[1]: Started domoticz.service - LSB: Home Automation System.

Posted: **Thursday 11 December 2025 20:09**

New try but now without webupdate but directly from cli
So restored the same 16990 backup
started Domoticz 16990

Code: Select all

sudo ./updatebeta
>> Starting Domoticz beta Update
>> Script: updatebeta (Directory: /home/bolt/domoticz)
>> Validating environment...
>> Environment validation passed (arch: x86_64, OS: linux)
>> Checking package dependencies...
>> All required packages are already installed
>> Downloading latest beta version...
domoticz_update.tgz               100%[=============================================================>]  16.09M  8.77MB/s    in 1.8s    
>> Download complete. Verifying archive integrity...
>> Archive integrity verified.
>> Checking for updated upgrade script...
>> Found updated script, re-executing...
>> Starting Domoticz beta Update
>> Script: updatebeta (Directory: /home/bolt/domoticz)
>> Validating environment...
>> Environment validation passed (arch: x86_64, OS: linux)
>> Checking package dependencies...
>> All required packages are already installed
>> Running updated script - proceeding with installation...
>> Stopping Domoticz service...
>> Creating backup: backups/domoticz_backup_20251211_200409.tar.gz
>> Backup complete.
>> Installing new version...
.........................................>> Installation complete.
>> Starting Domoticz service (please wait)...
>> Service started successfully.
>> Update completed successfully!

So no issues with beta update when running from cli. Update issues when running from Web.
This is some worrying because when trying to update from current stable to next stable with the same script it possibly also goes wrong....

Posted: **Friday 12 December 2025 6:16**

Thank you for testing.

Yes, this needs to be solved before making a new stable.

I will try to do this in the coming week, traveling the next few days with a huge jetlag

Posted: **Monday 15 December 2025 15:12**

Well i also have difficulties:

Spoiler: show: >> Starting Domoticz beta Update
>> Script: updatebeta (Directory: /home/xxxxx/domoticz)
>> Validating environment...
>> Environment validation passed (arch: x86_64, OS: linux)
>> Checking package dependencies...
>> All required packages are already installed
>> Downloading latest beta version...
domoticz_update.tgz 100%[=============================================================================>] 16.09M 26.5MB/s in 0.6s
>> Download complete. Verifying archive integrity...
>> Archive integrity verified.
>> Checking for updated upgrade script...
>> Found updated script, re-executing...
>> Starting Domoticz beta Update
>> Script: updatebeta (Directory: /home/xxxxx/domoticz)
>> Validating environment...
>> Environment validation passed (arch: x86_64, OS: linux)
>> Checking package dependencies...
>> All required packages are already installed
>> Running updated script - proceeding with installation...
>> Domoticz service does not exist - skipping service stop

it says the service does not exist, but it is just running fine:

Spoiler: show: systemctl --type=service --state=running | grep domoticz
domoticz.service loaded active running domoticz_service

16995 --> 16997

So i put "systemctl --type=service --state=running | grep domoticz" inside the script, instead of "systemctl list-unit-files | grep -q domoticz" but it still says domoticz not running???
And then:
tar: ./domoticz.db-wal: file changed as we read it
tar: .: file changed as we read it
>> Backup creation failed!

Ok i stop domoticz manually then updatebeta and it works, so thats i nice. But the script does not. I see here that it is a known fact. But i thought i'd give some information.Hopefully it will get sorted, thanks for everything

oh the reason i change it was that systemctl list-unit-files, comes up with nothing and --type=service --state=running, comes up with it.

Spoiler: show: $systemctl list-unit-files | grep -q domoticz

$ systemctl --type=service --state=running | grep domoticz
domoticz.service loaded active running domoticz_service

Posted: **Monday 15 December 2025 22:16**

same problem with latest 2 beta updates.
When running from commandline: no problems.
Only when clicking update from gui.

Posted: **Tuesday 16 December 2025 11:13**

Sorry for late reply, yes update error still exists for me too on 16997, a stop / start from cmd solves the problem and the update has indeed been applied. Like @waltervl I am using this on a test system to check all the updates before the final release.

Posted: **Tuesday 16 December 2025 12:15**

Just for information: i have seen this behavor also on the stable version of Domoticz (versions 2024.x and 2025.x) For me it is (was) not a big issue because after a stop and start of the domoticz service everything was working normal, without problems and errors, on the new version.

Posted: **Tuesday 16 December 2025 13:54**

Dave21w wrote: Tuesday 16 December 2025 11:13 Sorry for late reply, yes update error still exists for me too on 16997, a stop / start from cmd solves the problem and the update has indeed been applied. Like @waltervl I am using this on a test system to check all the updates before the final release.

I did not test that indeed if just a service restart would work too after a failed gui update....

Posted: **Tuesday 16 December 2025 18:37**

waltervl wrote: Tuesday 16 December 2025 13:54
Dave21w wrote: Tuesday 16 December 2025 11:13 Sorry for late reply, yes update error still exists for me too on 16997, a stop / start from cmd solves the problem and the update has indeed been applied. Like @waltervl I am using this on a test system to check all the updates before the final release.
I did not test that indeed if just a service restart would work too after a failed gui update....

Tested this with updating to build 16997 and indeed the gui update failed again. Stopping and starting the service did the trick. A service restart did not work.

Posted: **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...

Domoticz

beta update error over webgui

beta update error over webgui

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error

Re: beta update error