Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Button integration doesn't inform HomeKit about button press #62935

Closed
amirharush opened this issue Dec 28, 2021 · 5 comments
Closed

New Button integration doesn't inform HomeKit about button press #62935

amirharush opened this issue Dec 28, 2021 · 5 comments

Comments

@amirharush
Copy link

The problem

The newly introduced button integration doesn't tell HomeKit when a button is pressed. I configured a basic MQTT button, and exported it to HomeKit where it shows correctly.

When activating the button (e.g. using the developer tools --> call service), the activity log shows it was pressed but in HomeKit, where I have an automation triggered by this button, the button never turns on.

What version of Home Assistant Core has the issue?

2012.12.6

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

MQTT Button

Link to integration documentation on our website

https://www.home-assistant.io/integrations/button.mqtt/

Example YAML snippet

button_script_9_2:
  alias: Family Area - OFF
  mode: single
  sequence:
    - service: light.turn_off
      target:
        area_id:
          - or_s_room
          - east_balcony
          - noam_s_room
          - kids_bath
          - family_room
          - guest_bathroom
    - service: button.press
      target:
        entity_id: button.shutdown_family_area

Anything in the logs that might be useful for us?

Nothing in the logs but the normal stuff

Additional information

No response

@probot-home-assistant
Copy link

mqtt documentation
mqtt source
(message by IssueLinks)

@probot-home-assistant
Copy link

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

@frenck
Copy link
Member

frenck commented Dec 28, 2021

That would be correct actually? It is an stateless switch.

@amirharush
Copy link
Author

amirharush commented Dec 28, 2021

Well, the reverse works - if I trigger the button in the home app, the button is pressed in Home Assistant. I would expect the reverse to also work (momentarily of course, as you pointed out). BTW, I don't believe the issue is MQTT, but rather how the button integrates with HomeKit.

Here's the button definition in the configuration.yaml:

button:
  - platform: mqtt
    unique_id: shutdown_family_area
    command_topic: "home/family_area/shutdown"
    name: "Shutdown Family Area"

@frenck
Copy link
Member

frenck commented Dec 28, 2021

Well, the reverse works - if I trigger the button in the home app, the button is pressed in Home Assistant.

That is correct, that is its purpose.

I would expect the reverse to also work

Nope.

@github-actions github-actions bot added the stale label Jan 27, 2022
@github-actions github-actions bot closed this as completed Feb 3, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Mar 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants