Hue errors in beta 17554

[Doler]

After upgrading to beta 17554 I got the following in the log:

Code: Select all

2026-03-27 13:33:16.021  Status: Hue: V2 bridge detected, using V2 API.
2026-03-27 13:33:17.506  
2026-03-27 13:33:17.548  Error: PhilipsHueV2: failed to fetch security_area_motion
2026-03-27 13:33:17.581  subtype           = Interface Response
.
.
2026-03-27 13:33:17.766  Status: Hue: PhilipsHue: Sensor 'Hue outdoor motion sensor 1 (Motion)' now uses V1-compatible ID 3011 (was 1253744). Old device can be removed from Settings > Devices.
2026-03-27 13:33:17.773  Status: Zigbee-Z2M: Started.
2026-03-27 13:33:17.773  Status: PhilipsHue SSE: connected to event stream
2026-03-27 13:33:17.774  Status: Hue: Worker started...

I have an old, first generation bridge that perhaps should be detected as V1?
I don't know what to do with the info on the line on Hue outdoor motion sensor 1. I do have an outdoor motion sensor that is still working as is the rest of the hue system.
The Error: PhilipsHueV2: failed to fetch security_area_motion repeats about every 10 minutes, don't know what to do about that.

Please assist.
Regards, Mark

[Doler]

Next to the above I got three new devices:
- Hue Group Motion
- Hue Group LightLevel
- Hue Group LightLevel Lux

These are specific to V2 bridge, not for V1

[gizmocuz]

Please update to the latest beta, this should already have been solved.
A big change has been made to implement more V2 sensors and also SSE , so you directly get a change visible in domoticz.

And your bridge supports the V2 API

[Doler]

Confirmed that the error is gone. Still got the status log

Code: Select all

Status: Hue: PhilipsHue: Sensor 'Hue outdoor motion sensor 1 (Motion)' now uses V1-compatible ID 3011 (was 1253744). Old device can be removed from Settings > Devices.

that I don'tunderstand. And also got the three group devices created (could ignore them though).

[gizmocuz]

You can probably control the groups and see the status. There is nothing wrong with this.

This is a one-time migration notice. After a recent improvement, Philips Hue sensors now use stable V1-compatible IDs (matching the classic V1 API) instead of the internal hash-based IDs assigned previously.

What happened: A new device was created for your sensor under the new ID (3011), while the old device (1253744) is now orphaned and no longer receives updates.

Steps to resolve:

1. Go to Settings > Devices and find the old orphaned device (it will show no recent updates).
2. Find the device in the switches tab (if it is a switch)
3. Click Edit on the old device, then use Replace button and select the new device.
4. This will migrate all references (dashboards, timers, automations, etc.) to the new device automatically.

Important: If you reference devices by name in dzVents/Lua scripts, make sure the new device has the same name as the old one.
If not, rename it before replacing, so your scripts continue to work without changes.

I changed the status message to be more clear for other users

[Doler]

I probably would have understand that if there was a new device but there isn't. And the existing device is still working like normal. So still a bit confused