You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it is bug or feature.
According to documentation there should be sensor entity called Last Cleaning.
The only similar one I can find is sensor.(deebot_name)_vac_cleaning_duration
And as name states it holds only pure vacuum cleaning duration and does not change if mop or combined cleaning is done.
I think it would be useful to have cleaning duration regardless of type of the cleaning (or separate for every type)
On which deebot device (vacuum) you have the issue?
Deebot Omni T30s
Which version of the deebot-client are you using?
from HA 2025.2.5
Country
pl
Continent
eu
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered:
The last cleaning sensor is only shown if your vacuum is supporting it.
To check if that's the case, please send me your model id (The one in the brackets on the device page. See example below)
About the cleaning sensor: Please enable debug logs and perform a short mop and combined cleaning. Afterwards, please upload your logs here. I can only show this information if the bot is providing them
Checks
The problem
Not sure if it is bug or feature.
According to documentation there should be sensor entity called Last Cleaning.
The only similar one I can find is sensor.(deebot_name)_vac_cleaning_duration
And as name states it holds only pure vacuum cleaning duration and does not change if mop or combined cleaning is done.
I think it would be useful to have cleaning duration regardless of type of the cleaning (or separate for every type)
On which deebot device (vacuum) you have the issue?
Deebot Omni T30s
Which version of the deebot-client are you using?
from HA 2025.2.5
Country
pl
Continent
eu
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: