Philips Hue related crashes

[Gravityz]

I think everybody with problems need to specify excactly what type of bridge they have

from memory (i might be wrong)
v1.0 round white version, support stopped 2020
V2.0 square white one should be still supported product code xxxxx
V2.1 square white one i think with a bit more memory. productcode xxxxa
pro, latest one black square faster, more mem

i do not think philips will end support for the v2 in favour for the pro because there are a lot of v2 versions out there

what could be happening is they changed something in favour of the pro while it is backwards compatible with the V2 but not the v1

if domoticz uses code still based on the v1 that might be a problem

i am currectly on V2 bridge firmware 1.73
domoticz buid 16782 2025.1
i do not experience problems yet but will avoid the hue bridge update which is not mandatory

update: i see that people already are investigating, sorry just trying to help

[Matmar]

I also have the V2.0 square white bridge, not the newer black Pro model.
For me the crashes started right after the bridge auto-updated to firmware 1.74.1974063020 — before that, everything had been stable for years.

So it really looks like something introduced in this latest firmware is triggering the issue in Domoticz (probably in the old Hue integration code, as the crash always happens inside CPhilipsHue::GetGroups()).

I have already opened a new GitHub issue for GizmoCuz and the team, so hopefully we’ll get a fix or at least some guidance soon.

[gbonny]

Fellow Domoticz users, I've created a Pull Request that hopefully fixes the issues that appear since Hue Bridge version 1.74. At least it does more validations specifically in GetGroups().

However I have a Hue Bridge v2 with 1.74 as well and I am running Domoticz 2025.2 (no beta) on a Ubuntu 24.04.3 VM.
I have no issues at the moment so I cannot reproduce the issue, not even with beta on my development machine. I have Scenes disabled in Hue Domoticz Hardware and have Groups enabled. My Group names have no spaces or other special characters. A lot of you are running RPi's, is anyone having issues that doesn't use a RPi? My polling interval is default (10 sec) and port is set to 443.

Hopefully the PR will be merged into Development soon and hopefully the issue's will be gone.. Otherwise we have to pinpoint a bit further to find the root cause. PR to follow: https://github.com/domoticz/domoticz/pull/6459

[waltervl]

It is already merged, should be available in latest beta.

[Matmar]

Hi all,

just a quick update regarding the Philips Hue–related crashes.

I've updated Domoticz to build 16951, but unfortunately the crash still occurs on my system. The only improvement I see is that the previous PhilipsHueV2 error messages (FetchDevices / FetchContacts / FetchTamper / FetchDevicePower) no longer appear in the log — however, Domoticz still crashes, as before.

I'd like to ask if anyone else has updated to last beta and is still experiencing the same crash.
It would be helpful to know whether this is affecting multiple users.

Thanks!

[jannl]

The commit was done yesterday, I suggest using the latest build: 16954

[Peter2]

Thanks for providing the update Domoticz 2025.2 (build 16954). Hopefully this fixes the Domoticz crashes due to the Hue hardware since the Hue bridge update to software version 1974063020 (model-ID BSB002).

[waltervl]

The commit was done yesterday, I suggest using the latest build: 16954

There are no more Hue related changes after 16951, even after 16940 (the build were the Hue change landed in). So 16954 will behave the same in context of Hue as 16951 (see https://github.com/domoticz/domoticz/issues/6451)

But if everyone else using latest beta has no issues with Hue anymore?

[jannl]

How many builds are done in a day and published?

The hue cpp file had been updated yesterday.

Edit: I might be hitting the github local time issue

[gbonny]

At this moment only Matmar experiences problems. I need more information to try and solve this issue as I cannot reproduce it myself.

When you had Domoticz crashes before (before 16940), possible related to the firmware update of the Hue Bridge v2 using firmware 1.74:
- Did the a recent beta (16940 or later) fix these errors or not?

If not continue:

In Domoticz > Hardware > Philips Hue:
- What is your polling interval in? Default is 10. Philips recommends 5 seconds minimum.
- Do you have Groups enabled?
- Do you have Scenes enabled?
- Do you use an IP address as remote address or DNS?
- Which port are you using?

- How is your Philips Hue connected: Wifi or LAN cable?
- How is your Philips Hue's IP configured, DHCP, static IP or DHCP reservation?
- How many Philips Hue devices do you have?
- Do you have non-Philips Hue devices? If so which ones? Have you tried removing them to see whether the crashes persist?
- Do you use any special characters in your room names or scenes including space?
- What is your hardware you are running Domoticz on?
- How is this hardware connected to your network; Wifi or LAN cable?
- Is Domoticz running in a VM?
- Is Domoticz running in a container?
- What is your operating system/hypervisor/container platform you are running Domoticz on with exact version numbers?
- What reveals this in a shell/ssh: "netstat -an | grep WAIT | wc" ?
- How many WAIT's are there for your Philips Hue "netstat -an | grep WAIT | grep <ip-hue> | wc"?
- Anything else you think of that can matter?

Please provide as detailed as possible. Thanks!

[Woody1]

Hi,

I experienced this problem a few times and have installed the 16954 build yesterday. So far this works fine, I will let you know here if that changes.

*edit: wrong build number corrected

[Woody1]

Well, build 16954 did not solve the problem; yesterday (30-11) Domoticz quit again. I saw that a newer build was available (16972)* so I installed that and I'll see if that solves this problem.

Unless someone needs it for testing, if this latest build does not fix it I'll remove Hue from my installation; I use Domoticz hardly ever for Hue, the fact that it messes my data history is much more of a nuisance for me.

*edit: managed to mix up the build number again , fixed it.

[jannl]

I really wonder what the problem in your setup is. I heavily depend on Hue and never had any real problems.

I am running Docker on a pi 3b.

[Peter2]

After running stable for 5 days the Philips Hue Bridge hardware caused Domoticz to crash again.

Domoticz 2025.2 (build 16954) on a Pi4B running Bookworm
Philips Hue Bridge hardware connected over port 443
Hue Bridge v2 (square white, BSB002) API version 1.74 Software version 1974063020

Thread 34 (Thread 0x7f497aef40 (LWP 127328) "Hue Bridge"):
#0 0x0000007f8551b924 in __GI___wait4 (pid=146828, stat_loc=0x7f497ab3c4, opti>
#1 0x000000556a6c87b4 in dumpstack_gdb(bool) ()
#2 0x000000556a6c8d24 in signal_handler(int, siginfo_t*, void*) ()
#3 <signal handler called>
#4 __pthread_kill_implementation (threadid=546693640000, signo=signo@entry=6, >
#5 0x0000007f854e3c64 in __pthread_kill_internal (signo=6, threadid=<optimized>
#6 0x0000007f8549a8ac in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
#7 <signal handler called>
#8 __pthread_kill_implementation (threadid=546693640000, signo=signo@entry=6, >
#9 0x0000007f854e3c64 in __pthread_kill_internal (signo=6, threadid=<optimized>
#10 0x0000007f8549a8ac in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/rais>
#11 0x0000007f85487480 in __GI_abort () at ./stdlib/abort.c:79
#12 0x000000556adba6b8 in __gnu_cxx::__verbose_terminate_handler() ()
#13 0x000000556adb8ffc in __cxxabiv1::__terminate(void (*)()) ()
#14 0x000000556adb9060 in std::terminate() ()
#15 0x000000556adb91f4 in __cxa_throw ()
#16 0x000000556a5b1c34 in Json::throwLogicError(std::__cxx11::basic_string<char>
#17 0x000000556ac70a9c in Json::Value::operator[](unsigned int) ()
#18 0x000000556aa8fdb8 in CPhilipsHue::GetGroups(Json::Value const&) ()
#19 0x000000556aa930bc in CPhilipsHue::GetStates() ()
#20 0x000000556aa93318 in std::thread::_State_impl<std::thread::_Invoker<std::t>
#21 0x000000556ae38a0c in execute_native_thread_routine ()
#22 0x0000007f854e2030 in start_thread (arg=0x0) at ./nptl/pthread_create.c:442
#23 0x0000007f8554bf1c in thread_start () at ../sysdeps/unix/sysv/linux/aarch64>

[xhark]

Hello,

Same problem on my end, regular crashes (requires stopping and restarting the Domoticz service).

• Domoticz 2025.2

• Raspberry Pi 2 Model B Rev 1.1

• Philips HUE V2 (BSB002) port 443, "swversion": "1974063020", apiversion "1.74.0"
  
  Domoticz log ( Please find full domoticz log here)
  

  Code: Select all

  2025-12-04 04:12:27.053  Error: Domoticz(pid:26769, tid:26793('BM-hue')) received fatal signal 6 (Aborted)
  2025-12-04 04:12:27.053  Error: siginfo address=0x6891, address=0x76887aa4
  2025-12-04 04:12:32.752  Error: Did not find stack frame for thread (LWP 26793)), printing full gdb output:
  
  2025-12-04 04:12:32.752  Error: > gdb: warning: Couldn't determine a path for the index cache directory.
  2025-12-04 04:12:32.752  Error: > [New LWP 26772]
  2025-12-04 04:12:32.752  Error: > [New LWP 26773]
  2025-12-04 04:12:32.752  Error: > [New LWP 26774]
  2025-12-04 04:12:32.752  Error: > [New LWP 26775]
  2025-12-04 04:12:32.752  Error: > [New LWP 26778]
  2025-12-04 04:12:32.752  Error: > [New LWP 26779]
  2025-12-04 04:12:32.752  Error: > [New LWP 26780]
  2025-12-04 04:12:32.752  Error: > [New LWP 26783]
  2025-12-04 04:12:32.753  Error: > [New LWP 26784]
  2025-12-04 04:12:32.753  Error: > [New LWP 26786]
  2025-12-04 04:12:32.753  Error: > [New LWP 26787]
  2025-12-04 04:12:32.753  Error: > [New LWP 26788]
  2025-12-04 04:12:32.753  Error: > [New LWP 26789]
  2025-12-04 04:12:32.753  Error: > [New LWP 26792]
  2025-12-04 04:12:32.753  Error: > [New LWP 26793]
  2025-12-04 04:12:32.753  Error: > [New LWP 26794]
  2025-12-04 04:12:32.753  Error: > [New LWP 26795]
  2025-12-04 04:12:32.753  Error: > [New LWP 26796]
  2025-12-04 04:12:32.753  Error: > [New LWP 26806]
  2025-12-04 04:12:32.753  Error: > [New LWP 26807]
  2025-12-04 04:12:32.753  Error: > [New LWP 26808]
  2025-12-04 04:12:32.753  Error: > [New LWP 26809]
  2025-12-04 04:12:32.753  Error: > [New LWP 26810]
  2025-12-04 04:12:32.753  Error: > [New LWP 26811]
  2025-12-04 04:12:32.753  Error: > [New LWP 26812]
  2025-12-04 04:12:32.753  Error: > [New LWP 26813]
  2025-12-04 04:12:32.753  Error: > [New LWP 26814]
  2025-12-04 04:12:32.753  Error: > [New LWP 26815]
  2025-12-04 04:12:32.753  Error: > [New LWP 26818]
  2025-12-04 04:12:32.753  Error: > [New LWP 26819]
  2025-12-04 04:12:32.754  Error: > [New LWP 26832]
  2025-12-04 04:12:32.754  Error: > [New LWP 26833]
  2025-12-04 04:12:32.754  Error: > [New LWP 26834]
  2025-12-04 04:12:32.754  Error: > [New LWP 26835]
  2025-12-04 04:12:32.754  Error: > [New LWP 26836]
  2025-12-04 04:12:32.754  Error: > [New LWP 26855]
  2025-12-04 04:12:32.754  Error: > [Thread debugging using libthread_db enabled]
  2025-12-04 04:12:32.754  Error: > Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
  2025-12-04 04:12:32.754  Error: > 0x768beddc in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7ed5e988, rem=0x7                                                                                                               ed5e9a0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:62
  2025-12-04 04:12:32.754  Error: > 62    ../sysdeps/unix/sysv/linux/clock_nanosleep.c: Aucun fichier ou dossier de ce type.
  2025-12-04 04:12:32.754  Error: >   Id   Target Id                                       Frame
  2025-12-04 04:12:32.754  Error: > * 1    Thread 0x76a8b040 (LWP 26769) "domoticz"        0x768beddc in __GI___clock_nanosleep_time64 

  I prefer to wait for the next stable version and disable Hue in the meantime. I could control it from HA.
  Thank you to the developers for their time and assistance

