-
Notifications
You must be signed in to change notification settings - Fork 73
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
Integration is not working with HA 2023.10.1 #510
Comments
I have the same issue |
Same |
Nevermind, updated version works |
which updated version? |
Double nevermind, looks like it didn't. I'm on 1.0.12
|
I am using HA 2023.10.3 and the integration continues with same error :-(
|
+1 |
+1 |
Same |
same |
Same :( |
Mine seems to work randomly between reboots and generally tends to fix itself when I start the vacuum via the Roborock app on my phone. |
I updated HA and this integration today, HA kept rebooting and wouldn't load properly. I had to rename the Roborock folder to get it to load. |
I installed the latest update via HACS that was posted today. Fixed the problem for me. |
No change for me with latest main "release" |
Working perfectly again for me now. Thank you |
Does still not work for me. Same log messages as @MiguelCosta and error "No device found within your Roborock account" |
I switched to the main branch, reboot, not working. Never deleted the integration. I suspect that a sinple reinstall to force dependencies would had the same effect. Edit: didn't survived a restart :( |
Same here. |
Also same problem. |
I have the same issue! "No device found within your Roborock account"! I'm about to tear out my hair, at least what's left of it... |
Same Problem here :( |
Even with HA 2023.10.5, deleted and reinstalled integration and restart the whole serve the problem still exists. Is it a HA problem? Because I can’t even get my robot in through the official integration. |
Still working for me. I'm wondering if the roborock region has something to do with the problem others are still having. I'm in the US, again works fine. The recent logs posted were connecting to the EU roborock cloud. |
I’m a EU citizen…maybe the dev can tell us more about that. Like I said, even the HA own integration fails to initiate the robot. |
Updated to 1.0.12 and it started working for me. |
Okay…I’m using HA in Virtual Box on a Mac. So not directly docker 😅 |
it does not matter, even HA OS uses docker internally. So if you didn't use first that command should probably be the cause that dacite didn't show in your case |
You can also try the command |
For all getting the missing devices with dacite 1.8.1 - double check your password. The same error message appears if you type wrong password. |
Weird thing…I have shut down HA by Terminal, restarted the Server and tadaaaa…my robot works again?! I mean, I have tried to shut down HA completely from the standard menu and also restarted the server serval times but this time, it worked. That’s freaky 🤓 |
Neither password or email code is working for me. Dacite 1.8.1 |
Logs please. You are having a different issue |
2023-11-17 09:35:37.675 ERROR (MainThread) [custom_components.roborock.config_flow] wrong value type for field "rriot" - should be "roborock.containers.RRiot | None" instead of value "{'u': '', 's': '', 'h': '', 'k': '', 'r': {'r': 'EU', 'a': 'https://api-eu.roborock.com', 'm': 'ssl://mqtt-eu.roborock.com:8883', 'l': 'https://wood-eu.roborock.com'}}" of type "dict" I posted this log in another thread but here it is here as well. I have removed the values in json for identification purposes |
You still do not have the right version of dacite - that's what that error means. |
Now for some reason the dacite version is 1.8.0 Name: dacite But i have removed the roborock and installed xioami miio instead after pairing the roborock with xiomi home. Maybe that has changed the dacite version? I only need minimum functionality and the ability to read the status so can live without the map. |
Lol, I have waited a month for a fix and was watching this issue and this just fixed it. Goddamn govee integration. |
The just-released latest version of the |
Updated that, reinstalled the Roborock addon. Dacite version is 1.8.0...device not found.
Tested both password and code login |
Depending on what you need from the addon, you can try the xiaomi miio and pair your robot to the xiaomi home app. It has exactly the same GUI in the this app as the roborock app. Might be worth using temporarily until this is sorted out. |
Do the following and it should fix it:
|
@Lash-L - Thank you, I had the same issue as everyone else and the above steps solved it for me! |
Had the same issue and followed your steps. Everything is back to normal. Thanks! |
Working now with Govee lan and 0.13. Thanks. |
I don't have govee or dacite, but it failed as well. I tried: Thanks!
|
Try updating your home assistant |
FINALLY all is back to normal. thanks! |
This fixed my issue as well |
I upgraded the OS and core to latest version, updated the Roborock integration to 1.0.13, it didn't work at first, but i removed the device, then added it again, and now it works. Thanks for the fix! |
Actually it persisted until roborock custom integration upgrade, since manifest file changes only then :) Anyway, I had to do it again, because latest 1.0.13 comes with dacite==1.8.0 and it stopped working again even with this version on 2023.11.3, which works with 1.8.1 |
This works great for anyone having the issue. You can modify the files yourself until the pull goes through. Modify, restart, and the integration works. |
Not working :-( |
Version of the custom_component
1.0.12
What vacuum are you using?
Roborock S7
Describe the bug
The 1.0.12 integration version works with HA 2023.10.0, but after upgrade HA to 2023.10.1, the integration is not working anymore.
The master version is also not working.
Debug log
The text was updated successfully, but these errors were encountered: