The problem with integration Tuya

[Vladimir-huligan]

The problem

I have this problem almost every day. I have reached out to other users with the same problem. Please decide

What version of Home Assistant Core has the issue?

2024.9.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[mib1185]

Could you please provide an English translated version of the error? Further please also check and provide the home-assistant.log, thx 👍

[Vladimir-huligan]

[mib1185]

this shows an issue with xiaomi_miio integration, not with tuya ?

[Vladimir-huligan]

[mib1185]

yeah ... just copy&paste the text of this error had been more helpful, than this screenshot 😉

Nevertheless, what is your issue? I can't understand the screenshot from your initial post. From the log error message, I guess you've to re-authenticate your tuya account?

[home-assistant[bot]]

Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `tuya` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tuya` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tuya documentation tuya source _{^{(message by IssueLinks)}}

[Vladimir-huligan]

да ... просто скопируйте и вставьте текст этой ошибки, было бы полезнее, чем этот скриншот 😉

Тем не менее, в чем ваша проблема? Я не могу понять скриншот из вашего первоначального сообщения. Судя по сообщению об ошибке в журнале, я предполагаю, что вам необходимо повторно аутентифицировать свою учетную запись tuya?

you have understood the problem correctly. integration asks for authentication, but it happens almost every day

[garcru]

Same Thing happens to me. I use the QR and everything works fine, but after a while, less than an hour for me, or aftwr a reset of HA it tells me that the authentication failed. i dont know if it is related with this, but at the same time Tuya started with this problem Daikin ONECTA Integration also started with problema connecting to the cloud sip. Thank you in Advance

[Vladimir-huligan]

@tuya, @zlinoliver, @frenck don't you want to help?

[frenck]

@tuya, @zlinoliver, @frenck don't you want to help?

Sure I do! This is an open source project, feel free to help out an contribute a fix for this issue. That is absolutely greatly appreciated ❤️

[Vladimir-huligan]

@frenck I think this is how you can answer any question asked on this site. Thank you you've been very helpful

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Vladimir-huligan]

The home assist has been updated. The problem has not been solved

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.