Core: xiaomi_miio: vacuum.set_fan_speed not working on fw: 3.5.7_002008+

Created on 12 Mar 2020  Â·  7Comments  Â·  Source: home-assistant/core

The problem


The issue I have is that I upgraded my Xiaomi Roborock S55 to the newest version 3.5.7_002008 and now the set_fan_speed is not working. The only one that is working is "Gentle".

I tested this with the newest iOS-app. When in Home Assistant I choose Gentle, in the app the fan speed goes to Gentle, that works. When I choose something else in Home Assistant, the fan speed goes back to Standard in the app and shows 102 in Home Assistant.

image

Environment

  • Home Assistant release with the issue: 0.106.6
  • Last working Home Assistant release (if known): None because It just bought this vacuum.
  • Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
  • Integration causing this issue: xiaomi_miio
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/vacuum.xiaomi_miio/

Problem-relevant configuration.yaml

I'm just using this:

vacuum:

  • platform: xiaomi_miio
    host: 192.168.1.2
    token: YOUR_TOKEN

Traceback/Error logs

I have none because it is something in de configuration in this integration.

Additional information

I'm a tester, so I tried to get the correct info. If found this in the integration:

FAN_SPEEDS = {"Silent": 38, "Standard": 60, "Medium": 77, "Turbo": 90, "Gentle": 105}

This should be:

FAN_SPEEDS = {"Silent": 101, "Standard": 102, "Medium": 103, "Turbo": 104, "Gentle": 105}

xiaomi_miio

Most helpful comment

Just submitted a PR to fix this issue ✌

All 7 comments

Happening as well with Roborock S6 from previous versions as well.
Setting fan speed as number does work,

Hey there @rytilahti, @syssi, mind taking a look at this issue as its been labeled with a integration (xiaomi_miio) you are listed as a codeowner for? Thanks!

This should be:

FAN_SPEEDS = {"Silent": 101, "Standard": 102, "Medium": 103, "Turbo": 104, "Gentle": 105}

@duhow can you confirm these speed numbers?

I fixed it for me by overriding this integration in the folder custom components with the above values.

Confirming the issue, the issue started with FW 3.5.7_002008. Also confirming the new values.

Just submitted a PR to fix this issue ✌

This is duplicate of #31268.

Was this page helpful?
0 / 5 - 0 ratings