describe the changes between the device operation problem in Detail. What is the curernt state, what is the desired state ?
Desired state (behaviour on the previous adapter version):
Writing a color to the color state - as a named color (blue), as hex (#0000FF) or as RGB - puts the light into RGB mode and the light physically shows that color.
Writing to color_temp puts the light back into white mode with the requested color temperature. Switching back and forth between color and white works in both directions.
Current state (adapter 3.5.5):
Writing to the color state has no effect on the color of the light. The light stays in white mode; only the white tone changes. It never shows red, blue or any other color.
No error is logged and the operation is reported as SUCCESS, so from ioBroker's side the write appears to have succeeded.
On/off, brightness and color_temp still work normally. The problem is limited to the color state.
What changed:
Nothing on the device side - same hardware, same firmware, same pairing, no re-pairing in between. Only the adapter version changed. Downgrading restores working color control, upgrading breaks it again. No external converter is involved in either case; this is the built-in definition in both.
Device information (Type of the device, including the Z2M link to the device description page)
modelZigbee:TS0505B https://www.zigbee2mqtt.io/devices/14149505L_14149506L_2.html
Coordinator firmware version
20250321
Coordinator
Sonoff Zigbee 3.0 (ZStack3x0)
Setup
Proxmox Container
Current adapter version
3.5.5
Protocol of the error (as text, encapsulated in multiline code tags <>). Logs which are too big to be shown in the issue MUST be trimmed so that they fit, e.g. by removing duplicate warning messages.
No warning/error in console, but no effect. Color is not changing. This is the debug log:
zigbee.0 2026-08-17 11:23:48.102 warn ELEVATED:I04 (c500) value generated 'true' from device 'ComputerAmbilight (60a423fffe70cc3d)' for 'Switch state'
zigbee.0 2026-08-17 11:23:48.101 warn ELEVATED:I02.2a (c500) converter 2 : Cluster genOnOff
zigbee.0 2026-08-17 11:23:52.596 warn ELEVATED:SUCCESS (d607) convert result {"state":{"color_mode":"xy","color":{"x":0.7006,"y":0.2993}}} for device 'ComputerAmbilight (0x60a423fffe70cc3d)'
zigbee.0 2026-08-17 11:23:52.504 warn ELEVATED:O05 (d607) Attempt 1 at converting data for color with preparedValue {"r":255,"g":0,"b":0}, meta.state {"state":"ON"}, meta.message {"color":{"r":255,"g":0,"b":0}}
zigbee.0 2026-08-17 11:23:52.504 warn ELEVATED:O04 (d607) convert color with value {"r":255,"g":0,"b":0} and options {"state":"ON","transition_time":8,"transition":8} for device 'ComputerAmbilight (0x60a423fffe70cc3d)' without Endpoint
zigbee.0 2026-08-17 11:23:52.503 warn ELEVATED:Oo4.1 (d607) Overriding' converter to converter with key(s)'["color","color_temp","color_temp_percent"]}
zigbee.0 2026-08-17 11:23:52.503 warn ELEVATED:Os4.0 (d607) Setting' converter to converter with key(s)'["brightness","color","color_temp"]}
zigbee.0 2026-08-17 11:23:52.500 warn ELEVATED:O03 (d607) Publishing to 'ComputerAmbilight (0x60a423fffe70cc3d)' of model 14149505L/14149506L_2 with color
zigbee.0 2026-08-17 11:23:52.499 warn ELEVATED:O02 (d607) Change state 'color' at device 'ComputerAmbilight (0x60a423fffe70cc3d)' type '14149505L/14149506L_2'
zigbee.0 2026-08-17 11:23:52.455 warn ELEVATED:O01 (d607) User state change of state
zigbee.0.60a423fffe70cc3d.color with value red (ack: false) from system.adapter.admin.0
Previous adapter version
3.3.5
Protocol of the error (as text, encapsulated in multiline code tags <>). Logs which are too big to be shown in the issue MUST be trimmed so that they fit, e.g. by removing duplicate warning messages.
in version 3.3.5 color change did work. This was the debug log:
zigbee.0 2026-08-17 11:21:16.751 warn ELEVATED:SUCCESS (74e3) convert result {"state":{"color_mode":"hs","color":{"hue":240,"saturation":100}}} for device 0x60a423fffe70cc3d
zigbee.0 2026-08-17 11:21:16.570 warn ELEVATED:O04 (74e3) convert color with value {"r":0,"g":0,"b":255} and options {"state":true,"transition_time":8,"transition":8} for device 0x60a423fffe70cc3d without Endpoint
zigbee.0 2026-08-17 11:21:16.566 warn ELEVATED:O03 (74e3) Publishing to 0x60a423fffe70cc3d of model 14149505L/14149506L_2 with color
zigbee.0 2026-08-17 11:21:16.566 warn ELEVATED:O02 (74e3) Change state 'color' at device 0x60a423fffe70cc3d type '14149505L/14149506L_2'
zigbee.0 2026-08-17 11:21:16.516 warn ELEVATED:O01 (74e3) User state change of state zigbee.0.60a423fffe70cc3d.color with value blue (ack: false) from system.adapter.admin.0
mod Edit: Code Tags
describe the changes between the device operation problem in Detail. What is the curernt state, what is the desired state ?
Desired state (behaviour on the previous adapter version):
Writing a color to the color state - as a named color (blue), as hex (#0000FF) or as RGB - puts the light into RGB mode and the light physically shows that color.
Writing to color_temp puts the light back into white mode with the requested color temperature. Switching back and forth between color and white works in both directions.
Current state (adapter 3.5.5):
Writing to the color state has no effect on the color of the light. The light stays in white mode; only the white tone changes. It never shows red, blue or any other color.
No error is logged and the operation is reported as SUCCESS, so from ioBroker's side the write appears to have succeeded.
On/off, brightness and color_temp still work normally. The problem is limited to the color state.
What changed:
Nothing on the device side - same hardware, same firmware, same pairing, no re-pairing in between. Only the adapter version changed. Downgrading restores working color control, upgrading breaks it again. No external converter is involved in either case; this is the built-in definition in both.
Device information (Type of the device, including the Z2M link to the device description page)
modelZigbee:TS0505B https://www.zigbee2mqtt.io/devices/14149505L_14149506L_2.html
Coordinator firmware version
20250321
Coordinator
Sonoff Zigbee 3.0 (ZStack3x0)
Setup
Proxmox Container
Current adapter version
3.5.5
Protocol of the error (as text, encapsulated in multiline code tags <>). Logs which are too big to be shown in the issue MUST be trimmed so that they fit, e.g. by removing duplicate warning messages.
No warning/error in console, but no effect. Color is not changing. This is the debug log:
Previous adapter version
3.3.5
Protocol of the error (as text, encapsulated in multiline code tags <>). Logs which are too big to be shown in the issue MUST be trimmed so that they fit, e.g. by removing duplicate warning messages.
in version 3.3.5 color change did work. This was the debug log:
mod Edit: Code Tags