[jannl]

Seems I was a bit optimistic, Hue also crashes my domoticz. It is just I didnt notice beacause docker solved it

[waltervl]

Are you all on latest beta 2025.2? Because there it seems fixed for user Matmar....

[Matmar]

For me the crash issue is indeed solved.
I have been running the beta versions from 167xx onward, including the current 16990, and:

Philips Hue works perfectly, both lights and sensors.
I’m using the Hue Bridge V2 (white square model), but I believe this applies to other bridges as well.
All lights respond correctly to commands.
Motion sensors operate normally.
Temperature readings are updated without any issues.

No crashes at all for more than a week of continuous operation.
So yes, the bug has definitely been fixed in the latest beta versions.

For those who prefer not to install beta releases: the fix will be included in the next stable, so you will be safe waiting as well.

Regards,
Matmar

[waltervl]

It is safe to install the current beta. There are no operational issues to use it. Only be sure you take note of the important changes if you update from an older version. See wiki https://wiki.domoticz.com/Releases#Chan ... _attention

[globetrotter]

New firmware for Hue bridge:

Dec 8, 2025

Bridge v2 Software version 1974142030

This version includes changes to support migration of multiple bridges to a Hue Bridge Pro; full functionality will be available in upcoming app releases, so stay tuned!

We’ve made several small changes behind the scenes to make your Hue Bridge v2 work even better. 

We’ll start rolling out this firmware over the next few days. Turn on automatic updates in the app to make sure you get it as soon as it’s released!
---------

Is it safe to install?