Fan group will not turn on included "switch as fan" entity if percentage speed specified

[krazos]

The problem

There seems to be a bug in the new fan group (or possibly the new Switch as X function) that prevents the fan.turn_on service from turning on a smart switch that has been converted to a fan entity using Switch as X and subsequently grouped with another fan, if the fan.turn_on service call targeting the fan group includes a percentage setting.

The fan.turn_on service call works properly when targeting the converted switch-to-fan entity directly (i.e., the switch turns on and the percentage speed is ignored), but if the target is instead the fan group that includes the converted switch-to-fan entity, the other "real" fan entities in the group turn on, but the converted switch-to-fan entity does not turn on. On the other hand, if the fan.turn_on service call targeting the fan group does not include a percentage speed setting, then all grouped entities turn on as expected.

What version of Home Assistant Core has the issue?

core-2022.4.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Group

Link to integration documentation on our website

https://www.home-assistant.io/integrations/group/

Diagnostics information

No response

Example YAML snippet

Hypothetical Fan Group YAML Configuration:

fan:
  - platform: group
    name: Bedroom Fans
    entities:
      - fan.bedroom_ceiling_fan #  (native fan entity)
      - fan.bedroom_lectrofan #  (converted switch-to-fan entity)

Service Call:

service: fan.turn_on
data:
  percentage: 66
target:
  entity_id: fan.bedroom_fans

Anything in the logs that might be useful for us?

I do not see anything relevant in the logs, or any relevant diagnostics data for the fan group or the converted switch-to-fan entity.

Additional information

No response

[probot-home-assistant[bot]]

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

[probot-home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (group) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[krazos]

Tested again, and this is still an issue in core-2022.4.6.

Any suggestions as to what might be causing this issue?

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[krazos]

This is still an issue as of 2022.7.6.

[timothysantos]

Still an issue as of 2022.10.5 too

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.