Request to fix mode values for Product id ro2kyynmf6vb1l9u

[scoobydo]

The Home Assistant official Tuya integration no longer works with my Tuya thermostat. The integration developers enforced stricter validation on the responses coming from Tuya cloud and now my device (and many others) no longer work in Home assistant since the integration shows it as 'unknown'. This is because Tuya cloud is passing a non-standard mode of 'home' back to the integration I think, and the new stricter validation is returning a failure now instead of ignoring it.

Found invalid enum value home for datapoint mode in product id ro2kyynmf6vb1l9u, expected one of ['auto']; please report this defect to Tuya support

[JamesG]

hi，your issue has been received, and we are currently conducting verification.

[scoobydo]

Thanks. To review the diagnostics and see more please read this GitHub thread. https://github.com/home-assistant/core/ ... 3670703077

My profile name is Gdkkauowj33 so hopefully this gives you a lot more to work with.

[JamesG]

Thank you for your reply.

We have now identified the root cause of the issue and would like to explain it to you as follows:

To facilitate the personalized product presentation of developers' software products, the cloud side of Tuya processes device-reported messages via the MQTT channel and forwards them to external developers (including Home Assistant).

This process includes the reporting of non-standard instruction sets—these are customized functions implemented by manufacturers to enhance the competitiveness of their products.

If the Tuya integration script in Home Assistant does not incorporate fallback handling for these non-standard instruction sets, the device status may be displayed as "Unknown".

However, this will not affect the normal usage of your devices in Home Assistant for the time being.

We will prioritize exploring and implementing an optimization solution for this issue as soon as possible.

[scoobydo]

Hello, thank you. It does impact the device in home assistant since it shows up as 'unknown' in the interface. At that point the device status is no longer available.

What is the solution? Do you need to fix it, or does the homeassistant integration need to have fallback handling?

[JamesG]

We will consider not pushing non-standard DP values to Home Assistant, because even if the push is successful, the final displayed results will still be incorrect according to the previous logic of the plugin.

[scoobydo]

Ok sounds good. What is the timeframe associated with a fix?

[JamesG]

Hi,

We are currently conducting an evaluation and will try to resolve the issue within this week.

Please note that once non-standard commands are no longer reported to Home Assistant, when you perform operations using non-standard commands in the APP, the Home Assistant panel will not respond.

To explain this further: the Tuya APP panel is custom-developed for the product by a dedicated team, so it supports one-to-one mapping for all command functions. However, the Home Assistant plugin only supports the display of functions covered by the standard command set, resulting in slight functional discrepancies between the two.