VacuumActivity cleaning modes

[sca075]

I would add the mopping states to the vacuum entities, this is a quite easy modification and would give the possibility (as many new vacuums have the mopping capabilities) to monitor when the vacuum do a simple vacuuming operation or a mopping one.

The VacuumActivity are currently defined in vacuum cost as:

class VacuumActivity(StrEnum):
    """Vacuum activity states."""

    CLEANING = "cleaning"
    DOCKED = "docked"
    IDLE = "idle"
    PAUSED = "paused"
    RETURNING = "returning"
    ERROR = "error"

The states to add in the VacuumActivity will be:

class VacuumActivity(StrEnum):
    """Vacuum activity states."""

    CLEANING = "cleaning"
    DOCKED = "docked"
    DOCK_MOP_CLEAN = "docked cleaning mop"
    DOCK_MOP_DRYING = "docked mop drying"
    IDLE = "idle"
    PAUSED = "paused"
    RETURNING = "returning"
    ERROR = "error"
    MOPPING = "mopping"

The current cleaning state might be kept as it is in order to prevent braking changes. As well most of the vendor apps make a net distinctions between normal "Cleaning" and "Mopping", this would allow also MQTT future vacuums improvements as proposed in here home-assistant/core#155595 (comment)

[gjohansson-ST]

Proposals are already in discussion #684

[sca075]

I had a look at the discussion and also left a comment but it looks there's no progress since quite long over there. I probably under estimated the changes are quite drastic to the current implementation.. anyhow would give it a try.. if we here agree is worth to invest time on it.

[gjohansson-ST]

Well, that proposal seems stuck given no one really further commented on the missing parts.
If you want any traction on this proposal you need to update it to reflect the comments on that one:

• Which integrations can benefit from it
• Comments here Add mop and empty bin support to the vacuum component #684 (comment)

[sca075]

I did a little more of that actually I put a little time to modify the code and test the modifications. It looks that this part of the code will need to be review at 2026.2 so the PR was closed understanding that makes no sense to modify the model many times.

Will keep an eye on this and hopefully the approval loop will be processed soon.