-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
Roborock - Unable to set up integration - 'code': 'auth.err', 'msg': 'auth.err.invalid.token', 'status': 'UNAUTHORIZED' #102487
Comments
Hey there @humbertogontijo, @Lash-L, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) roborock documentation |
I have the same issue after setup the integration. Notification in the app that someone logged in but the mentioned error in home assistant. Update: So, I am not sure if it is the same root cause but the solution from the other issue worked for this issue. |
Hi there, To ensure no conflict to other integrations (like mentioned in other issues) I set up a new home assistant instance using docker.
In my case my Raspberry Pi was out of sync with the current local time. I hope this is a permanent fix. |
Same issue here, however the error I receive when putting in my verification code is "Unknown error". |
I had the same issue presentation (running HA as an app in TrueNAS Scale) and eventually figured out that the issue was that my system time was out of sync. It took me a while to figure that out because:
|
Yea I think it has something to do with timezone settings. I was running it as a trueNAS Scale app also, but was having all sorts of other issues with some other integrations. Ended up getting a rasp pi with HAOS and now it works perfectly. So for others I would say check your timezone settings. Or bite the bullet and run the OS as its own thing. |
Not a time issue. Current tz is America/Los Angeles and all logs show correct time to the second. Running HA OS on mini PC. I was able to successfully reconnect the integration today though. Unsure if it was an HA update or something on Roborocks side. |
I am running HAOS on an x86 (bare metal) so I doubt it is just a timezone issue. |
The problem
I am setting up the robo rock integration for the first time. I have a Q Revo, which is setup in the robo rock app. I go to set up the integration, type in my email, and then type in the one time code I receive. I get a notification on my phone about a new login on my roborock account, but the integration on HA just says 'Failed to setup' with the following error log:
Let me know what else I can provide to help!
Logger: homeassistant.config_entries
Source: config_entries.py:399
First occurred: 9:39:37 AM (3 occurrences)
Last logged: 9:40:59 AM
Error setting up entry [email protected] for roborock
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 399, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/roborock/init.py", line 32, in async_setup_entry
home_data = await api_client.get_home_data(user_data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 708, in get_home_data
raise RoborockException(home_response)
roborock.exceptions.RoborockException: {'code': 'auth.err', 'msg': 'auth.err.invalid.token', 'status': 'UNAUTHORIZED', 'timestamp': '2023-10-21T18:55:46.087+00:00'}
What version of Home Assistant Core has the issue?
core-2023.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Roborock
Link to integration documentation on our website
https://www.home-assistant.io/integrations/roborock/
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
The text was updated successfully, but these errors were encountered: