HomeKit initiating "vacuum.start" instead of "vacuum.turn_on" service for Deebot N79s entity.

[dekay7]

The problem

When turning on my RoboVac's accessory in HomeKit, it initiates the "vacuum.start" service instead of "vacuum.turn_on" service for the Deebot N79s entity. The Deebot status does not change with the "vacuum.start" but it starts cleaning with "vacuum.turn_on".

Environment

• Home Assistant Core release with the issue: 2021.1.1
• Last working Home Assistant Core release (if known):
• Operating environment (OS/Container/Supervised/Core): Raspberry Pi OS Docker Container Supervised
• Integration causing this issue: HomeKit and Ecovacs
• Link to integration documentation on our website: HomeKit Integration and Ecovacs Integration

Problem-relevant configuration.yaml

ecovacs:
  username: email
  password: password
  country: US
  continent: NA

Traceback/Error logs

none

Additional information

nope! that's literally it.

[frenck]

Your issue template is lacking information. Please fill out the given template as much as possible.

Without it, we can't help you.

Thanks already! 👍

[dekay7]

there isn't really much to it, it is just that the homekit accessory is initiating the wrong service...

[frenck]

Still, please fill out the issue template. Thanks.

[dekay7]

done?

[probot-home-assistant[bot]]

ecovacs documentation ecovacs source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

homekit documentation homekit source _{^{(message by IssueLinks)}}

[bdraco]

        if features & (vacuum.SUPPORT_START | vacuum.SUPPORT_RETURN_HOME):
            a_type = "DockVacuum"

The current code assumes that we should use start if SUPPORT_RETURN_HOME or SUPPORT_START

[dekay7]

yes i see that, however, my deebot does support return home, but it doesn't support start. Home Assistant Vacuums refer to this link to see the service that needs to be initiated for specific robo vac brands.

[dekay7]

the issue isn't fixed...

[bdraco]

Did you pull in the new code from the PR?

[dekay7]

yes it was updated even before i setup the integration in the first place. it still doesn't work. ill fix it later locally.