-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tuya Integration - Devices showing as Unavailable #134180
Comments
Hey there @tuya, @zlinoliver, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) tuya documentation |
I have the same problem, it |
Same here. |
Same here... |
Same here , working with tuja an smartlife app...not in HA 2024.12.5 |
Same. Just HA Comms issues with Tuya. Most of the time it can't read device status and won't respond to commands... But it almost never shows any errors. Core 2025.1.0b2 |
same here, commands not working. |
Same here. 8 sets of curtains, 2 sets marked as Zemismart (3 yrs old) work fine, 6 sets Quoya QL500 found but not supported. Seems crazy. |
i have the same prolem Core 2024.12.5 HaOS |
Same problem. I have three lights that shows up normally, but no commands are going through, or if they do, they do so with extreme delay. Everything working fine in Smart life app. |
Same thing - commands sometimes don't work! |
The problem
Hello, I was able to connect Tuya and my devices are populating on HA, however they are showing as unavailable. They are working on my "Smart Life" app.
What version of Home Assistant Core has the issue?
core-2024.12.5
What was the last working version of Home Assistant Core?
core-2024.12.5
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: