2024.4 Tuya integration shows wrong color mode

[bartplessers]

The problem

Hi,
Since HA 2024.4.0 I noticed that HA does not show the color mode correctly of certain Tuya bulbs,
The problem only raises for bulbs that support white and color modus, without the abality to change the white color temperature

Than

• on/off is correctly displayed
• when I change color in HA: state icon in HA shows the selected color, bulb switches to color mode
• when I switch back to white modus in the Tuya app (I can’t switch to white modus in HA): the color of the icon in HA remains in color modus although the bulb works now in white modus
• on/off works in HA, but when I want to change the brightness in HA, the old color modus is sent to the bulb

This makes that all my Tuya bulbs become more or less useless in HA:

• I can’t switch to white modus in HA
• I can’t dimm my lights because than they switch to a random color modus

Anybody same problem?
Any solution?

PS. I'm creating a new issue here because #115056 was not picked up by the @homeassistant bot

What version of Home Assistant Core has the issue?

core-2024.4.0

What was the last working version of Home Assistant Core?

core-2024.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

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

Diagnostics information

I filterd logs on device bf9447a3e3f58bed9af04x

HA 2024.4.4 (with issue)

home-assistant_tuya_2024-04-28T10-39-58.635Z.log

HA 2024.3.3 (no issue)

home-assistant_tuya_2024-04-28T10-45-09.326Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

You can find more detailed information in #115056
The main issue is that since HA 2024.4.x, it does not recognize the "brightness" modus of this tuya bulb!

What you can see here: same light, but other version of HA:

HA 2024.3.3

HA 2024.4.2

So it seems that HA 2024.4.x does not recognize the "brightness" modus of this tuya bulb!

I have a feeling that this problem was introduced with
#110327
resulting in
770e48d

To me it seems that following logic is missing in latest version

[home-assistant]

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

Code owner commands

Code owners of tuya 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 tuya 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)}}

---

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

[ph30n1x]

I am also having experiencing this issue with 5 lights. This was not previously an issue, appears to have originated with the 2024.4 release.

[bartplessers]

same problem on 2024.5.0

Please can somebody give this some attention.
I'm also using zigbee2mqtt. There is a new release https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.37.0 but ...
this release requires at least Home Assistant 2024.4.

I really want to upgrade, but this tuya issue prevents me from doing this :-(

[ph30n1x]

Please roll back the changes, this clearly wasn't fully tested and is affecting a specific type of device. As the tuya integration is part of core this needs to be rectified

[bartplessers]

just for your interest: originally I created #115056 . @Kelso-Utah provided a workaround, but only for very urgent cases, because the provide solution is "This project will no longer continue to iterate"

[bartplessers]

Problem still exist in 2024.5.1
I'm not a developer, but can somebody try to revert the following code:
770e48d

I think this is missing:

[bartplessers]

2024.5.3. Still same problem

[nollid3]

I have the problem as well. Would be nice to have it fix in this months releases