Missing roborock sensors in 2025.12.0b0

[Gloomyeye]

The problem

Hello,

some sensors are missing in HA 2025.12.0b0. The following sensors are now unavailable for my robots:

select.roborock_dock_poppy_emptying_mode (Entleerungsmodus)
switch.roborock_vacuum_poppy_charge_outside_offpeak (Laden zum Niedertarif)
switch.roborock_vacuum_poppy_child_lock (Kindersicherung)
switch.roborock_vacuum_rocky_child_lock (Kindersicherung)

I had also the problem in issue #157366 and delete the requested folder. After folder deletion, I could load the integration again.

The missing sensors where available with the old version core-2025.11.3.

What version of Home Assistant Core has the issue?

core-2025.12.0b0

What was the last working version of Home Assistant Core?

core-2025.11.3

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

config_entry-roborock-438806a5fae17ebb36a43cb0ae03daf9.json

Example YAML snippet

Anything in the logs that might be useful for us?

No entry in logs

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)}}

[allenporter]

Thank you, the report is very helpful.

For the image sensor: Does this device currently have multiple maps? (e.g. are there multiple image sensors and some work and some do not?. To diagnose it may be helpful to run with debug logging on for the integration when it loads.

Will also look at these:

• valley timer
• emptying mode
• Child lock looks entirely broken

[allenporter]

(1) On child lock and off peak energy:
The device features currently say:

            "isSetChildSupported": false,
            "isSupportedValleyElectricity": false,

so the device claims to not support these features. Are you aware that these are supported? I am wondering if they were incorrectly created before and shouldn't have been. (though now dangling, so maybe we need to clean them up)
(2) On emptying mode -- i can't find a reference to that anywhere in the code. i wonder if that has another name?

[Lash-L]

(2) On emptying mode -- i can't find a reference to that anywhere in the code. i wonder if that has another name?

This could be a holdover on the device from the custom component - it may have had that entity

[Gloomyeye]

In general, I renamed my sensors with a new entity id which matches my entitiy id schema.

Thank you, the report is very helpful.

For the image sensor: Does this device currently have multiple maps? (e.g. are there multiple image sensors and some work and some do not?. To diagnose it may be helpful to run with debug logging on for the integration when it loads.

Will also look at these:

* valley timer

* emptying mode

* Child lock looks entirely broken

I found out that a new image sensor was another name was created. So, map sensor is now avaialble. I deleted the old sensor and use now the new sensor.

(1) On child lock and off peak energy: The device features currently say:

            "isSetChildSupported": false,
            "isSupportedValleyElectricity": false,

so the device claims to not support these features. Are you aware that these are supported? I am wondering if they were incorrectly created before and shouldn't have been. (though now dangling, so maybe we need to clean them up) (2) On emptying mode -- i can't find a reference to that anywhere in the code. i wonder if that has another name?

These two sensors were available in the previous version and were fully functional . The values of the sensors were correct and show the child locks for both robots and the offpeak charging option for my S8 Pro Ultra. In addition, the time sensors (e.g. time.roborock_vacuum_poppy_charge_outside_offpeak_start and time.roborock_vacuum_poppy_charge_outside_offpeak_end) are also not available.

The emptying mode sensor shows how the dock can be cleaned (e.g. value smart). This was also available in the previous version.

In general, I didn't use the custom component version from hacs.

[Gloomyeye]

Here is the debug log from the HA start: home-assistant_roborock_2025-11-27T07-32-13.532Z.log

[Gloomyeye]

Short update: HA 2025.12.0b1 shows the same behaviour. Sensors are still missing.

[allenporter]

I am able to reproduce the map issue. The entity appears to have changed names.

Currently its images.<device name> but used to be image.<device name>_<map name> so I will see if there is something that was accidentally changed. I am wondering if something is happening when the map is not named.

[allenporter]

For device features: I think the issue is that all of the features are not loaded and we didn't do any device feature discovery.