Color-Mode changes with color-changing on Eglo Ceiling light (1 large light, 1 surrounding led circle)

[senna1992]

The problem

I do see this behaviour when changing the LED-Circle color from within HA Dashboard:
The entity changes its color_mode compared to changing the settings of the large light)

This is after first setting color and then white tone and finally brightness:

min_color_temp_kelvin: 2702 max_color_temp_kelvin: 6535 min_mireds: 153 max_mireds: 370 effect_list: blink, breathe, okay, channel_change, finish_effect, stop_effect supported_color_modes: color_temp, xy color_mode: color_temp brightness: 194 color_temp_kelvin: 5882 color_temp: 170 hs_color: 29.739, 8.419 rgb_color: 255, 244, 233 xy_color: 0.343, 0.339 effect: null friendly_name: Licht.2 supported_features: 44

This is entitys state after changing color:
min_color_temp_kelvin: 2702 max_color_temp_kelvin: 6535 min_mireds: 153 max_mireds: 370 effect_list: blink, breathe, okay, channel_change, finish_effect, stop_effect supported_color_modes: color_temp, xy color_mode: xy brightness: 140 color_temp_kelvin: null color_temp: null hs_color: 244.744, 84.314 rgb_color: 57, 40, 255 xy_color: 0.15, 0.054 effect: null friendly_name: Licht.2 supported_features: 44

This is my setup:

• HA Yellow (HAY) Supervisior: 2023.12.0; OS: 11.2; Frontend: 20231208.2]
• Z2M using HAY-Zigbee-Radio [V: 1.34.0; EZSP v12; 7.3.2.0 build 212; Herdsman converter 15.130.1; Herdsman 0.25.0]

Sorry for the formatting of the middle part, i didnt get it to show up as code.

What version of Home Assistant Core has the issue?

2023.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Light settings (combinaed rgb and ccw light)

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

This might be related:

`Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:421
First occurred: 10:59:00 (1 occurrences)
Last logged: 10:59:00

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:
    b'\x16\x03\x01'
      ^`

Additional information

This is Zigbee2Mqtt's reaction:
Zigbee2MQTT:debug 2023-12-29 11:02:21: Requested color_temp 569 is higher than maximum supported 370, using maximum!

[home-assistant]

Hey there @emontnemery, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign mqtt Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

mqtt documentation
mqtt source
_{^{(message by IssueLinks)}}

[jbouwh]

Can you share the json config published and and the payloads / actions with expected state that lead to the issue you have found.
Futher, 99 % of this type off issues is Z2M related, which is not supported.
I suggest you open a Z2M issue for this here (if you have not already done that): https://github.com/Koenkk/zigbee2mqtt/issues

[jbouwh]

The error in the logs seems something else: See also: #106533

[senna1992]

Can you share the json config published and and the payloads / actions with expected state that lead to the issue you have found. Futher, 99 % of this type off issues is Z2M related, which is not supported. I suggest you open a Z2M issue for this here (if you have not already done that): https://github.com/Koenkk/zigbee2mqtt/issues

i'm quite new to this type of investigation, best i can do atm is this:

Debug 2023-12-29 19:30:45Received MQTT message on 'zigbee2mqtt/Licht.2/set' with data '{"state":"ON","color":{"x":0.353,"y":0.321}}' Debug 2023-12-29 19:30:45Publishing 'set' 'color' to 'Licht.2' Info 2023-12-29 19:30:45MQTT publish: topic 'zigbee2mqtt/Licht.2', payload '{"brightness":216,"color":{"h":350,"hue":350,"s":24,"saturation":24,"x":0.353,"y":0.321},"color_mode":"xy","color_temp":220,"color_temp_startup":153,"linkquality":180,"power_on_behavior":"on","state":"ON"}' Debug 2023-12-29 19:30:46Received Zigbee message from 'Licht.2', type 'attributeReport', cluster 'lightingColorCtrl', data '{"currentHue":253}' from endpoint 1 with groupID 0 Info 2023-12-29 19:30:46MQTT publish: topic 'zigbee2mqtt/Licht.2', payload '{"brightness":216,"color":{"h":350,"hue":350,"s":24,"saturation":24,"x":0.353,"y":0.321},"color_mode":"xy","color_temp":220,"color_temp_startup":153,"linkquality":180,"power_on_behavior":"on","state":"ON"}' Debug 2023-12-29 19:30:46Received Zigbee message from 'Licht.2', type 'attributeReport', cluster 'lightingColorCtrl', data '{"currentSaturation":222}' from endpoint 1 with groupID 0 Info 2023-12-29 19:30:46MQTT publish: topic 'zigbee2mqtt/Licht.2', payload '{"brightness":216,"color":{"h":350,"hue":350,"s":24,"saturation":24,"x":0.353,"y":0.321},"color_mode":"xy","color_temp":220,"color_temp_startup":153,"linkquality":180,"power_on_behavior":"on","state":"ON"}' Debug 2023-12-29 19:30:46Received Zigbee message from 'Licht.2', type 'attributeReport', cluster 'lightingColorCtrl', data '{"currentX":23134}' from endpoint 1 with groupID 0 Info 2023-12-29 19:30:46MQTT publish: topic 'zigbee2mqtt/Licht.2', payload '{"brightness":216,"color":{"h":350,"hue":350,"s":24,"saturation":24,"x":0.353,"y":0.321},"color_mode":"xy","color_temp":220,"color_temp_startup":153,"linkquality":180,"power_on_behavior":"on","state":"ON"}' Debug 2023-12-29 19:30:46Received Zigbee message from 'Licht.2', type 'attributeReport', cluster 'lightingColorCtrl', data '{"currentY":21037}' from endpoint 1 with groupID 0 Info 2023-12-29 19:30:46MQTT publish: topic 'zigbee2mqtt/Licht.2', payload '{"brightness":216,"color":{"h":350,"hue":350,"s":24,"saturation":24,"x":0.353,"y":0.321},"color_mode":"xy","color_temp":220,"color_temp_startup":153,"linkquality":180,"power_on_behavior":"on","state":"ON"}'

This is the debug log from z2m when i am swichting color (moving the circle on the colorweel), hope it helps - and sorry for the lack of formatting!

Will open another ticket over at z2m tomorrow!

[jbouwh]

Please add debug logging for Home Assistant mqtt instead:

https://www.home-assistant.io/integrations/logger/

To find the config you can also click the MQTT-info button at the MQTT device page in Home Assistant,

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.