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 ...

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 ...

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 ...

It’s probably the V2, the white square one, not the new black Pro version. The previous model!

Hi Jolle,
just to let you know: I have already opened a new issue on the official Domoticz GitHub regarding this exact crash in the Philips Hue integration.
Gizmocuz and the team are now aware of it.

My symptoms are identical to yours:
• Domoticz runs for years without issues
• After updating to ...

and this error:
2025-11-22 19:16:26.539 Error: PhilipsHueV2: FetchDevicePower HTTP GET failed (https://192.168.1.2:443/clip/v2/resource/device_power)

Hi all,

Even though I’m using the latest beta, with my older (white) Philips Hue bridge I keep getting these errors in the log:

2025-11-22 19:01:24.349 Error: PhilipsHueV2: FetchDevices HTTP GET failed (https://192.168.1.2:443/clip/v2/resource/device)
2025-11-22 19:01:24.575 Error: PhilipsHueV2 ...

Hi Richard,

I just wanted to add that I’m in the same situation. My Hue Bridge is running the same software version as yours: 1.74.197….
It’s the white square bridge, which has always worked for years over plain HTTP without any problems.

Now Philips is selling the new “Hue Bridge Pro” (the black ...

Just to add some extra information based on further testing.

With the latest beta (16922), the CPU usage on my Pi 3B stays around 15–20% on average when the Philips Hue hardware is enabled (around 20–30 devices on a Hue V1 bridge).
This is very high for a Pi 3B and has a real impact on the system ...

Thanks for your feedback.
I also upgraded to the latest beta (16922) and with around 20–30 Hue devices I’m seeing an average CPU load of 15–20%.
On the stable 2025.1, instead, my system sits around 5% CPU on average, so for now I prefer staying on the stable release.
To me it looks like there is ...

Hi, I’m chiming in because I’ve encountered exactly the same issue with the stable 2025.1 release of Domoticz on Raspberry Pi OS Bullseye.

In my case, Domoticz regularly crashes after a few minutes/hours of operation when using the old Philips Hue bridge (port 80).

Here’s my experience:

I updated ...

Hello,

I just wanted to thank you for the clarification regarding the changes in the JSON API. I now understand that the old command:

/json.htm?type=devices

has been replaced with:

/json.htm?type=command&param=getdevices

I appreciate the heads-up and the explanation—it was very helpful in ...

Hello everyone,

I'm currently running Domoticz 2025.1 (16657) because I need the Netatmo OAuth2 support (which is not available in the stable version yet).
Everything works fine when accessing the Domoticz web interface (e.g., http://192.xxx.x.x::8080/), but whenever I try to access the JSON API, I ...

My Netatmo data reception has resumed, and everything is working again. I don’t fully understand the reason either.

Basically, I wanted to upgrade from my stable version 16157 to the latest beta, which includes the new Netatmo plugin. While doing this, I started by updating the operating system (I ...

@jpcasta Sorry, I didn't realize that you're already using the new authentication method: version build 16406. My mistake—I’m using the stable version build 16157. So switching to the new authentication method doesn’t help. Let's wait for them to complete their migrations. Thanks!

I also saw this communication from March 12. Thanks for the info!
So it would seem that the issue is with Netatmo and that the Domoticz beta is also affected by it.

Same issue with my Domoticz 2024.7 (build 16406)

Error: Netatmo: Invalid/no data received...

I also have the stable version from July 2024.
The thing is, I would also like to try the new authentication mode provided by the latest Domoticz beta, but I’d like to know—from those already using the ...

Hallo,
the same thing happened to me.
I also installed the latest stable 2023.2 but no luck.
Netatmo authentication is not implemented in this version either.

This was implemented in the last beta I tried and here the connection with Netatmo works.

In the latest beta, however, the OpenZwave Stack ...

The beta that I find in the link you reported is the last one and it doesn't suit me because support for OpenZwave Usb controller has been removed.
I need the previous beta from September which I can no longer find for Raspberry.
It's an older beta that should already have the new Netatmo ...

Is there any way or some forum user can tell me, or give a download link, about the beta version 2023.2 (build 15667). (11-Sep-2023).
Unfortunately, the July 2023.2 stable release does not include Netatmo's new OAuth2 authentication and the latest beta works with Netatmo but no longer has Openzwave ...