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
Errors with 2024.5.0 beta concerning roborock.coordinator and maps #116300
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 |
Can you please upload your diagnostics as well? |
I added my diagnostics. |
Can you please do the following: Enable debug logging for Roborock Go to developer tools -> Services -> Vacuum: Send Command command is "get_clean_summary" Select one of your vacuums at the entity. (Then select the other) Get me the response from the debug log. That first error shouldn't be happening based on the diagnostic data you sent me. |
Hello, you can find attached the debug information: With every restart the following error occurs:
The other error with "TypeError: unsupported operand type(s) for /: 'list' and 'int'" is not available anymore... |
Just to confirm all of your other entities show up, correct? |
Yes, that is correct. Only the image entities are unavailable. |
Thanks! Fix is working. |
The problem
Hello,
with the newest beta version of home assistant two errors/warnings occur (see logs) during start of home assistant. The map entities of my two roborocks could not be initialized during startup and are not available anymore. Every vaccum has only one map availalble.
What version of Home Assistant Core has the issue?
core-2024.5.0b1
What was the last working version of Home Assistant Core?
core-2024.4
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
DELETED
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: