Müller Licht Tint GU10 RGBCCT Bulb isn't showing up as RGB-Capable in HA

[RubenKelevra]

The problem

My Müller Licht Tint Reflektor 350lm GU10 RGBCCT Bulb only show up as CCT not RGBCCT in HA:

What version of Home Assistant Core has the issue?

2022.11.5

What was the last working version of Home Assistant Core?

unknown

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

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

Diagnostics information

zha-8e524e4ed1fc3a6e06817777d318db3a-MLI tint-ExtendedColor-d1190f9d3090994de4b2107e98d3b09c.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[issue-triage-workflows[bot]]

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.

[TheJulianJES]

Did you see my response in the other issue? This might have been fixed in one of the last HA releases. Try to remove and re-pair the bulb. Otherwise, create an issue in the zha-device-handlers repo.

[RubenKelevra]

That's an annoying bot action. Closing valid bug reports without looking at them achieves only additional workload for the team, for re-opening bugs which got automatically closed and add frustration for the users which go the extra mile to report issues.

I would recommend to mark them as stale, if you think that helps you organizing. But expecting that users who reported the bugs fight your bots just to keep the reports from beeing closed, gives a pretty unfriendly atmosphere.

[frenck]

It closes stale issues, all you have to do is respond if it still occurs in the most recent version. It adds information and the bot will back off. That simple.

Without it, our issue tracker would grow, with (mostly) already solved issues (often as a side effect).

It is not here to be annoying, it is here to keep our issue tracker current and full of still legitimate issues that can be taken care of.

../Frenck

[RubenKelevra]

But closing a ticket will hide it in the search for issues. This leads to other people not confirming the issue and instead leads to duplicates beeing created.

Sure, the bug tracker will grow - but on the other hand noone confirmed that the bugs are really not happening anymore - if noone looked at it again.

So the assumption that everything beeing closed by the stale bot has been fixed may just not be true.

So I think closing them after a short while isn't a good decision. Maybe the community could help here by searching for issues marked stale and try to confirm them?

This could help to reduce the load on the devs and add additional information/confirmation to the issues happening.

[frenck]

But closing a ticket will hide it in the search for issues.

It does not, I search history all the time (not just for issues, but also for historical changes in PRs). Please consult the GitHub documentation if you need more help on how to use their search.

For all the rest, I think we should not continue the discussion here, as it is not the right place and not fitting. If you have a request, please use our community forums, which is the place set up for discussions like these.

../Frenck

[TheJulianJES]

@RubenKelevra Like mentioned by the bot (and me in your other very similar issue), did you check if the issue is still present with HA Core 2023.3.0 and later?

You might need to remove the device, re-add it, and then check again.

[issue-triage-workflows[bot]]

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.

[RubenKelevra]

I've switched back to Z2M because there's too much stuff not working with ZHA

[issue-triage-workflows[bot]]

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.