Yeah, unfortunately this is a known problem on some vacuums/firmwares. The reason is unclear, but it would be worth verifying if this also happens when the final query contains the requests for all queries that succeeded separately.
What I'm guessing is that queries with too large responses (or too large queries themselves) cause memory corruption, causing the device to jump into some sort of recovery mode.
There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
Please make sure to update to the latest python-kasa version and check if that solves the issue.
Thank you for your contributions.
Activity
rytilahti commented on Mar 6, 2025
Yeah, unfortunately this is a known problem on some vacuums/firmwares. The reason is unclear, but it would be worth verifying if this also happens when the final query contains the requests for all queries that succeeded separately.
What I'm guessing is that queries with too large responses (or too large queries themselves) cause memory corruption, causing the device to jump into some sort of recovery mode.
Scags104 commented on Mar 31, 2025
I have an RV30 Max Plus. Happy to do any testing needed. Maps returning would be great for Home Assistant integrations downstream.
github-actions commented on Jun 30, 2025
There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
Please make sure to update to the latest python-kasa version and check if that solves the issue.
Thank you for your contributions.
Scags104 commented on Jun 30, 2025
keep open
rytilahti commented on Jul 11, 2026
Unsure what exact call causes it to lose the map, but confirmed again in #1721.