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
New Tuya Integration 'Permission Deny' Error (Upstream issue at Tuya) #58145
Comments
Hey there @tuya, @zlinoliver, @METISU, @frenck, mind taking a look at this issue as it has been labeled with an integration ( tuya documentation |
I had the same problem, however, I tracked it down to this: https://www.home-assistant.io/integrations/tuya#1106-permission-deny Tuya made some changes on their end, I had to fix my datacenter settings in their developer console and re-link the app. |
I followed the instructions all in one go, so only a couple of minutes passed in between linking the app in the dev console and trying to add the HA integration. I actually first assumed that I had to wait for some kind of propagation, but an hour and then a day later, the error remained the same. So I don't think it could be due to a change on their end, unless you mean that the instructions are out-of-date and there's a new step that I'm missing? What do you mean by fixing the datacenter settings? |
I just tried adding US East to the datacenter list, in addition to US West. I then unlinked my app account and re-linked it. Still the same error. The "Availability Zone" link in the documentation, under the 1106 error heading, is also semi-broken. It points to a doc in the tuya-home-assistant repo, which tells you to look at the app's "Account and Security" settings for "Region", and then says that "The Region field is what to be entered in Data Center". But my region in the app is "United States of America / Canada", which doesn't help me know whether to use US West or US East. That page also says "For more information about the data centers, see Correspondence of regions and data centers." However, that is not a link and there's no such heading on the page. There's just a lot here - no logging, no details in the error, missing documentation, etc. - that makes this integration feel unfinished. It's disappointing, because the old Tuya integration was incredibly easy to set up and worked perfectly. |
US East/West is sufficient, mine previously had all of the datacenters and it prevented linking the dev account to the app. Tuya made some other changes (Oct 21) that are advertised with a banner at the top of the page. Some of the basic API permissions have been consolidated along with other changes. The documentation is a bit out of date but the basics are still right. Make sure you can see your devices in the dev account after linking, make sure you've enabled the right API permissions, remove the Tuya integration and re-add it (don't worry, your entities will stay the same), select the right app (I use Smart Life) and zone (1 - USA), then punch in your app credentials. If that doesn't work log out of the app and log back in with your existing credentials to verify they're still correct/valid/haven't been force changed by Tuya. |
Yep, that's exactly what I had tried. I just went through it one more time: un-linked my app account from Tuya IOT, signed out of the app, signed back in, linked the app account again, confirmed that the app shows that it's linked to my Cloud Development Project, confirmed that my devices show up in Tuya IOT, then tried to set up the integration again using the exact same app account and password that I had just used to sign in. Same error. :( The only difference from what you wrote is that when setting up the integration I don't see any option to choose Tuya v.s. Smart Life, and I don't have a number next to the zone name. This is what I see: (Ignore the "Extensions" text; just a tooltip that was up when I took the screenshot) |
Oh, and yes, I confirmed under the Tuya IOT "My Services" pane that I'm "Subscribed" to the new "Device Connection Service", as well as "Device Status Notification", "Authorization", "Smart Home Scene Linkage, and "IoT Data Analytics. |
That more closely matches the dialog described in the documentation. I'm running Home Assistant 2021.8.8 and mine asks for my app password so I'm not sure what the deal is there, other than mine works and yours doesn't =) |
You're using the old Tuya integration. Mine worked great in 2021.9.6 and earlier as well, but in 2021.10.0 the Tuya integration was replaced with a completely new one. |
I've the exact same issue as you during my test today.
Like you, I'm running out of options unfortunately :/ |
Can we please have the new Tuya integration rolled back, or at least have the old one reintroduced as a "Tuya Legacy" option? There are many other issues being reported with the V2 integration. Please give us the option to use the old one until V2 is stable. |
With HA new version 2021.11 the Tuya integration has stopped working. With the previous version 2021.10 it worked correctly. |
Same authentication issue for me. Updated Home Assistant Core to latest version 2021.11.0 and tried to setup the tuya integration for the first time. What I did so far is:
App is working fine as well as Postman and Node Red. Debug log only shows username / password wrong. |
Same here.
|
Same here. Was using Tuya V2 with no issues. Upgraded to 2021.11 and started getting 1106 error. Have removed Tuya V2 integration and tried to install the HA Tuya integration but also get 1106 error. Have double checked subscribed services and all seems okay. Had tested HA Tuya under 2021.10.* and it worked, but I backed it out due to lack of device support. |
I switched from V2 to the main one and no issues. Make sure you use the login data of your app, not the login to the IOT site. |
In my case the mail address and password is the same for IOT site and app. |
I just checked my password for the app and it is correct (also the same for IOT and app). |
I can confirm I'm having exactly the same problem, worked fine on 2021.10, but since updating to 2021.11 it's giving the 1106 permission deny error. |
I confirm as well, exactly the same problem, worked fine on 2021.10, but since updating to 2021.11 today it's giving the 1106 permission deny error. |
I was using 2021.11 beta version without issues. And yesterday I installed the new official 2021.11 release. After that it also worked without issues. This morning I did a restart and now I also get the "permission deny error" in my logging. So it seems to me that there is an issue with the Tuya platform itself. |
I confirm as well, exactly the same problem, worked fine on 2021.10, but since updating to 2021.11 today it's giving the 1106 permission deny error. |
Right, I downgraded my system to 2021.10.7 and I have the same issue, yesterday it worked fine... |
I confirm as well, exactly the same problem, worked fine on 2021.10, but since updating to 2021.11 today it's giving the 1106 permission deny error. |
Same issue here. Worked on 2021.10 but I get the 1106 error with 2021.11 today. |
1 similar comment
Same issue here. Worked on 2021.10 but I get the 1106 error with 2021.11 today. |
I've seen the error a few times on 2021.10.x, but it didn't stop working so i didn't look into it. after upgrading to 2021.11 it stopped working altogether. |
Started working for about 10 minutes, and now it's stopped again. |
nope...stopped again |
anybody else still having the issue?? |
Yes, still happening. Earlier today I was able to connect, but now I get 1106 - permission deny. |
ℹ️ update.This is an upstream issue @ Tuya. They are working on a solution. |
Managed to login an hour ago and started fixing all my name migrations from V2 to Core .. then it all fell over again. Same 1106 error. Hopefully this will prove to Tuya user reliance on cloud isn't the best idea and will include local at some point in the future. |
I noticed my upgrade from 2021.10.x to 2021.11.0 broke the Tuya integration again. Was previously forced to select country Germany to login. Now unable to login as my real country South Africa or Germany. Getting the same 1106 Permission Deny error. |
@CraigN Please, see a couple of messages above yours... Your comment will not help with that. Please have some patience while they resolve their issue. |
Do we have any eta on resolution? Or I just need to have faith🤣 can’t be to soon to have local control 🥳 |
I was able to get the integration to work by removing the eastern American data center and adding the western American data center to my IOT application and relinking that to my Tuya app account |
hey, doing what @scambo00 suggested worked for me as well! |
not a working solution for europe |
I managed to login now. It still said 1106 and then i switched to United States and back to my location and finally it works. |
I tried the same. However, when I try to relink the account and scan the QR Code from my App, it errors because my app apparently stored everything in a different data center. Or I'm doing it wrong. :) I'll just wait and see what happens here. Edit: I spoke to soon. I just looked and mine is working again. I just deleted my link and re-setup to the same Western America data center. |
Found working solution...tested!! |
Changing my password, then changing it back worked for me too. |
Didn't work for me..... |
Well, I've really screwed mine up now, as I can't re-link the integration due to "device deployed to another data centre". Been through every single one and can't see where ... grrr. |
You can have multiple data centers. When the issue first started I unlinked the account added all data centers in Europe and relinked it. |
Changing password and then changing it back fixed it for me as well. |
You can, but I'm completely unable to relink to any data centre apart from China, and then I am blocked from using that. Tuya is FUBAR at present. I've tried everything, but this trust in HA and Tuya getting things done is massively undermined. Their IOT website is poor, the inability to remove a cloud project to wipe a slate clean is just massive warnings about their level to detail. |
Tried and true fix: in Tuya/Smart life app, change your password and then change it back to what it was. Restart HA, it will log in and Tuya integ will work. |
Can confirm that changing password fixed the issue. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Update on this one for anyone playing along and still has issues! |
The problem
I updated to HA Core 2021.10.6, removed the old Tuya integration, and tried to add the new one, but I'm getting a "permission deny" error. I followed the instructions very carefully:
When I click "Submit", red text "Login error (1106): permission deny" appears.
I verified that my account and password were correct by signing out of the Tuya app and then signing back in with the same username + password
Nothing at all is shown in the HA log.
What is version of Home Assistant Core has the issue?
core-2021.10.6
What was the last working version of Home Assistant Core?
core-2021-9.6
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Tuya
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tuya/
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: