core
core copied to clipboard
New Tuya integration not showing QR code
The problem
What version of Home Assistant Core has the issue?
2024.2.0
What was the last working version of Home Assistant Core?
2024.1.0
What type of installation are you running?
Home Assistant Container
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
same thing happening with me. :(
I don't really know, but I speculate that Tuya is being overwhelmed. Would suggest others try later in the event this is the case.
At me don't work:
Same thing here... Invalid hex color
I'll add that when I click the reauthenticate to get this popup there is a network call made that seems to look legit.
Same error but i just closed the error window and reconfigured again.. QR code became visible and authentication in smart life app successfull
Same problem here, for new integrations too.
I ran into this same issue. As a workaround, I copied the "data" string from the API request that is sent when the popup opens, used it to generate a QR code in an external app and scanned it with the Tuya app. After that, all I had to do was clicking on "submit" on the popup of on the homeassistant app and the integration was working!
Changing theme to default worked for me ! To change theme, click on your user name on the bottom left and then change theme to "Use default theme"
Changing theme to default worked for me ! To change theme, click on your user name on the bottom left and then change theme to "Use default theme"
This did the trick for me too! I had to choose the "Home Assistant" theme, as for me the default theme was a custom theme set by an automation
I had to select the Home Assistant Theme and then it would've worked however it had been too long so I also needed to restart home assistant and re-enter my User Code
Yes, changing the theme to the default one helped generate the QR-code. Thank you!!!
I get the "Login error (0)" message (same as @Liionboy), not the "Invalid hex color" message. I use the default theme. I tried restarting HA, and was asked again for my user code, but then get the same error.
I get the "Login error (0)" message (same as @Liionboy), not the "Invalid hex color" message. I use the default theme. I tried restarting HA, and was asked again for my user code, but then get the same error.
I managed to get this working. I wondered if the app was interfering with my local devices (although not sure how this would be a problem here), so I turned off the wifi on my phone, retried the reconfigure, and the QR code appeared. The app said the QR code had expired, but I tried a couple more times and it worked. This work-around doesn't make sense to me, and I'm wondering if it was simply the Tuya servers being overloaded, and I simply needed to try a few more times.
I'm not getting a QR code, but no error message either:
Clear browser cache and try again. the problem will be solved
Clear browser cache and try again. the problem will be solved
Thank you so much this worked! I used an incognito broswer window.
Tried again a while later and it worked. AFAIK, I didn't do anything different (like clearing my cache), so maybe it was something on the Tuya end, or maybe just waiting a while.
Yes, changing to the default Home Assistant Theme also worked for me.
For me changing the theme color from "Auto" (which would choose the Dark theme in my browser) to "Light" shows the QR code. Leaving this out there for those who don't have any other themes installed (like me) and are already using the Home Assistant Default theme.
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 closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign tuyaRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove 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)
This is a frontend issue, which is here:
duplicate of https://github.com/home-assistant/frontend/issues/19722
Also, #80278 (which is pinned in our issue tracker), is a catch all.
The workaround is, to temporarily switch to the default theme to re-authenticate.
../Frenck
I have tried changing the theme, clearing the cache, using a private window, giving it permission for pop-ups, etc.... and I can't do it. I see a 500 error in the development window.
That is not the same issue as reported in this issue. You have a different error message than the person reported in the opening topic / issue description.
I guess it's a frontend cache problem, a simple F5 did the trick for me
same here
@jarucho This isssue has been closed and marked duplicate. I'm not fully understanding what your last comment would add. The solution was given.
Same for you @j-lorenzo...
Read before you post... see: https://github.com/home-assistant/core/issues/109898#issuecomment-1933540834
@jarucho This isssue has been closed and marked duplicate. I'm not fully understanding what your last comment would add. The solution was given.
Same for you @j-lorenzo...
Read before you post... see: #109898 (comment)
I cannot switch switch to default theme so... no solution for me
I cannot switch switch to default theme so... no solution for me
Then there is no solution at this point. Any customization outside of HA is generally unsupported. We do our best to make things work but can't guarantee it with custom modifications.
Please follow the above linked issues for progress.
In my case, I temporally stopped https then barcode was shown.