RGB MQTT publish sets `color_mode` to `hs` instead of `xy`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
When I publish an MQTT message with an RGB value, Zigbee2MQTT logs the resulting state as color_mode: hs.
According to the documentation, setting a color through RGB should use color_xy and set color_mode to xy. The current behavior is confusing and makes it difficult to configure RGB reliably for this device.
Device: https://www.zigbee2mqtt.io/devices/EBF_RGB_Zm.html
This is an Awox (EGLO) device. In the native application, both the RGB strip and the main light can be turned on and controlled independently, including RGB colors, without any issues.
What did you expect to happen?
Publishing an RGB value via MQTT should set the device color through color_xy and report color_mode: xy, as described in the documentation.
How to reproduce it (minimal and precise)
- Publish an MQTT message that sets an RGB value for the device.
- Check the Zigbee2MQTT log or resulting state.
- Observe that
color_modeis reported ashsinstead ofxy.
Zigbee2MQTT version
2.13.0
Adapter firmware version
8.0.2
Adapter
Sonoff Dongle-E
Setup
HAOS, RPi5
Device database.db entry
No response
Debug log
No response
Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the RGB MQTT publish on the Awox EBF_RGB_Zm device with Zigbee2MQTT 2.13.0, then compare the resulting state with the documented RGB behavior. Trace the publish handling and resulting color state, and consider the issue done when RGB publishes use color_xy and report color_mode: xy for this device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100