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
74.21k stars 31.16k forks source link

Home Assistant scenes are not transferred to HomeKit Bridge as a scene. #124379

Open MiLeX84 opened 3 months ago

MiLeX84 commented 3 months ago

The problem

When creating scenes in Home Assistant, you can add them to your Apple Home via HomeKit Bridge. The issue is that the scenes are transferred as a button, not as a scene. As owner of Philips Hue items, I know that scenes can be handed over from Hue to Apple Home as an actual scene, therefore it should be possible for Home Assistant to do the same with it's own scenes.

What version of Home Assistant Core has the issue?

core-2024.8.2

What was the last working version of Home Assistant Core?

NA

What type of installation are you running?

Home Assistant OS

Integration causing the issue

HomeKit Bridge

Link to integration documentation on our website

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

Diagnostics information

NA

Example YAML snippet

NA

Anything in the logs that might be useful for us?

NA

Additional information

Not really, HomeKit Bridge simply hands over scenes in the incorrect manner, they will show up as toggle buttons, but should show up as a scene. If the toggle button is a desired feature, perhaps an option how scenes are handed over would be a good idea.

The Eve app is also able to manage and edit said scenes. https://apps.apple.com/us/app/eve-for-matter-homekit/id917695792

HMActionSet Class: Scenes in HomeKit are managed using the HMActionSet class. Documentation Link: HMActionSet Class Reference

home-assistant[bot] commented 3 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)

home-assistant[bot] commented 3 months ago

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (mobile_app) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `mobile_app` 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 mobile_app` 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)


mobile_app documentation mobile_app source (message by IssueLinks)

bdraco commented 3 months ago

This issue is a feature request for the mobile_app since the HomeKit integration is a HAP server that doesn't have API access to the iOS device and thus cannot create native HomeKit scenes

MiLeX84 commented 3 months ago

I see you already added the feature request tag. Thanks!

Would be nice if this would be possible, as scenes are an important and widely used feature. While I work mostly with the HA dash, either in browser or companion app, the rest of the family would like to keep using the iOS HomeKit app and never touch HA.

Having everything in HomeKit, working properly, while the actual automations are handled in HA, invisible to the family, is a big WAF gain.

In general, I have no idea what Philips is doing differently, all I see is that both the Philips Hue Bridge and the HA HomeKit Bridge are added to HomeKit as a third party bridge, one is able to add native scenes, the other is not.

rentrop commented 1 month ago

+1 that would be great!

Second Issue with the current implementation: Each scene is exported as button in HomeKit. Switching on the HK-button activates the Scene in HomeAssistent. Switching off the HK-button does nothing.

Meaning one can not use the switch-off as an automation trigger...

abort commented 3 weeks ago

+1 that would be great!

Second Issue with the current implementation: Each scene is exported as button in HomeKit. Switching on the HK-button activates the Scene in HomeAssistent. Switching off the HK-button does nothing.

Meaning one can not use the switch-off as an automation trigger...

Just came across this and am experiencing the same. Would be a great improvement to have actual scene integrations

jfedyczak commented 1 week ago

+1 to the above - scene is exposed as a stateful switch...