narrow slate
Basically picking back up on the topic here:
https://github.com/home-assistant/core/issues/130460
Not sure why that discussion was closed, the issue remains.
Basically at this point the integration is unusable. Has anyone found a way to solve this?
nova hazel
There is a brand new backing package and implementation starting with HA 2025.12.0 beta. I suggest trying the HA beta and reporting any new issues.
narrow slate
By backing package and implementation, are we talking about background stuff in HA itself and also a newer version of the integration that makes use of that?
nova hazel
Yes
narrow slate
huh
I'm very curious, and by no means do I expect you to go into deep detail, but why does the integration care about base HA when it comes to contacting a device on the LAN, especially if that device already supposedly has local API?
just trying to understand what's going on before I jump onto a beta version of HA
nova hazel
The integration is part of HA
narrow slate
I have been kinda thinking about integrations as add-ons of sorts, especially these ones that are maintained by third party groups
nova hazel
It's how HA interacts with the device. It's how HA interacts with all devices
Integrations and addons are completely different
narrow slate
ah so the "backbone" of how integrations are "wielded" by HA is undergoing changes in the beta
mighty shoreBOT
nova hazel
That's too grandiose a statement
The Roborock integration has changed in this beta release
narrow slate
Integrations and addons are completely different
I know, I meant in terms of the integrations (not) being a part of "base HA", the terminology is a bit confusing for someone who is not super acquainted with the exact internal structure of HA, but I understand an integration exists to connect HA to a "system of devices" like Philips Hue lamps etc
aaaah ok I get it now
nova hazel
Core integrations are part of the HA release
narrow slate
I was not aware that the integrations were maintained so close to base HA
I honestly thought they worked more like packages in Linux, where the kernel is it's own thing and while the software depends on kernel to work, updating one is kinda separat from updating the other
but your explanation helped
well then I guess I'm gonna go clone the SD card just in case then hop on Beta
thanks for the pointer
nova hazel
The devs for this integration are very active, so please report issues in GitHub
narrow slate
joined beta channel and updated everything before doing a full reboot
still doing it, guess I'll head over to the github
nova hazel
You should review the logs to see what's wrong first
narrow slate
I recognize many words in this, but having no knowledge of how this integration works I don't even know how to interpret it
there's error's related to network connection, "Network info failed", but I have no idea what that's related to or caused by 🤷♂️
and unexpected message ID "5" pops up several times
nova hazel
Looks like the one I already filed: https://github.com/home-assistant/core/issues/157494
narrow slate
your description of the issue is very different from what I'm experiencing though
my integration fails to even initialize
narrow slate
in previous issues/reports from other users this was tied to Roborock throttling API calls by blacklisting devices
I might do that tomorrow
nova hazel
it's not blacklisting devices, it's rate limiting access to the cloud API
And if you get your account rate limited, then it will ignore you for a "a while". And then it will allow you back in after a while
narrow slate
yeah, I had that issue a month ago and disabled the integration for a week and I had access again
nova hazel
And with the old integration, it would often fail to connect to the local API and fell back to using the cloud API, which would promptly lock you out through rate limiting
narrow slate
but then it blocked me again and I waited another week with it disabled and it hasn't reset