Lidl bulb TS0505A has lost colours

[LeoeLeoeL]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

It's impossible to set an RGB colour. Only "whites" are available.

Steps to reproduce the behavior

Move the sliders in Phoscon never show a colour.
Same behaviour in Home Assistant.

Expected behavior

Set a colour

Screenshots

No response

Environment

• Host system: (Raspberry Pi)
• Running method: (Raspbian)
• Firmware version: (26780700)
• deCONZ version (not Home assistant Addon version!): (2.25.3)
• Device: (ConBee II)
• Do you use an USB extension cable: (yes) -- only relevant for ConBee I/II/III
• Is there any other USB or serial devices connected to the host system? If so: Which?

deCONZ Logs

No response

Additional context

For info, the lamp has the same issue in Zigbee2MQTT (using a Sonoff ZB Dongle-P).
The lamp works nomally if paired to a Hue bridge or Lidl bridge

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[LeoeLeoeL]

Is there anybody out there?

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[LeoeLeoeL]

I really would like to know if my mesh is the only one in the world that suffers this issue.

[ebaauw]

Is the light exposed by DDF or by legacy code? Please attach deCONZ GUI screenshots so the node, including endpoints and clusters, and of the _Basic _ and Color Control cluster attributes, making sure to read these first.

[LeoeLeoeL]

Hi, nice to see you.
Legacy code

Basic

On/Off

Level Control

Color Control

These Livarno lights worked OK until 6 months ago (or something more)

[ebaauw]

What about the other attributes in Color Control? Notably Color Capabilities (0x400A).

And what does the API resource look like? In particular: does it expose state/xy?

[LeoeLeoeL]

Everything else I didn't show is greyed.
{
"capabilities": {
"alerts": [
"none",
"select",
"lselect"
],
"color": {
"ct": {
"max": 65279,
"min": 0
},
"modes": []
}
},
"colorcapabilities": 0,
"config": {
"groups": [
"0",
"3"
]
},
"ctmax": 65279,
"ctmin": 0,
"etag": "610fa80cab1ba813d2fb2abc71a3a9a4",
"hascolor": true,
"lastannounced": "2024-03-21T01:11:38Z",
"lastseen": "2024-04-10T15:26Z",
"manufacturername": "_TZ3000_dbou1ap4",
"modelid": "TS0505A",
"name": "Extended color light 7",
"state": {
"alert": "none",
"bri": 255,
"colormode": "xy",
"ct": 189,
"effect": "none",
"hue": 0,
"on": false,
"reachable": true,
"sat": 254,
"xy": [
0.3012,
0.1183
]
},
"swversion": null,
"type": "Extended color light",
"uniqueid": "84:2e:14:ff:fe:02:c0:3e-01"
}

[ebaauw]

Ok, as I expected, the light doesn't expose Color Capabilities (colorcapabilities is 0). But the legacy code still exposes state/xy. Can you change the light's colour through the API (PUT to state of {"xy": [1.0, 0.0]} should turn the light red-ish)? Maybe this is a limitation of Phoscon?

Anyways, the best resolution probably is to create a proper DDF for the light, defaulting the colour capabilities.

[LeoeLeoeL]

Can you change the light's colour through the API (PUT to state of {"xy": [1.0, 0.0]} should turn the light red-ish)?

How can I do that?

[ebaauw]

Using any REST client, like Postman, or even curl.

[LeoeLeoeL]

At this time, I think, it's beyond my possibilities.

[Mimiix]

At this time, I think, it's beyond my possibilities.

You can find out how to do it here https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/

It's a very comprehensive guide

[LeoeLeoeL]

Tks, I shall try.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[LeoeLeoeL]

Keeping alive

[Mimiix]

Keeping alive

Did you test the DDF yet?

[LeoeLeoeL]

Not yet.
In this time I tried to create DDF for Vimar Covering devices but with non luck and 3 days to have one device working again.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[LeoeLeoeL]

Up