core: Tuya fan (code fs) won't show speed options
The problem
I’ve bought two Tuya fan switches with 4 buttons: light and low/mid/high speeds.
HA shows the light fine, but the fan entity only has an on/off switch (which places it in the last used speed).

Details from iot.tuya.com
- name: WiFi风扇灯
- category:
fs - Given the JSON below, this looks like a Tuya issue, since not even their IOT platform seems able to do the speed change? 🤦♂️ If that’s the case, any hint on how to report it to them?
Tuya JSON
[ { "code": "switch", "value": true }, { "code": "child_lock", "value": true }, { "code": "light", "value": true } ]
What version of Home Assistant Core has the issue?
core-2022.10.4
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
Tuya
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tuya/
Diagnostics information
tuya-02266b4b334e525dfb4a68819f7d43a3-Ventilador Cinema-35b28db8fb3875e329308d828f29474b.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
PS: the GH issue template needs some update - ~Settings > About does not show the exact version requested (with the core- prefix), nor the installation type, which might confuse some people. That seems to be available at the top-right option at the Repairs screen (which I stumbled upon at some other request, I would never think of looking for this there).~
Went ahead and PR’d it at #58933
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 19 (15 by maintainers)
I just saw another issue that was also related to Tuya inconsistencies, where Frenck showed up stating that was a non-issue, and that HA isn’t focused on bridging gaps or leveling manufacturer inconsistencies. It’s a sad reality that HA was created to group IOT devices together but doesn’t care about one of the most accessible brands - but even more importantly, that @tuya seemed to show up and planned to do better, but just disappeared and left us with amazingly weird devices, in all sorts of ways.