Problems after updating to HA 2023.10 #500
Comments
|
There's an Roborock update which works now. |
What update? A update of the Custom integration or the device or what? Please be more specific. Thanks! |
i have the same issue. i have deleted the whole integration and reinstalled anything but still can't setup my S7. After i typed in my authentication code, the prompted says "no device found in your Account". |
|
yep same problem: no device found. |
|
I can confirm similar issue with S7 using HAOS. The .10 update broke many things.. even the energy dashboard/file editor of the core integrations are not workin properly anymore and some other integrations as well. I hope they will hotfix that, as i just downgraded to .9.2 to make it work again. Many issues opened about this update :D. I have never experienced a similarly difficult update in the half year I have been using HA now. |
Same here! I’ve used HA for over 8 months and…this is the worst! (Insert The office meme) |
|
I had an issue after HA 2023.10 update, but with Roborock Integration version 1.0.11. The update 1.0.12 solved the problem on my system. |
Agreed. Update to 2023.10, then restart HA (again). That'll pickup the Roborock update in HACS. Install that. Restart HA (again). Back up and running. Thanks! |
|
Same for me. Broken. |
|
I have found a temporary workaround: Downgrade HA back to 2023.9.3 via Terminal, reinstall the Roborock Integration version 1.0.11 and everything is fine again. And then we should wait for a hotfix of HA 2023.10 and the Roborock Integration. |
|
I fixed the problem. I rebooted Home Assistant, entered HACS, after the custom component update appeared. Updated, rebooted and it worked |
That didn’t fixed my problem. That’s why I downgraded anything to a prior version. |
|
Guys just make your life easier a for now: downgrade to 2023.9.3 and live your life 😂 I was going mad! |
That’s exactly what I said two posts ago 😂 |
|
You rock man! Thanks 🙏 |
|
update HACS |
I've tried this, but am still hitting an error when trying to validate my account.
|
|
same problem with 2023.10.1 |
|
2023.10 2023.10.1 Logger: homeassistant.config_entries Error setting up entry Roborock for roborock |
|
I have exactly the same problem as @superpower10 2023.10.0 => works with the last HACS integration version 2023.10.1 => it's not working |
|
For me it started working again, I think it was after updating HA to 2023.10.1 |
|
@jorblad As I wrote before updating this Integration in HACS after updating 2023.10 it worked again. But after updating to 2023.10.1 it doesn’t work anymore and I‘m not alone with that. |
|
That is the weird thing, I did a lot of things to try before but now I just updated the integration when I still was running 2023.10.0 and sometime after updating to 2023.10.1 I saw that my automation was working and then I looked at the status and saw that it was working fully again. |
Have you tried to reboot the whole hardware of your HA host? For me this was the key. Restarting HA or roborock integration wasn't successful (even if it doesn't makes much sense). |
|
Im still having problems. Restarted, deleted the integration in hacs, restarted, restarted the hardware but still getting the same error in the newest HA
|
just checking; roborock and mi home are different accounts |
I did that (see post above). Didn’t help. It helped with 2023.10 but not with 2023.10.1 |
Its my Roborock account. I dont have a MiHome account anymore. It worked in the older versions of HA. |
Same Problem |
|
Try downloading the 'main' version of the component and restart and see if that fixes your problem |
Didn't fix it, unfortunately |
|
HI. Same problem. |
Didnt work for me either :( |
|
Any news? |
Nope. Even the dev is very still… |
I tried this solution and it works finally again :) |
|
i don't see the 1.0.12 update from hacs, i'm stuck a 1.0.11 |
For me, after updating the Core to 2023.10.1, there was the regular update notification in the settings. Before, i also was not able to pull the 1.0.12 update. Good luck |
|
You won't see the latest version, 1.0.12, until you are at least on 2023.10. So you have to upgrade home assistant which will break the integration. Then upgrade the integration. Confirmed working in 2023.10.1 here. |
|
I have 2023.10.1 installed and the clicking on the integration it says that I have 1.0.12. Even after restarting it doesn’t work |
|
Updated to 2023.10.2 still the same |
|
Reading the error message this has nothing to do with rebooting. To my opinion it‘s a type error which is a programming problem. So the developer has to do something: dacite.exceptions.WrongTypeError: wrong value type for field "rriot" - should be "roborock.containers.RRiot | None" instead of value |
It is not an error on our side. Basically - the version of a library we need is being hard pinned by something else on your system - so you have to manually fix it. |
I'd propose to backup your system, delete the integration, upgrade to the newest HA core version and to reconfigure the newest version of the integration again (try several things out first) instead of spamming this issue thread, especially if there are many confirmations already for its working functionality.. And dont forget that the devs are doing this volunteerly.. they dont "have to" do things. |
|
I am not spamming and by „have to“ I meant that the user is not able to fix this. And if it‘s only my problem why do others still have the same problem? |
|
I still have the same problem, made a backup, removed the updated Home Assistant 2023.10.2 integration, re-integrated it, it doesn't work. |
|
I did another test, removed integration from HACS restarted, tried Home Assistant integration doesn't work. |
|
With Home Assistant 2023.10.3 solved for me |
|
For now, reload your HA 9.3 backup, download or redownload Roborock from HACS making SURE to downgrade to Roborock version to 1.0.11. Restart HA. Add Roborock integration. Enter credentials. All good. |
|
Here's how to fix Roborock dependencies if you're using hassos: |
|
Try the latest main if you are having issues and let me know how that works for you |
|
Upgrading to the latest main made the map work for me. |
|
Same here, switching to main just now made everything work once again. Thank you! |
|
I am finding it hard to follow what the problem is here and how to fix it. I am on the November branch of HA and the Dacite version is 1.8.1. I am running the main branch (have tested the default branch as well) Ive removed the strings in the log that might open me up for a security breach. |
and others
Version of the custom_component
1.0.12
What vacuum are you using?
Roborock s6 maxv
Describe the bug
After updating to HA 2023.10 I lost contact to my Roborock in homeassistant. I updated to from 1.0.11 to 1.0.12 to fix that but it didn't change anything other than possibly what logs there are. I also tried to install the main version without success and deleting and re adding the Roborock account in integrations. I also tried reinstalling the integration completely. But after that it instead complains that no devices could be found on my account.
Debug log
Before complete reinstallation
After complete reinstallation
The text was updated successfully, but these errors were encountered: