Roborock failed Setup #102952
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 just tried setting it up again this AM, everything is up to date: 'types.UnionType' object has no attribute 'origin' During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
I have the same problem. Roborock stopped working and i tried reinstall but error in integration. |
|
This is an issue I have relatively little control over unfortunately. A few other issues have been made that talk about it Basically the following things are of note: If you have the govee hacs integration, switch to the core integration. You may need to manually update the dacite install version by executing pip install dacite==1.8.1 inside the home assistant docker container Lots of info in both of those threads |
|
Just updated Home Assistant, removed Govee HACS, dacite had already been update to 1.8.1, it accepts the code emailed to me, but, "failed to setup device". |
|
@crpeck share your logs please |
|
Logger: homeassistant.config_entries Error setting up entry [email protected] for roborock During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
@crpeck You do not have a fully up to date version of dacite. Make sure you are inside the actual home assistant docker container instead of just the terminal when you are running pip show dacite |
|
My bad - Guess I had to pip installl dacite==1.8.1 again, I did that in the container & restart Home Assistant - it works!!!!! My bad again, updated manifest.json in giver to dacite>=1.8.0, restarted, installed Roborock, got the exact same error as above. I need giver more than Roborock right now, so... ha info: ha infoarch: amd64
|
|
I dont have docker, only HA in raspberry. My log: Logger: homeassistant.components.roborock.config_flow wrong value type for field "rriot" - should be "roborock.containers.RRiot | None" instead of value "{'u': '51sLrkA3ZVSuKySNh0zkmR', 's': 'vpfPpD', 'h': 'v5Lv5fW8Mt', 'k': 'Esl6iFn4', 'r': {'r': 'EU', 'a': 'https://api-eu.roborock.com', 'm': 'ssl://mqtt-eu-2.roborock.com:8883', 'l': 'https://wood-eu.roborock.com'}}" of type "dict" |
|
I had the same issues and fixed them with this: LaggAt/hacs-govee#132 EDIT: Not really fixed yet . I still have problems!! 🤦♂️ |
|
+1 having same issue, even with dacite 1.8.1 |
|
I have almost clean supervised installation of HA updated to latest release and I also reproduce this issue. |
|
+1 |
|
If you are having issues and you can confirm you have dacite==1.8.1 - please post your logs |
|
I just set |
After setting the Govee manifest.json to
and rebooting. When sshing into the box and triggering |
this helped get dacite 1.8.1 to stick but unfortunately did not solve the roborock integration unexpected error issue. |
You do not have the right version of dacite. Try running in terminal "ha core rebuild" that should reinstall all your dependencies. |
After Confirmed version 1.8.1 after and |
If I did not restart HA twice it failed to remove everything properly and the rebuild did not resolve the problem. :) |
Yes removing Govee works, but what about people who want to use both? Switching to Govee LAN helped me get both working together. |
|
Govee Lan is only compatible with a very small subset of devices, almost nothing. Not a workaround for most people. I did manage only once to have Roborock working while Govee installed and working at same time. But that was a fluke, out of me troubleshooting some unrelated dns resolver issues. So my connection was on and off in the meantime, and I ended up with both running, which was weird. From my ad-hoc experimentation. together with some wild guessing: So here it comes the really wild guess, excuse me if I'm talking bananas, but I hope at least I inspire someone in the right direction: Maybe the code on Dacite is instantiating some kind of protected class that can not be Really instantiated more than once. Hence whoever get to it first gets the free pass. And not the others. |
|
Sigh.... `Logger: homeassistant.config_entries Error setting up entry [email protected] for roborock |
|
@atle-dahlman unless you have more logs. Your vacuum isn't reachable from the cloud. As it currently stands (will change in 2023.12) - if you have a signle device offline, the integration will not start |
|
Anyone stitll having problems: Attempt updating your govee hacs to the latest version or switch to the govee lan integration (my understanding is it still works with most govee devices). This is the downside of custom integrations, If it were a core integration, I could have likely fixed the problem within hours, but since it is custom, I had no power or control |
|
Hi ! In my homeassistant container: |
Ok, thanks. Didn't know that all devices had to be online. |
|
Closing this issue as there is a confirmed solution and anyone still having problems is seemingly having a seperate problem. Quoting what I said above for anyone else who coms upon this thread Attempt updating your govee hacs to the latest version or switch to the govee lan integration (my understanding is it still works with most govee devices). Restart Home Assistant |
|
@home-assistant close |
The problem
Roborock stopped working after I rebooted the System due to a relocation of my Raspberry with HA installed on it. I tried reloading the System/Integration multiple times. I attached a snippet of the error in the Debug console.
What version of Home Assistant Core has the issue?
core-2023.10.5
What was the last working version of Home Assistant Core?
core-2023.10.5
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
2023-10-28 11:47:01.881 ERROR (MainThread) [homeassistant.config_entries] 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 29, in async_setup_entry
user_data = UserData.from_dict(entry.data[CONF_USER_DATA])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/containers.py", line 90, in from_dict
return from_dict(cls, decamelize_obj(data, ignore_keys), config=Config(cast=[Enum]))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/dacite/core.py", line 68, in from_dict
raise WrongTypeError(field_path=field.name, field_type=field.type, value=value)
dacite.exceptions.WrongTypeError: wrong value type for field "rriot" - should be "roborock.containers.RRiot | None" instead of value "{'u': '5GU7EP31faFf9AOqpl7Ii', 's': 'p1Nnir', 'h': 'awjjmNBrna', 'k': '8FKYpRIN', 'r': {'r': 'EU', 'a': 'https://api-eu.roborock.com', 'm': 'ssl://mqtt-eu-4.roborock.com:8883', 'l': 'https://wood-eu.roborock.com'}}" of type "dict"
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: