Tuya re-authorization problem .

[motogon]

The problem

Tuya app gives an error QR expired. Refresh it and scan again.

I have reloaded the integration but QR code is not updated

What version of Home Assistant Core has the issue?

core-2024.6.4

What was the last working version of Home Assistant Core?

--

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

home-assistant_tuya_2024-06-27T07-41-03.302Z.log.zip

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[EboBH83]

Can't find the Privacy Option on iot.tuya.com that some are referring to. Would appreciate some help. Cheers!

[StevusPrimus]

Can't find the Privacy Option on iot.tuya.com that some are referring to. Would appreciate some help. Cheers!

Before Tuya itself had taken over the integration, the process to integrate the Tuya/Smart Life/... was to have a Web Development project in iot.tuya.com. This is not needed anymore since a while. But some of us, never migrated to the new standard. So if you do not have a user and project there, you used the new process. Still I mention it here as it is MAYBE the root cause for the frequent issues since a couple of days. And @tuya might need to have a look in their integration. This is more like a hint, rather than a solution.

[motogon]

Sadly, it's been 4 days since a ticket was opened for a problem affecting a large number of HA users. But HA developers have not responded to this problem.

[MondMann2019]

Can't find the Privacy Option on iot.tuya.com that some are referring to. Would appreciate some help.

Cheers!

Deactivate all addblockers or no script services. Then try visiting the page again.

In my case this showed up after I did it.

[svptje]

Rebooted Home Assistant and retried authentication and it started working again. Saturday it was not for working for me either, despite trying multiple times.

[EboBH83]

Can't find the Privacy Option on iot.tuya.com that some are referring to. Would appreciate some help. Cheers!

Deactivate all addblockers or no script services. Then try visiting the page again.

In my case this showed up after I did it.

If this is the pop-up message, then it worked. Thanks a million.

[MondMann2019]

Can't find the Privacy Option on iot.tuya.com that some are referring to. Would appreciate some help.

Cheers!

Deactivate all addblockers or no script services. Then try visiting the page again.

In my case this showed up after I did it.

If this is the pop-up message, then it worked. Thanks a million.

No, I had another message, which asked to acknowledge the new terms.

[bernardofortes]

still not working. worked briefly after dozens of reauthentications in SAT, but stopped again.

[TobiasPSP]

You should log in to iot.tuya.com and confirm the new privacy options. At least that did the Trick for me.

Good catch. I am using the smartlife app, though. There doesn't seem to exist a corresponding website, and I have no tuya account, just a smartlife account. This has been working flawlessly so far.

Currently, HA is accepting my re-authentication again, so maybe it was a hickup on their cloud side.

Incidents like this (and the dramatic impact it has on home automation availability) make me re-eval my tuya investment. Since I have quite a number of tuya devices meanwhile, it's probably time to look into reflashing firmware for mission-critical devices.

[MondMann2019]

I have entered most of the devices in Local Tuya anyway, so I have few problems. However, it doesn't work with all devices such as thermometers. In future, however, I will only use the Zigbee standard anyway. Then I'll be independent of other manufacturers. Plus the speed is much better.

[applegeeks]

You should log in to iot.tuya.com and confirm the new privacy options. At least that did the Trick for me.

Good catch. I am using the smartlife app, though. There doesn't seem to exist a corresponding website, and I have no tuya account, just a smartlife account. This has been working flawlessly so far.

Currently, HA is accepting my re-authentication again, so maybe it was a hickup on their cloud side.

Incidents like this (and the dramatic impact it has on home automation availability) make me re-eval my tuya investment. Since I have quite a number of tuya devices meanwhile, it's probably time to look into reflashing firmware for mission-critical devices.

couldn't agree more here. A similar outage happen with Tuy a few months back and since then any broken tuya devices (lights/plugs/etc..) I've encountered since I have been slowly replacing with tappo products which proves to be a little bit more reliable than tuya based products so far.

Hoping slowly, I'll be able to replace all my tuya devices with other brands going forward as the tuya platform has proven to be a headache when it does go down.

[peteS-UK]

I have entered most of the devices in Local Tuya anyway, so I have few problems. However, it doesn't work with all devices such as thermometers. In future, however, I will only use the Zigbee standard anyway. Then I'll be independent of other manufacturers. Plus the speed is much better.

I'd use Tuya Local rather than Local Tuya, as a) it has broader device support and b) you can define your own device configs to add support for others currently unsupported.

[Just4vinnie]

Can't find the Privacy Option on iot.tuya.com that some are referring to. Would appreciate some help. Cheers!

Before Tuya itself had taken over the integration, the process to integrate the Tuya/Smart Life/... was to have a Web Development project in iot.tuya.com. This is not needed anymore since a while. But some of us, never migrated to the new standard. So if you do not have a user and project there, you used the new process. Still I mention it here as it is MAYBE the root cause for the frequent issues since a couple of days. And @tuya might need to have a look in their integration. This is more like a hint, rather than a solution.

So accepting the new terms on iot.tuya.com did not fix it for me. Then I read your feedback. Had been unaware the WEb development project was no longer needed for Tuya integration to work. I am sloppy at reading stuff, untill I run into problems ;) So went ahead and removed my cloud project in iot.tuya.com. Then restarted HA and Tuya integration worked without prompting. (no longer prompting to re-authenticate) So for me this seems like a permanent fix, not a workaround.

Thanks !!

[GraemeDBlue]

Tuya integration worked without prompting. (no longer prompting to re-authenticate) So for me this seems like a permanent fix, not a workaround.

did it ask for a QR code

[Just4vinnie]

Tuya integration worked without prompting. (no longer prompting to re-authenticate) So for me this seems like a permanent fix, not a workaround.

did it ask for a QR code

No, service just came up after restart. Before I removed the project I used the QR code, seemed to accept it succesfully at all times, but to then fail a few seconds later.

[GraemeDBlue]

No, service just came up after restart. Before I removed the project I used the QR code, seemed to accept it succesfully at all times, but to then fail a few seconds later.

yeah so mine has been working ok since Friday despite complaining baout needing a re-auth, but i cant make any changes or move existing devices to Tuya Local becuase of the auth issue. So my devices are still controllable

[StevusPrimus]

You should log in to iot.tuya.com and confirm the new privacy options. At least that did the Trick for me.

Good catch. I am using the smartlife app, though. There doesn't seem to exist a corresponding website, and I have no tuya account, just a smartlife account. This has been working flawlessly so far.

Currently, HA is accepting my re-authentication again, so maybe it was a hickup on their cloud side.

Incidents like this (and the dramatic impact it has on home automation availability) make me re-eval my tuya investment. Since I have quite a number of tuya devices meanwhile, it's probably time to look into reflashing firmware for mission-critical devices.

Smart Life, Tuya, ... Apps all use the same backend and thats iot.tuya.com. I am also using the smart life app btw. There are all just rebranded interfaces to Tuya IOT. The account to iot.tuya.com is a Developer account. It is not the same as the consumer account for the app. I am referring to this here --> https://developer.tuya.com/en/docs/iot/Home-assistant-tuya-intergration?id=Kb0eqjig0utdd#title-2-Prerequisites At my home all things have a physical workaround, as smart home automation can always fail for many reasons. But yes, for me it is the investment into Zigbee devices that I regret sometimes. :)

[peteS-UK]

I don't understand all the aggressive comments on this thread. Yes, it's a serious problem of course, but a) it's a cloud service and given that this happened outside of any HA update or change, it seems very likely the problem is with the cloud service, over which HA have no control, b) we all surely know that anything dependent on a cloud service can go down so is by definition unreliable, and c) there are working local-only solutions which overcome this problem. If you can't live with unreliable cloud services - and the reality is Tuya could block HA tomorrow and there would be nothing we could do about it - then doesn't it make sense to adopt one of the already available local only solutions?

[GraemeDBlue]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

[TurboKanne]

back to the topic ... did I understand correclty: deleting the iot.tuya.com web project will fix this problem?

[clanic70]

Hi all, it looks that this issue has been resolved (from my side) reloading Tuya hub 2-3 times until Hub error was definitely cleared. Then to cancel Tuya integration box appeared on top of HA integration list, I've rebooted HA and everything was back to normal. Thus no needed to delete any Tuya project or using again QR code. Best regards

[peteS-UK]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

[peteS-UK]

back to the topic ... did I understand correclty: deleting the iot.tuya.com web project will fix this problem?

For me, accepting the new t&C's did it, for others, deleting the account did it. So, perhaps there's a common thread that if you have the account you have to accept the new t&C's but if you don't have the account, it works anyway.

[StevusPrimus]

back to the topic ... did I understand correclty: deleting the iot.tuya.com web project will fix this problem?

Well, it fixed the issue @Just4vinnie ;) For me login into iot.tuya.com, accepting the terms, then restarting HA fixed it. Looking at the history of thread, all of this could also be just luck. Working like 20 years in IT experience, tells me not to generalise over only single cases. Maybe it is also a complete else issue, which solves after restarting often enough. like @clanic70 .

Out of my view we can agree that https://developer.tuya.com/en/docs/iot/Home-assistant-tuya-intergration?id=Kb0eqjig0utdd#title-2-Prerequisites describes the creation of such a cloud developer project, but https://www.home-assistant.io/integrations/tuya is not talking about it anymore and I am quite sure I read a while ago, that we do not need the cloud dev project anymore ...

[clanic70]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

Hi, in my case Tuya Local is not reliable because all devices go offline 2-3 times per day even with static IP configuration 😞 I've created a routine which restart Tuya Local service automatically but in most of cases I need to reboot HA....really a mess!

[MondMann2019]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

Hi, in my case Tuya Local is not reliable because all devices go offline 2-3 times per day even with static IP configuration 😞 I've created a routine which restart Tuya Local service automatically but in most of cases I need to reboot HA....really a mess!

This sounds like a network problem to me. Did you split 2,4 an 5 Ghz? Just doing this often solves the problems.

Another issue might be a bad router. I have over 50 tuya devices and only 1 or 2 loose connection once in three months (which only a restart of the device solves).

[clanic70]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

Hi, in my case Tuya Local is not reliable because all devices go offline 2-3 times per day even with static IP configuration 😞 I've created a routine which restart Tuya Local service automatically but in most of cases I need to reboot HA....really a mess!

This sounds like a network problem to me. Did you split 2,4 an 5 Ghz? Just doing this often solves the problems.

Another issue might be a bad router. I have over 50 tuya devices and only 1 or 2 loose connection once in three months (which only a restart of the device solves).

Hi, thanks for your advice. I have both 2.4 and 5 Ghz with the same SSID, so I'll try to split to see any improvement 👍 For the rest I have a FritzBox 7590 router with which are connected 80 devices usually without any connection issues 😊

[MondMann2019]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

Hi, in my case Tuya Local is not reliable because all devices go offline 2-3 times per day even with static IP configuration 😞 I've created a routine which restart Tuya Local service automatically but in most of cases I need to reboot HA....really a mess!

This sounds like a network problem to me. Did you split 2,4 an 5 Ghz? Just doing this often solves the problems.

Another issue might be a bad router. I have over 50 tuya devices and only 1 or 2 loose connection once in three months (which only a restart of the device solves).

Hi, thanks for your advice. I have both 2.4 and 5 Ghz with the same SSID, so I'll try to split to see any improvement 👍 For the rest I have a FritzBox 7590 router with which are connected 80 devices usually without any connection issues 😊

Advice: Keep the name SSID of the 2,4ghz the same as is was before and only give the 5ghz network a new name. This way you don't have to reconnect all devices. ;) Smartphones and other devices can be connected manually to the "new" 5 ghz network.

The router should be no issue. I've got the same ;-P

[clanic70]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

Hi, in my case Tuya Local is not reliable because all devices go offline 2-3 times per day even with static IP configuration 😞 I've created a routine which restart Tuya Local service automatically but in most of cases I need to reboot HA....really a mess!

This sounds like a network problem to me. Did you split 2,4 an 5 Ghz? Just doing this often solves the problems.

Another issue might be a bad router. I have over 50 tuya devices and only 1 or 2 loose connection once in three months (which only a restart of the device solves).

Hi, thanks for your advice. I have both 2.4 and 5 Ghz with the same SSID, so I'll try to split to see any improvement 👍 For the rest I have a FritzBox 7590 router with which are connected 80 devices usually without any connection issues 😊

Advice: Keep the name SSID of the 2,4ghz the same as is was before and only give the 5ghz network a new name. This way you don't have to reconnect all devices. ;) Smartphones and other devices can be connected manually to the "new" 5 ghz network.

The router should be no issue. I've got the same ;-P

Sounds good! Thanks 😊

[TurboKanne]

Ok, I just deleted the web project within iot.tuya.com and after a HA restart the error did not occur, I then could reload the integration and the configuration button showed up. I used the QR code with the smart life app for authorization and after a couple of seconds the Tuya Integration got back to work ... so far so good ...

... but interestingly, there are "only" 85 devices showing up, instead of my originallly 106 devices :-( some temperature and humidity sensors are missing and as far as I can see some sort of switches are missing.

better than nothing :-) i made another restart of HA then now it has 108 devices ?? but again with an authentication issue. clicking on reload makes Tuya work again, but then it has 85 devices. Weird.

And in the Repair-Section of Home Assistant still shows the issue with Tuya authoriiztation.

edit (after a few minutes) i looked into the inetragtion and could see that there are again 108 devices, but it switches back and forth, sometimes 85 and sometimes 108 ... even more weird.

[peteS-UK]

then doesn't it make sense to adopt one of the already available local only solutions?

Not everyone has purchased devices in the last few months, I have many legacy devices from when I first used Alexa to control things that are stuck on Tuya that offer no Tuya local migration as they are not supported devices. I'm not going to spend a forture to purchase all new zigbee devices and throw a whole bunch of working devices in the trash

No, I don't intend to throw things away. Almost all of my Tuya devices are years old and I initially moved to Tuya Local because it supported a device that the core Tuya integration didn't and allowed me a degree of future proofing as you can define your own device configs for anything not supported.

Hi, in my case Tuya Local is not reliable because all devices go offline 2-3 times per day even with static IP configuration 😞 I've created a routine which restart Tuya Local service automatically but in most of cases I need to reboot HA....really a mess!

This sounds like a network problem to me. Did you split 2,4 an 5 Ghz? Just doing this often solves the problems. Another issue might be a bad router. I have over 50 tuya devices and only 1 or 2 loose connection once in three months (which only a restart of the device solves).

Hi, thanks for your advice. I have both 2.4 and 5 Ghz with the same SSID, so I'll try to split to see any improvement 👍 For the rest I have a FritzBox 7590 router with which are connected 80 devices usually without any connection issues 😊

Yes, I found lots of IoT devices just don't like a shared SSID - trying to get my cameras working a while back was just a non-starter until I renamed my 5Ghz. I find Tuya Local to be a lot more stable than the core Tuya integration - I found with core Tuya that devices kept disappearing and re-appearing and I don't get that with Tuya Local. YMMV of course.

[TobiasPSP]

I don't understand all the aggressive comments on this thread.<

It is rather deep frustration. If it appears aggressive, then I am sure that was not the intention.

For severely limiting bugs like the auth problem, especially when recurring over many months now, I would expect some progress or call for action. There is none, it appears to worsen.

The tuya integration is awesome when it works, but in its current state with frequent lockouts, frankly it‘s not fit for real home automation.

At current state, regular users can do little and help little. There is no way to diagnose auth or identify who might own the code that causes this.

As last measure, many users resort to wild (hopeful) speculation, me included. That’s not productive. Possibly the tuya cloud service just had a hickup over the weekend, and regardless of whether you accepted new tuya terms, replaced accounts, redid the integration, downgraded HA, or whatnot, everything might have been fine by Monday morning anyway. It can‘t be rocket science to add a „test authentication“ button with verbose error messages to end this helpless situation.

Home automation is business-critical for many users these days and not just a hobby. So it‘s hard to just breathe away frequent total lockouts at random intervals, or being forced to trial and error.

There is no gold standard solution either. Local tuya has its own set of issues and limitations, and not all devices are reflashable. So there is no perfect solution, which is why HA and its wide range of integrations is so awesome.

So when there is a severly impacting recurring issue with any integration, I kindly ask for respect and taking the issue seriously (rather than suggesting to just stop complaining or to avoid the problem by avoiding the integration).

If really noone has the faintest clue what might be amiss here, then maybe some authentication diagnostics with verbose logging could shed light into this. I am sure most users are absolutely willing to invest time and effort to help improve the integration. Just enable them. :-)

[frytaman]

in my case after 5 days I just tried to find new ToS mentioned earlier and logged to IoT. During regular digging in I found that my subscription is suspended. Just like on screen unfortunately I have the screen after I filled up some form to extend free subscription for 6 months. It was automatically accepted and all back "In Serivice". Tuya started working again without any restaring etc. Please check your subscribed resources it should resolve the problem.

[apf-doit]

re-enabling the tuya subscription is not the issue here. i have mine re-enabled 2 times now over time and it is still valid, but auth problems in HA pop up every kind of hour now.

[Sir-Udo]

Hi all, i has a soluten vor the problem here. (at me it's works, i hope vor you too) At the Tuya IOT Platform, i lock at my Projekt and i have more then one DataCenter in it. A Long Time ago, i start my account i have the choise to use more then one datacenter and i try both western europ and central europ. Today there is a massege that only one datacenter is allowed, after i kill the second one, and restart my Home Asssistant, The Tuya authentication runs. Till Yet ! ;-) The IOT Datacenter:

The Tuya in HA:

The Reasen is, delete the wrong datacenter and only use the one you realy need. THX Udo

[cmgestevao]

Hi all, i has a soluten vor the problem here. (at me it's works, i hope vor you too) At the Tuya IOT Platform, i lock at my Projekt and i have more then one DataCenter in it. A Long Time ago, i start my account i have the choise to use more then one datacenter and i try both western europ and central europ. Today there is a massege that only one datacenter is allowed, after i kill the second one, and restart my Home Asssistant, The Tuya authentication runs. Till Yet ! ;-) The IOT Datacenter: The Tuya in HA:

The Reasen is, delete the wrong datacenter and only use the one you realy need. THX Udo

I have only one datacenter selected since the beginning (2 years ago) and I also have this problem...

[caitotheonlypotato]

Did the reauthorize again just now (something I've done a hundred times over the last few days), scanned the QR with the Tuya App and it went through first time and it worked and stayed. Hopefully a good sign, I'll post back if it drops again.

[applegeeks]

Did the reauthorize again just now (something I've done a hundred times over the last few days), scanned the QR with the Tuya App and it went through first time and it worked and stayed. Hopefully a good sign, I'll post back if it drops again.

if you restart your HA, did it re-prompt again? or did it work and stick?

[applegeeks]

decide to restart my HA and it no longer prompts for authentication.

[gaosq856]

decide to restart my HA and it no longer prompts for authentication.

hi, the issue has been resolved, please try again. Thank you.

[applegeeks]

decide to restart my HA and it no longer prompts for authentication.

hi, the issue has been resolved, please try again. Thank you.

What was the issue and the fix?

[caitotheonlypotato]

Did the reauthorize again just now (something I've done a hundred times over the last few days), scanned the QR with the Tuya App and it went through first time and it worked and stayed. Hopefully a good sign, I'll post back if it drops again.

if you restart your HA, did it re-prompt again? or did it work and stick?

I'm imaging the server tonight so I'll let you know tomorrow :)

[frenck]

We've been informed by the Tuya team that they have fixed the issue on their end, causing the occasional signature errors.

Closing this issue on our end.

../Frenck

[GraemeDBlue]

@frenck still not working for me, reloaded integration , click configure and scan QR code and still auth fails

[GraemeDBlue]

@frenck still not working for me, reloaded integration , click configure and scan QR code and still auth fails

ok a reboot seems to have solved that

[EboBH83]

@frenck still not working for me, reloaded integration , click configure and scan QR code and still auth fails

ok a reboot seems to have solved that

Tried reloading, still works well for me too

[caitotheonlypotato]

I can confirm for me that Tuya is now operational again