core icon indicating copy to clipboard operation
core copied to clipboard

Homekit bridge stateless programmable switch showing “not supported” after a few days

Open lightingghost opened this issue 8 months ago • 2 comments

The problem

I have a zigbee programmable button, and was connected to home assistant via zigbee2mqtt.

I also configured homekit bridge to bridge this button to apple home, by adding the button in advanced configuration of programmable switches.

It works OK at first (despite not showing the single press, double press, long press options). However, after a few days, the switch in apple home showed “not supported”, and configured actions no longer works.

Image

Is there anything I am doing wrong? any help will be appreciated

What version of Home Assistant Core has the issue?

core-2025.2.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Homekit Bridge

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet


Anything in the logs that might be useful for us?


Additional information

No response

lightingghost avatar Mar 23 '25 03:03 lightingghost

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

Code owner commands

Code owners of homekit_controller 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_controller 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_controller documentation homekit_controller source (message by IssueLinks)

home-assistant[bot] avatar Mar 23 '25 10:03 home-assistant[bot]

I have the same issue with HomeKit integration. After the update I lost actions like single press, double press and long press. Automations also stopped working due to lack of actions in entities

I was even about to add my case here, but after performing several HA restarts and reloading the configuration + changing the language to English, it suddenly turned out that the buttons were available!

ravek71 avatar Mar 25 '25 21:03 ravek71

I have the same issue with HomeKit integration. After the update I lost actions like single press, double press and long press. Automations also stopped working due to lack of actions in entities

I was even about to add my case here, but after performing several HA restarts and reloading the configuration + changing the language to English, it suddenly turned out that the buttons were available!

Thank you! This is not the case for me -- I restarted HA, and the button is still showing "not supported"

I believe this is a bug since this button was previously used with homebridge and no issue.

lightingghost avatar Mar 26 '25 20:03 lightingghost

After the update I lost actions like single press, double press and long press. it have the same issue here! :/

Manuel2030 avatar Apr 22 '25 10:04 Manuel2030

any solutions?

Manuel2030 avatar Apr 22 '25 10:04 Manuel2030

Image any solutions after this problem?

Manuel2030 avatar Apr 22 '25 10:04 Manuel2030

okay i updaterd everything to the latest home assistant not it worked again... well i think it was a bug?!

Manuel2030 avatar Apr 22 '25 10:04 Manuel2030

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.