Log error in 2025.8.0b0 for roborock

[luca-angemi]

The problem

Detected that integration 'roborock' is setting the battery_level which has been deprecated. Integration roborock should implement a sensor instead with a correct device class and link it to the same device.

Detected that integration 'roborock' is setting the battery supported feature which has been deprecated. Integration roborock should remove this as part of migrating the battery level and icon to a sensor.

What version of Home Assistant Core has the issue?

2025.8.0b0

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @Lash-L, @allenporter, mind taking a look at this issue as it has been labeled with an integration (roborock) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of roborock can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign roborock Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

roborock documentation
roborock source
_{^{(message by IssueLinks)}}

[mib1185]

re.: Vacuum battery properties are deprecated

[allenporter]

@gjohansson-ST can you help me understand what integrations are supposed to do for this migration?

My impression is this integration is already creating a battery sensor yet we want to keep this functionality around for a year to avoid an immediate breaking change. My impression is the integration is already in the right end state, but the user needs to know not to use the battery level in an automation for example. My impression is the intent of this warning is not for integrations to remove this attribute otherwise it breaks but the blog post says it should keep working for a year. Is there something that the integration needs to set to ACK that it has created a battery sensor for the device that i'm missing?

[gjohansson-ST]

Hi @allenporter
Props are always breaking as we don't have a way for deprecating it. So since you have the right sensor, just remove the battery props and mark the PR as breaking.
The reason for 1 year deprecation is because integration owners should have time to make the necessary sensor (which is already existing in this integration)