-
-
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 authentication fails after moving HA docker. #101289
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 |
Do you have the govee hacs integration by chance? |
Yes I do! |
They have an issue with one of their requirements that conflicts with roborock and causes problems Go into a file editor or ssh into your machine and edit custom components/govee/ manifest Change dacite==1.6.0 to dacite==1.8.0. Restart home assistant Reinstall Roborock See this thread: #100846 |
Thanks. I updated the manifest, rebooted, but still seeing this error when I try to connect:
|
You can try this Disable Govee Restart Readd Roborock Altenatively, you can do a pip install dacite==1.8.0 . Read through the thread and you should see a lot of different ways to do it |
Reviewing other thread, will try some of those things, like disabling Govee. |
OK so disabling Govee before adding Roborock after updating the manifest worked. I then re-enabled and Govee is working now too. Thanks @Lash-L . |
I have the same problem but I don't have Govee installed, I do have Homewhiz that is also using dacite but in that manifest it does'nt lock to a specific version.
|
You more than likely have something else using it then @jorblad You can always test by following the steps above for disabling it and reinstalling roborock To see if something else is using it, do a pip show dacite in your ssh/ docker env |
Requires: |
You can manually install the right version by doingg pip install dacite==1.8.0 What version does it say it currently has? And what about your custom components? |
1.8.0...
|
You are not having the same problem then, please share your error. |
I described in humbertogontijo/homeassistant-roborock#500 because that is the integration I have and have problem with but since it seemed very like this problem I wrote here as well. |
FYI, in case anyone has same issue. The resolution of my issue above, where I disable Govee, restart, and then it unblocks Roborock from connecting, and then I can re-enable Govee -- that needs to, for now, be done every time you restart HA or you'll have the same issue. Maybe there will be an update to the Govee or Roborock integration in the future that makes that unnecessary, but for now, keep that in mind if you see an error with Roborock on reboot that has anything to do with dacite. |
So I tried what was done in this thread but I get no device found in Roborock account edit edit2 Updated to HA 2023.10.1 and roborock still working, I still have the govee disabled but Ill give it a try tomorrow when I have a little more time on my hands to test |
For those of you using hassos, here's what I did to fix the problem:
Hope this helps! ✌️ |
Didn't help for me. :-( |
Work for me !!!! tanks |
Most painful issue I have had so far! finally a fix for this. For those who are not skilled in this area like me....
Please like this post to help others find it! |
Disabled govee, updated via pip3 to 1.8.1 and still the issue persists. |
This worked briefly for me when Dacite was 1.8.0 but now it is up to 1.8.1 it isnt working again. Neither email code or using the password will list the devices. The Govee Hacs plugin is working fine and it is more important to me to control my lights then see what the vacuum is doing in HA but i would like to get both working together. |
+1 this fix is not working at all for me |
Well I have the supervised version of HA and it also did not work for me out of the box. Also had the other cloud based Govee integration. I have switched to the LAN version of govee. After that went into Advanced terminal/ssh and renamed the site-package name of dacite to daciteold. Then installed the dacite 1.8.0 and reboot. After that I could install the integration at least and it sees the robot. Now just have to test if it will work :) |
The problem
I recently built a new server and moved my docker with HA and copied all the config files. Everything is working fine except my Roborock S7 using the Roborock official integration. I've tried re-authenticating and enter the code I receive but I receive an 'unknown error'. I've also tried repairing my Roborock to WiFi.
In the log, this is what I see:
wrong value type for field "rriot" - should be "roborock.containers.RRiot | None" instead of value "{'u': 'yBRMVHKdiWGBk6Ird3AdL', 's': 'cUfbzL', 'h': 'hQ4dakgDyM', 'k': 'jKwAJTQo', 'r': {'r': 'US', 'a': 'https://api-us.roborock.com', 'm': 'ssl://mqtt-us.roborock.com:8883', 'l': 'https://wood-us.roborock.com'}}" of type "dict"
Looking for advice on what to try next. I think the only thing I can do is wipe my Roborock account but I'd prefer not to lose my maps, so wondering if there is something else to try.
Thanks!
What version of Home Assistant Core has the issue?
core-2023.9.3
What was the last working version of Home Assistant Core?
core-2023.9.3
What type of installation are you running?
Home Assistant Container
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: