You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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)
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:
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
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: