-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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 setup fails due to dependency conflict with Govee HACS causing 'wrong value for rriot' #100846
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 |
Same issue with my instance with the update to core-2023.9.3. However, I was on core-2023.9.1 before. |
Very strange - that part of our code was not change in our version updates. Just grabbed what you gave me, and that seemingly works. My guess right now is that it is caused by another integration you use specifying a version of dacite that breaks our code |
Do you get an error anywhere in your logs that says something along the lines of: or |
@Lash-L FWIW I checked my logs and didn't see any pip error as you mention. I reverted my instance back to 2023.9.1 and can confirm my roborock integration is working again. I do have a few integrations with HACS that could maybe be culprit if you are not seeing any issues. |
I have no issues on my side - but I can confirm that older versions of dacite do break the code. Update back to 2023.9.3, check the logs for anything that says dependency or anything that says dacite As well, are any of your other integrations listed as having changes for 2023.9.3? |
I looked through the changelogs for both 2023.9.2 and 2023.9.3 for my case and it looks like the ones that would affect me are:
I'll update to 2023.9.2 to rule those changes out and report back. |
Are you able to ssh into your machine and the underlying container and run pip show dacite? How to get there depends on your HA install. Just google "how to run pip commands home assistant (install method here)" |
Just FYI that I am experiencing this as well since updating from 2023.8.4 to 2023.9.3. The integration is not connecting at all with the same error message. |
2023.9.2 doesn't have any issue so it is specific to 2023.9.3 changes. Here's the output of the pip show dacite from my instance: homeassistant:/config# pip show dacite |
metoo - roborock not working one 2023.9.3 |
Do you know if you use any of these requirements? And can you try doing pip install dacite==1.8.0 and let me know what it says? |
Same here, updated this morning to 2023.9.3 and it stopped working. Error setting up entry [email protected] for roborock |
@Lash-L I am using the brother, govee, and roborock integrations from that list. I reverted back to 2023.9.2 yesterday but I can test the dacite update later today and report back what I see. |
What Govee do you use? HACS or something else? |
metoo - roborock not working on 2023.9.3 |
It's HACS. It's also been a while since it was last updated. Here's the output I see when I update dacite: homeassistant:/config# pip install dacite==1.8.0 Looks like the dacite update fixed it for me. I now have the Roborock integration working with 2023.9.3 and verified I'm seeing entity updates. |
If it is not too much trouble - could you try disabling the govee hacs integration, then performing the update from 2023.9.2 to 2023.9.3 again for me? I would like to confirm that is the root of the issue |
Ok I just did the update with my Govee integration disabled and I can confirm it was the issue for me. I have a working Roborock integration without any dacite update. |
Do you also have the govee integration? |
I have the govee integration as well, and I have the same issue. |
Yes, I have the Govee HACS integration too |
Same Issue and I also have the HASCs Govee integration |
I also have the HASCs Govee integration, same error |
Yes i have that too |
@Lash-L I don't have the govee integration. |
You aren't having the same problem. If you look - your error is completely different. Check out the other issues - there are a few that talk about timeouts, you can post there |
I also have the HASCs Govee integration, same error |
IF you have the HACS Govee integration and you are experiencing this issue: Go into your file editor, and go to custom components then govee, then edit the manifest requirements to be dacite==1.8.0 instead of dacite==1.6.0 I have created a PR on their library to try to fix this, but I don't have access to their repository so I cannot make changes myself directly |
@derdustin1987 did you follow the steps I stated before? You need to update dacite to 1.8.0. You can do that manually by doing pip install or editing the manifest of govee hacs to be 1.8.0 instead of 1.6.0 |
@kalpik please run pip show dacite and give me the results. Then pip uninstall dacite and finally pip install dacite==1.80 Then restart and show me pip show dacite again |
Before uninstall: adf05938f794:/config# pip show dacite After uninstall and reinstall: adf05938f794:/config# pip show dacite |
Hmm... I modified my govee manifest to 1.8.0 restarted then tried to setup and got the same error as before. Running HassOs on a Intel NUC |
Okay, after uninstalling and installing dacite, I was able to set up the integration again at least, but it still says "Failed to set up" under devices. Logs: Logger: homeassistant.config_entries Error setting up entry k*****@gmail.com for roborock During handling of the above exception, another exception occurred: Traceback (most recent call last): |
@Mr-HaleYa please include your error trace when you are reporting an issue for the first time, just because an error may appear to be the same error, does not mean it is. I need to be able to confirm and have all of the information |
Logger: homeassistant.components.roborock.config_flow wrong value type for field "rriot" - should be "roborock.containers.RRiot | None" instead of value "{'u': 'GjWfNtDIUYOSIIHgoMc7D', 's': '4c3Fcu', 'h': 'rJdsrRCzpR', 'k': '2ukI7pjT', '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" |
@Mr-HaleYa Are you able to do a pip show dacite for me? |
@Mr-HaleYa are you also 100% sure you're running the commands inside the docker container, and not just the host OS? |
I never said I was using docker. It's Home Assistant OS on a NUC |
From: https://github.com/home-assistant/operating-system
|
@kalpik Okay i'm not 100% sure what is going on with your error. But try the following for me: Disable govee HACS pip uninstall python-roborock Restart See if it works? Your error is really strange to me |
@home-assistant rename Roborock setup fails due to dependency conflict with Govee HACS causing 'wrong value for rriot' |
Yep, this works now. Roborock shows entities. So probably something else is also conflicting with Govee HACS? |
@kalpik Not 100% sure - I think something was just going wrong with the installation of the package, by uninstalling roborock and letting HA install roborock and the version of dacite it wants, it hopefully fixed it. You can try re=enabling govee with the manifest having dacite==1.8.0 and see if it works for you |
Yep, already enabled Govee HACS, and it all works together properly now :) Thanks a lot for your help! |
I had to go through the same thing to get mine working again: Disable Govee, restart HA, re-install Roborock, re-enable Govee. I had previously tried Thanks for figuring this out! |
I'm going to go ahead and close this ticket because it all seems resolved |
@home-assistant close |
I know its closed, so please remove this if this is not okay But as a starter of the issue, my problem is not fixed. I tried disabling the govee hacs and restart, but after inserting the Roborock Verfication Code i still get my error.
docker / pip command is not avaible in the HA-Command Line. Is there anything i could do? I dont see an option to reinstall the native roborock integration or something like that. |
pip uninstall python-roborock from inside the HA container, and restart HA. |
If you can't figure out how to pip uninstall - a solution that should probably work is the following: Completely remove Roborock Disable Govee Restart Readd Roborock You should now have the right version of dacite. |
As is wrote, i didnt know how to pip uninstall, and just removing roborck was'nt working for me. (i'm new to homeassistant in general). But i now learned how to Thank you @ all :) |
This morning, I again had issues with the roborock integration because of Govee HACS, and I was really annoyed. Found this other govee LAN control HACS integration, and it seems to work really well. Thought of posting here in case it would help others: https://github.com/wez/govee-lan-hass |
The problem
After the Core Update today, Roborock Integration stopped working with the following Error Log. I tried deleting and re-login, but i get an "Unexpected Error".
What version of Home Assistant Core has the issue?
core-2023.9.3
What was the last working version of Home Assistant Core?
(the one before)
What type of installation are you running?
Home Assistant OS
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: