-
-
Notifications
You must be signed in to change notification settings - Fork 330
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
Can't complete Link Tuya App Account #573
Comments
Have the same problem, didn't managed to fix it yet, tried to clear the cache for the app, changed password, as it was mentioned somewhere else... Nothing works... Any ideas how to get the device ID's w/o that stupid API? |
I opened a ticket with Tuya and they responded next day. They suggested I change my Data Center to Western USA even though I am in NC. That solved the problem and I was able to link my account. Now back to mqtt |
Thanks kxkayser, changing the datacenter to western usa fixed it for me as well. Been trying to get it connecting for over a month to smart home. |
Glad it worked for you too. I was able to integrate my Tuya devices with my other devices on the same Node-Red dashboard. Just what I wanted. |
Ran into the same issue today. Glad I found this, since it worked for me as well! |
Ran into the same issue as well - went through a whole heap of troubleshooting - turns out you need access to the magic table the lists each of the data centres - here is a link to it. Once i entered Central Europe (makes sense for Australia - NOT) all went OK Craig |
Hi. Following the steps in "Listing Tuya devices from the Tuya Smart or Smart Life apps". When I scan the QR code in the Smartlife App, the confirmation is successful and the "Link Tuya App Account" pops up on the Tuya site. I select the Automatic Link and Read, write and Manage options and click OK. Then 2 quick pop-up lines appear near he top of the browser window that say "x - capp_binded_userid". They disappear and I am still in the link screen. See attached. No devices are discovered or added to the project
.
The text was updated successfully, but these errors were encountered: