Update Xiaomi Vacuum to new StateVacuumDevice

[cnrd]

Description:

Adds support for states to the Xiaomi Vacuum Platform, this can be merged after: #15573

It also introduce breaking changes, as it no longer uses:

• STATE_ON
• STATE_OFF

Also removes any functions related to ToggleEntity, which results in the following services no longer working:

• turn_on (Use start instead)
• turn_off (Use return_to_dock instead)
• toggle (No replacement)

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#5902

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

[houndci-bot]

line too long (87 > 79 characters)

[cnrd]

@syssi @rytilahti Can you take a look at this, so that we may get this in the same release as #15573 ? :-)

[arbreng]

Part of: home-assistant/architecture#29

[cnrd]

@rytilahti @syssi Sorry for asking again, but could one of you chime in on this, such that it can be a part of the same release as the Component changes in: #15751

[syssi]

LGTM. I cannot test the changes because I don't own the device.

[cnrd]

I have been running it here since I pushed the changes to the PR without problems.

[marciogranzotto]

@cnrd this broke my node-red automation. The state doesn't have enough information anymore. When calling the service xiaomi_remote_control_move_step I used to get state change from charging to manual mode and then from manual mode to idle. Now I get from idle to unknown and then unknown to idle.

[cnrd]

The proposal have been open for a long time: home-assistant/architecture#29 remote was not identified as a common state and as such is not supported. The best thing we can do currently is change that unknown to cleaning.

I'm not sure how many vacuums support remote, so you may have to propose to have it added in that thread such that people who use other vacuums can chip in on wether it makes sense to add that state or not.