-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Bug]: Connection to device succeeded but no datapoints could be found. Please try set-up again #438
Comments
THIS IS THE CORRECT LOG FILE |
Same issue with me on two mini smart plugs, one new and one deleted to see if I can add it. Two other previously-configured mini smart plugs work fine. All 4 work fine with Tuya cloud and HA integration. All are version 3.3. |
Same here I deleted a smart switch (to test something ) and can't add it again it was working previously. |
I went to tuya.com and renewed my free iotcore subscription another 6 months. That allowed me to restore my deleted and install my new mini smart plug. All my mini smart plugs are active now. That resolved the issue. |
Thanks for the tip hope it helps some people, but that is not my issue since my iotcore only expires at 28/02/2025 |
I removed the device from mains and added again and it works now, needed a reset. |
Since Tuya device has toxic behavior when using them on fully local environment I can't be sure if this related to the integration, I tried following the step you reproduced and deleted many devices as test no issues occurs, well at least glad you fixed it. The logs you posted seems the device does connect successfully however the |
LocalTuya Version
2024.12.1
Home Assistant Version
2024.12.5
Environment
What happened?
I had previously added the device and it was working fine as a test , when i deleted it , and added it again , it was not able to find datapoints
home-assistant_localtuya_2024-12-22T15-15-05.985Z.log
Steps to reproduce.
Relevant log output
No response
Diagnostics information.
No response
The text was updated successfully, but these errors were encountered: