home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.94k stars 29.03k forks source link

Fan entity shows additional controls in HomeKit when preset_modes is available #105179

Closed ejjoman closed 1 month ago

ejjoman commented 7 months ago

The problem

As soon as a fan component provides preset_modes, it gets additional controls in the Apple Home App and the oscillating switch disappears. In the example provided, I added two fans that are identical, but one provides preset_modes and the other does not. I have attached some screenshots of the results.

Buggy fan:

Working fan:

What version of Home Assistant Core has the issue?

core-2023.12.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

homekit

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

- platform: template
  fans:
    buggy_fan:
      friendly_name: "Buggy HomeKit fan"
      value_template: "on"
      percentage_template: 20
      oscillating_template: false
      speed_count: 10
      preset_modes:
        - Auto
        - Normal
      turn_on:
      turn_off:
      set_percentage:
      set_preset_mode:
      set_oscillating:

    working_fan:
      friendly_name: "Working HomeKit fan"
      value_template: "on"
      percentage_template: 20
      oscillating_template: false
      speed_count: 10
      turn_on:
      turn_off:
      set_percentage:
      set_preset_mode:
      set_oscillating:

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 7 months ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `homekit` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homekit` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


homekit documentation homekit source (message by IssueLinks)

issue-triage-workflows[bot] commented 4 months ago

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.

ejjoman commented 4 months ago

This bug is still present in HA 2024.3.0.

issue-triage-workflows[bot] commented 1 month ago

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.