Tuya stuck on deprecated API #98
Replies: 2 comments 1 reply
|
🏷️ I've automatically added the |
0 replies
|
This is not a feature request, nor an issue from Home Assistant. The base of our integration is written by Tuya, and runs on the libraries provided by Tuya itself. This open-source project (and thus the API implementation) is owned and maintained by Tuya. It would be more fitting to report this with Tuya. ../Frenck |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Integration name
Tuya
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tuya/
Describe the enhancement
The Tuya integration is using a deprecated API. This issue has been reported, noting that several fields are missing. These missing fields are also discussed in the underlying Tuya Device Sharing SDK used to access the API.
Use cases
This is important because the current Tuya implementation in Home Assistant does not align with the official Tuya API. Home Assistant appears to use a private or undocumented API, which results in discrepancies compared to other libraries such as tinytuya.
As highlighted in the issue report, I provided an example showing the expected output versus the actual response received.
The primary goal should be to either update the endpoints being used or consider migrating to a better-supported and actively maintained package that aligns more closely with the official Tuya API.
Anything else?
No response
All reactions