HomeKit integration devices unresponsive #84387

brsnik · 2022-12-21T16:43:55Z

The problem

After adding the integration, and selecting which devices to include etc.
I am scanning the QR and adding it to Apple Home. It does get added but this is where everything breaks.

The devices get their current state shown in the Home app, but become unresponsive immediately after adding them.
For example if a light is on, it shows as on in the Home app. But if I try to change it's not responsive. And then shows no response.

Also when I include more devices from the HA UI, they don't get updated and don't show up in the Home app.

I've deleted and reinstalled the integration a few times still the same issue.

Don't know if this is relevant but I am using the MariaDB add-on.

What version of Home Assistant Core has the issue?

2022.12.7

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

config_entry-homekit-d81ec6216377cf1eecfc09333e7a5d2f.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing in the system logs. If there is another way to get logs for this integration please let me know I'll share them.

Additional information

No response

home-assistant · 2022-12-21T16:43:58Z

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 Change the title of 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.

_{^{(message by CodeOwnersMention)}}

homekit documentation
homekit source
_{^{(message by IssueLinks)}}

Nbr1Sniper · 2022-12-24T00:15:46Z

Similar issue here…. I also have an issue with HomeKit seeing the device if power was lost then restored. Only way to discover it has power again is if I restart HA.

gaoyixiang · 2022-12-25T12:07:58Z

I have the same question, I think maybe apple update the homekit architecture.

andersovreseth · 2023-01-01T20:51:29Z

I also have this issue and suspect it is due to the homekit architecture upgrade. I did the upgrade, after updating all of my devices to IOS 16.3, and have not been able to connect to any "native HA devices" through Home Assistant Bridge. I am running HA 2022.12.8.

andersovreseth · 2023-01-01T20:52:17Z

Hopefully it will be fixed either by Apple in IOS 16.4 or in Home Assistant Bridge.

Nbr1Sniper · 2023-01-01T21:14:06Z

Everything I have is on 16.2 and have this issue. Thanks, Guy M. DeFazio On Jan 1, 2023, at 3:52 PM, andersovreseth ***@***.***> wrote: Hopefully it will be fixed either by Apple in IOS 16.4 or in Home Assistant Bridge. — Reply to this email directly, view it on GitHub<#84387 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE7XNNO7VKAMCOZEXYYGZF3WQHVAZANCNFSM6AAAAAATF2HJ2M>. You are receiving this because you commented.Message ID: ***@***.***>

miquellaboria · 2023-01-07T13:17:23Z

I have this issue, to fix I have removed bridge and readded and it works.

But if Homekit Hub change to another ATV or Homepod all accessories are inaccessible and the log of HAS appears:

de gen. 07 13:18:44 raspberrypi hass[4366]: 2023-01-07 13:18:44.781 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.36’, 54915): Client xxx attempted pair verify without being paired to HASS Bridge first.

de gen. 07 13:18:44 raspberrypi hass[4366]: 2023-01-07 13:18:44.804 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.36’, 54916): Client xxx attempted pair verify without being paired to HASS Bridge first.

de gen. 07 13:18:56 raspberrypi hass[4366]: 2023-01-07 13:18:56.509 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.58’, 59159): Client xxx attempted pair verify without being paired to HASS Bridge first.

de gen. 07 13:18:56 raspberrypi hass[4366]: 2023-01-07 13:18:56.537 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.58’, 59160): Client xxx attempted pair verify without being paired to HASS Bridge first.

de gen. 07 13:18:56 raspberrypi hass[4366]: 2023-01-07 13:18:56.610 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.58’, 59161): Client xxx attempted pair verify without being paired to UE32J5500 first.

de gen. 07 13:18:56 raspberrypi hass[4366]: 2023-01-07 13:18:56.635 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.58’, 59162): Client xxx attempted pair verify without being paired to UE32J5500 first.

de gen. 07 13:18:56 raspberrypi hass[4366]: 2023-01-07 13:18:56.680 ERROR (MainThread) [pyhap.hap_handler] (‘192.168.1.58’, 59163): Client xxx attempted pair verify without being paired to UE40F7000 first.

shuiguojiao · 2023-01-09T03:45:06Z

I have the same issue.
Unpair HomeKit bridge and pair it again fixed it.

kylecwhite · 2023-01-09T10:27:15Z

Same issue here. It will work when I remove and repair bridge. It at some point in next day or so it stops working.

andersovreseth · 2023-01-09T10:38:21Z

I have updated all of my Apple devices to 16.3, including Apple TV and Homepod (that are both Homekit servers). After this update I removed the Homekit bridge and created a new in HA. This allowed me to get most of the devices to work again and become available in the Home app. I had to add some cameras in a separate bridge in auxillary mode, but this is recommended in any case so I think it is a better solution.

kevin7s-io · 2023-01-09T13:41:55Z

same issue (more or less) here.

Whenever a "home hub" is enabled, all devices from the HA HomeKit bridge are unresponsive.
Removing and adding the bridge back has no effect. It is 100% repeatable.

All Apple TVs, which function as hubs, are running 16.2.

qis90 · 2023-01-26T17:47:20Z

Exactly as you state here, I fix the issue after I disable "home hub" in my Apple TV

same issue (more or less) here.

Whenever a "home hub" is enabled, all devices from the HA HomeKit bridge are unresponsive. Removing and adding the bridge back has no effect. It is 100% repeatable.

All Apple TVs, which function as hubs, are running 16.2.

bdraco · 2023-01-26T18:24:54Z

Ymmv but There have been some reports that updating every home hub device to 16.3 has resolved this for some

brsnik · 2023-01-27T16:47:25Z

The problem has been resolved for me too. I am not sure if it has anything to do with the new update.

joshbish · 2023-01-30T04:28:08Z

All of my hubs have been updated to 16.3 and this issue is still happening for me. Is there something else that you all did after 16.3 to get it to work again?

brsnik · 2023-01-30T21:17:55Z

@joshbish My HA was on a different subnet, 10.6.x.x/16 designated for IoT, while my personal devices aka. phone on another subnet 10.10.x.x/16. Since then I have moved only the HA to the 10.10 network, and allowed it to communicate with the 10.6 network devices. And it worked. I've not had this issue prior, but I guess Apple has changed something...
Maybe you have a similar setup?

RoyHP · 2023-04-23T20:21:22Z

I'm having the same problem on iOS 16.4.1 and the new HomeKit Architecture upgrade. Devices are briefly available after recreating the homekit bridge, but shortly become unresponsive and stay that way in homekit.

RoyHP · 2023-04-23T23:11:31Z

Attached my debug log file for the HASS bridge. This seems to happen when using the dimmer slider in iOS on a switch. I think it's overloading the network with events according to the log and everything becomes unresponsive. This is trying to control a single ZHA group with 9 hue bulbs in it.
home-assistant_homekit_2023-04-23T23-09-00.031Z.log

bdraco · 2023-04-25T23:14:26Z

Your keys are out of sync or iCloud is failing to sync.

2023-04-23 13:45:40.710 ERROR (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49372): Client 83bc69d7-7f01-4313-8677-133a3aaa7104 attempted pair verify without being paired to HASS Bridge first.

https://www.home-assistant.io/integrations/homekit/#unpairing-and-re-pairing

If that doesn't work, delete the bridge and recreated it.

Finally you can do a full reset to cleanup iCloud:

https://www.reddit.com/r/HomeKit/comments/yy2oy7/apple_has_a_downloadable_profile_to_really_clear/#:~:text=After%20installing%20the%20profile%2C%20the,the%20process%20to%20nuke%20everything.

RoyHP · 2023-04-27T03:03:27Z

Your keys are out of sync or iCloud is failing to sync.

2023-04-23 13:45:40.710 ERROR (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49372): Client 83bc69d7-7f01-4313-8677-133a3aaa7104 attempted pair verify without being paired to HASS Bridge first.

https://www.home-assistant.io/integrations/homekit/#unpairing-and-re-pairing

If that doesn't work, delete the bridge and recreated it.

Finally you can do a full reset to cleanup iCloud:

https://www.reddit.com/r/HomeKit/comments/yy2oy7/apple_has_a_downloadable_profile_to_really_clear/#:~:text=After%20installing%20the%20profile%2C%20the,the%20process%20to%20nuke%20everything.

@bdraco Thanks for the insight! I tried the full reset and am still having the issue, and it's worse now. I did the following:

Deleted the HASS homekit bridge in HA.
Factory "Reset and Update" the apple tv which is the home hub (10.23.1.228).
Ran the homekit reset from the profile link you provided.
Waited about 10 minutes and restarted my other Apple devices.
Set up the apple tv using my iphone.
Created a new home.
Created a new HASS homekit bridge in HA, paired it with the QR code.

Now the ZHA-grouped light (which has always worked perfectly in HA directly. It consists of 9 Hue bulbs.) immediately shows up as "No Response" and I can't use it at all, when I used to be able to use it for a few minutes before it started showing No Response and saying "The accessory is not responding."

I've attached a new log file, which seems to show that same error...
For reference both the iphone and apple tv are running the latest iOS with the "new homekit infrastructure upgrade" applied. I'm using the SkyConnect.

It seems that HomeKit/HASS for me is entirely unusable. At this point I'm not sure what else I can do to fix this bridge key pairing issue. I saw some sqlite foreign key constraint failures in the logs - could it be that there's some database corruption on the HA side of things? Should I try reinstalling HA?

home-assistant_homekit_2023-04-27T01-48-55.362Z.log

(Am very thankful for your response though @bdraco )

bdraco · 2023-04-27T18:32:18Z

2023-04-23 13:45:40.710 ERROR (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49372): Client 83bc69d7-7f01-4313-8677-133a3aaa7104 attempted pair verify without being paired to HASS Bridge first.

It looks like it was unpaired here

2023-04-23 19:02:10.241 DEBUG (MainThread) [pyhap.hap_protocol] ('10.23.1.228', 49733) (81656c9f-de5b-46e8-b25c-6c6b142718d3): Recv decrypted: b'GET /characteristics?id=390094243.10,390094243.9,390094243.11 HTTP/1.1\r\nHost: HASS\\032Bridge\\03281F602._hap._tcp.local\r\n\r\n'
``2023-04-23 19:04:51.215 DEBUG (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49734): Pair verify with client completed. Switching to encrypted transport.`

And then at the end there is another client uuid being forwarded though the apple tv:

2023-04-26 21:45:14.132 ERROR (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49160): Client 9cb60465-c562-4968-9be0-0162317f1f4d attempted pair verify without being paired to HASS Bridge first.

Is it possible you have another iOS device in the home that is holding on to the old pairings that didn't get cleaned up when you reset your iPhone's homekit?

foru17 · 2023-05-03T10:39:56Z

A few months ago, after upgrading to iOS, all my devices lost connection and were unresponsive. After reading recent forum discussions and updates, I was able to solve the problem by following these steps:

Upgrade HASS to the latest version;
Upgrade iOS to version 16.4.1;
Disable other home pub devices in my home network (mine is the "Home Hub" Setting in AppleTV).

After doing this, everything was restored. Steps 1 and 2 alone did not work - step 3 of disabling the hub was necessary for a solution, as turning it on/off reproduced the disconnection issue.

RoyHP · 2023-05-03T13:24:21Z

2023-04-23 13:45:40.710 ERROR (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49372): Client 83bc69d7-7f01-4313-8677-133a3aaa7104 attempted pair verify without being paired to HASS Bridge first.

It looks like it was unpaired here

2023-04-23 19:02:10.241 DEBUG (MainThread) [pyhap.hap_protocol] ('10.23.1.228', 49733) (81656c9f-de5b-46e8-b25c-6c6b142718d3): Recv decrypted: b'GET /characteristics?id=390094243.10,390094243.9,390094243.11 HTTP/1.1\r\nHost: HASS\\032Bridge\\03281F602._hap._tcp.local\r\n\r\n' ``2023-04-23 19:04:51.215 DEBUG (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49734): Pair verify with client completed. Switching to encrypted transport.`

And then at the end there is another client uuid being forwarded though the apple tv:

2023-04-26 21:45:14.132 ERROR (MainThread) [pyhap.hap_handler] ('10.23.1.228', 49160): Client 9cb60465-c562-4968-9be0-0162317f1f4d attempted pair verify without being paired to HASS Bridge first.

Is it possible you have another iOS device in the home that is holding on to the old pairings that didn't get cleaned up when you reset your iPhone's homekit?

Thanks @bdraco - just to keep you updated, I am trying to do the full reset again but waiting at least a week (instead of just 30 minutes) for all of my devices to hopefully sync up with the new home instance before trying the HASS integration again. I'll let you know how it goes.

Dryusdan · 2023-05-10T16:00:46Z

Hi

I have the same issue here. I use home assistant OS and it manage all smart thing (except the HomePod) in my home.
I bought an HomePod mini (so it's also an home hub) (192.168.1.89).
I use Apple only as a remote (to switch on and off the light with homekit), all automation are managed by HomeAssistant.

So, I make a homekit bridge via config file (because it's too long when I try to reproduce it to reconfigure anything).

I remove all config/.storage/homekit.* from storage. Remove bridge.
I restart HomeAssistant
I add bridge on Homekit on my Iphone (192.168.1.54) . That work almost every time
I restart HomeAssistant and bridge don't respond :(

I try another way :

Remove all config/.storage/homekit.* from storage. Remove bridge.
Reset homepod.
Add HomePod in new home
Add bridge in my home
Restart Homeassistant

It's work but some functionnality (like "what is humidity in bedroom") don't work :/

In log, I see some curious log

2023-05-10 10:15:54.506 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.54', 50752): Connection made to Home Assistant Bridge
2023-05-10 10:15:54.740 INFO (MainThread) [pyhap.accessory_driver] Paired with 2b0d4fe3-545a-4b39-817a-7935832455e3 with permissions b'\x01'.
2023-05-10 10:15:54.814 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.54', 50753): Connection made to Home Assistant Bridge
2023-05-10 10:15:58.343 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50147): Connection made to Home Assistant Bridge
2023-05-10 10:16:01.009 INFO (MainThread) [pyhap.accessory_driver] Paired with 7e626d7f-4ef6-481b-9a12-c52210572692 with permissions b'\x01'.
2023-05-10 10:16:02.212 INFO (MainThread) [pyhap.accessory_driver] Unpairing client 2b0d4fe3-545a-4b39-817a-7935832455e3.
2023-05-10 10:16:04.986 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50148): Connection made to Home Assistant Bridge
2023-05-10 10:16:05.012 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50148): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:05.113 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50149): Connection made to Home Assistant Bridge
2023-05-10 10:16:05.132 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50149): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:10.957 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50150): Connection made to Home Assistant Bridge
2023-05-10 10:16:10.977 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50150): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:11.425 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50152): Connection made to Home Assistant Bridge
2023-05-10 10:16:11.444 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50152): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.

So I try to dig it and rerun step behind and I see this log (but I set debug mode on pyhap.hap_handler and not pyhap.accessory_driver

So I see :

2023-05-10 10:44:34.555 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '6', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:34.556 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [1/5]
2023-05-10 10:44:34.682 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '457', 'content-type': 'application/pairing+tlv8'}      
2023-05-10 10:44:34.683 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [2/5]
2023-05-10 10:44:34.777 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '159', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:34.778 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [3/5]
2023-05-10 10:44:34.781 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [4/5]
2023-05-10 10:44:34.785 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [5/5]
2023-05-10 10:44:34.789 DEBUG (MainThread) [pyhap.hap_handler] Finishing pairing with admin 2B0D4FE3-545A-4B39-817A-7935832455E3 uuid=2b0d4fe3-545a-4b39-817a-7935832455e3
2023-05-10 10:44:34.856 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '37', 'content-type': 'application/pairing+tlv8'}      
2023-05-10 10:44:34.856 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify [1/2].
2023-05-10 10:44:34.869 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '125', 'content-type': 'application/pairing+tlv8'}     
2023-05-10 10:44:34.869 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify [2/2]
2023-05-10 10:44:34.872 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify with client completed. Switching to encrypted transport.
2023-05-10 10:44:34.878 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request GET for path '/accessories': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local'}
2023-05-10 10:44:38.828 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '37', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:38.828 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify [1/2].
2023-05-10 10:44:38.859 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '125', 'content-type': 'application/pairing+tlv8'}     
2023-05-10 10:44:38.859 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify [2/2]
2023-05-10 10:44:38.862 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify with client completed. Switching to encrypted transport.
2023-05-10 10:44:38.895 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request GET for path '/accessories': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local'}
2023-05-10 10:44:39.316 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request PUT for path '/characteristics': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '59', 'content-type': 'application/hap+json'}

And after I don't see anymore 192.168.1.54 :/
Everything is up to date :)

I think HomePod force connect to Home Assistant Bridge and kill my Iphone connection but don't work properly after that ? 🤔

Do you need more log ? :) (I cannot found a way to make some test or modification on homeassistant OS)

ouchkilljoys · 2023-05-17T03:07:21Z

I'm having the same issue, however I think (and I could be wrong) that my devices added as accessories are working fine, whereas the ones under the home assistant bridge with like 15 odd devices keep having the connection issues, similar story with scrypted devices unaffected its just Home Assistant forwarded ones

Home Assistant Version: 2023.5.3
iOS Device Version: 16.4.1 (a)
Home app new architecture: Yes

junweier · 2023-05-28T03:39:18Z

I also encountered the same problem. As long as I add a new device or restart HomeAssistant, the devices in HomeKit will become unresponsive. I must remove this bridge, restart the router, and add a new bridge to recover. Even if I don't add a device, I won't restart HomeAssistant, and after about 7 days, the device will still be unresponsive
I guess the reason for this issue may be due to the upgrade of the HomeKit architecture, which I also encountered after upgrading the HomeKit architecture

jay7210 · 2023-05-28T13:06:47Z

Same No response issue here!

Been trying to figure this out for the last 48 Hours.

2 Days ago i received a notificaton in Apple Home on Iphone saying there was an Home upgrade available. After update i started to receive NO RESPONSE on all my Entites in Apple Home.

All apple devices are on the latest IOS (16.5).
Home Assistant 2023.5.4
Supervisor 2023.04.1
Operating System 10.1
Frontend 20230503.3.

I have deleted my home via my Iphone,
have then deleted the home kit bridge intergration,
then run the delete profile described here Reddit - Dive into anything
then re added the intergration, then joined it via the QR code. after 3-4 minutes the items return to NO REPONSE.

I have Retarted my router several times with no effect (Unifi UDMP v3.1.9 - network 7.4.156), i have turned off IGMP Snooping - no effect, turned on IGMP Snooping - no effect

If i reload the intergration via the intergration panel, etities recover, but after a couple of miutes return to NO RESPONSE

The biggest head ache is that this was working fine before i accepted the update to upgrade the Apple Home architecture.

Any pointers would be grate full as im loosing my mind trying to find the issue!

TempleZhou · 2023-06-03T06:06:38Z

Hi

I have the same issue here. I use home assistant OS and it manage all smart thing (except the HomePod) in my home. I bought an HomePod mini (so it's also an home hub) (192.168.1.89). I use Apple only as a remote (to switch on and off the light with homekit), all automation are managed by HomeAssistant.

So, I make a homekit bridge via config file (because it's too long when I try to reproduce it to reconfigure anything).

I remove all config/.storage/homekit.* from storage. Remove bridge.
I restart HomeAssistant
I add bridge on Homekit on my Iphone (192.168.1.54) . That work almost every time
I restart HomeAssistant and bridge don't respond :(

I try another way :

Remove all config/.storage/homekit.* from storage. Remove bridge.
Reset homepod.
Add HomePod in new home
Add bridge in my home
Restart Homeassistant

It's work but some functionnality (like "what is humidity in bedroom") don't work :/

In log, I see some curious log

2023-05-10 10:15:54.506 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.54', 50752): Connection made to Home Assistant Bridge
2023-05-10 10:15:54.740 INFO (MainThread) [pyhap.accessory_driver] Paired with 2b0d4fe3-545a-4b39-817a-7935832455e3 with permissions b'\x01'.
2023-05-10 10:15:54.814 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.54', 50753): Connection made to Home Assistant Bridge
2023-05-10 10:15:58.343 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50147): Connection made to Home Assistant Bridge
2023-05-10 10:16:01.009 INFO (MainThread) [pyhap.accessory_driver] Paired with 7e626d7f-4ef6-481b-9a12-c52210572692 with permissions b'\x01'.
2023-05-10 10:16:02.212 INFO (MainThread) [pyhap.accessory_driver] Unpairing client 2b0d4fe3-545a-4b39-817a-7935832455e3.
2023-05-10 10:16:04.986 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50148): Connection made to Home Assistant Bridge
2023-05-10 10:16:05.012 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50148): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:05.113 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50149): Connection made to Home Assistant Bridge
2023-05-10 10:16:05.132 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50149): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:10.957 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50150): Connection made to Home Assistant Bridge
2023-05-10 10:16:10.977 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50150): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:11.425 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50152): Connection made to Home Assistant Bridge
2023-05-10 10:16:11.444 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50152): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.

So I try to dig it and rerun step behind and I see this log (but I set debug mode on pyhap.hap_handler and not pyhap.accessory_driver

So I see :

2023-05-10 10:44:34.555 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '6', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:34.556 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [1/5]
2023-05-10 10:44:34.682 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '457', 'content-type': 'application/pairing+tlv8'}      
2023-05-10 10:44:34.683 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [2/5]
2023-05-10 10:44:34.777 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '159', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:34.778 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [3/5]
2023-05-10 10:44:34.781 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [4/5]
2023-05-10 10:44:34.785 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [5/5]
2023-05-10 10:44:34.789 DEBUG (MainThread) [pyhap.hap_handler] Finishing pairing with admin 2B0D4FE3-545A-4B39-817A-7935832455E3 uuid=2b0d4fe3-545a-4b39-817a-7935832455e3
2023-05-10 10:44:34.856 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '37', 'content-type': 'application/pairing+tlv8'}      
2023-05-10 10:44:34.856 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify [1/2].
2023-05-10 10:44:34.869 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '125', 'content-type': 'application/pairing+tlv8'}     
2023-05-10 10:44:34.869 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify [2/2]
2023-05-10 10:44:34.872 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify with client completed. Switching to encrypted transport.
2023-05-10 10:44:34.878 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request GET for path '/accessories': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local'}
2023-05-10 10:44:38.828 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '37', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:38.828 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify [1/2].
2023-05-10 10:44:38.859 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '125', 'content-type': 'application/pairing+tlv8'}     
2023-05-10 10:44:38.859 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify [2/2]
2023-05-10 10:44:38.862 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify with client completed. Switching to encrypted transport.
2023-05-10 10:44:38.895 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request GET for path '/accessories': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local'}
2023-05-10 10:44:39.316 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request PUT for path '/characteristics': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '59', 'content-type': 'application/hap+json'}

And after I don't see anymore 192.168.1.54 :/ Everything is up to date :)

I think HomePod force connect to Home Assistant Bridge and kill my Iphone connection but don't work properly after that ? 🤔

Do you need more log ? :) (I cannot found a way to make some test or modification on homeassistant OS)

Homepod firmware version 16.5, same issue

TempleZhou · 2023-06-03T08:16:05Z

I found the solution, related issue ikalchev/HAP-python#424,
I just upgrade the HAP-python version to 4.6.0 manually, then everything work fine ( with HomePod mini )

Hi

I have the same issue here. I use home assistant OS and it manage all smart thing (except the HomePod) in my home. I bought an HomePod mini (so it's also an home hub) (192.168.1.89). I use Apple only as a remote (to switch on and off the light with homekit), all automation are managed by HomeAssistant.

So, I make a homekit bridge via config file (because it's too long when I try to reproduce it to reconfigure anything).

I remove all config/.storage/homekit.* from storage. Remove bridge.
I restart HomeAssistant
I add bridge on Homekit on my Iphone (192.168.1.54) . That work almost every time
I restart HomeAssistant and bridge don't respond :(

I try another way :

Remove all config/.storage/homekit.* from storage. Remove bridge.
Reset homepod.
Add HomePod in new home
Add bridge in my home
Restart Homeassistant

It's work but some functionnality (like "what is humidity in bedroom") don't work :/

In log, I see some curious log

2023-05-10 10:15:54.506 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.54', 50752): Connection made to Home Assistant Bridge
2023-05-10 10:15:54.740 INFO (MainThread) [pyhap.accessory_driver] Paired with 2b0d4fe3-545a-4b39-817a-7935832455e3 with permissions b'\x01'.
2023-05-10 10:15:54.814 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.54', 50753): Connection made to Home Assistant Bridge
2023-05-10 10:15:58.343 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50147): Connection made to Home Assistant Bridge
2023-05-10 10:16:01.009 INFO (MainThread) [pyhap.accessory_driver] Paired with 7e626d7f-4ef6-481b-9a12-c52210572692 with permissions b'\x01'.
2023-05-10 10:16:02.212 INFO (MainThread) [pyhap.accessory_driver] Unpairing client 2b0d4fe3-545a-4b39-817a-7935832455e3.
2023-05-10 10:16:04.986 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50148): Connection made to Home Assistant Bridge
2023-05-10 10:16:05.012 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50148): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:05.113 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50149): Connection made to Home Assistant Bridge
2023-05-10 10:16:05.132 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50149): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:10.957 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50150): Connection made to Home Assistant Bridge
2023-05-10 10:16:10.977 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50150): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.
2023-05-10 10:16:11.425 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.89', 50152): Connection made to Home Assistant Bridge
2023-05-10 10:16:11.444 ERROR (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50152): Client 2b0d4fe3-545a-4b39-817a-7935832455e3 attempted pair verify without being paired to Home Assistant Bridge first.

So I try to dig it and rerun step behind and I see this log (but I set debug mode on pyhap.hap_handler and not pyhap.accessory_driver

So I see :

2023-05-10 10:44:34.555 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '6', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:34.556 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [1/5]
2023-05-10 10:44:34.682 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '457', 'content-type': 'application/pairing+tlv8'}      
2023-05-10 10:44:34.683 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [2/5]
2023-05-10 10:44:34.777 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Request POST for path '/pair-setup': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '159', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:34.778 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [3/5]
2023-05-10 10:44:34.781 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [4/5]
2023-05-10 10:44:34.785 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50787): Pairing [5/5]
2023-05-10 10:44:34.789 DEBUG (MainThread) [pyhap.hap_handler] Finishing pairing with admin 2B0D4FE3-545A-4B39-817A-7935832455E3 uuid=2b0d4fe3-545a-4b39-817a-7935832455e3
2023-05-10 10:44:34.856 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '37', 'content-type': 'application/pairing+tlv8'}      
2023-05-10 10:44:34.856 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify [1/2].
2023-05-10 10:44:34.869 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '125', 'content-type': 'application/pairing+tlv8'}     
2023-05-10 10:44:34.869 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify [2/2]
2023-05-10 10:44:34.872 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Pair verify with client completed. Switching to encrypted transport.
2023-05-10 10:44:34.878 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.54', 50788): Request GET for path '/accessories': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local'}
2023-05-10 10:44:38.828 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '37', 'content-type': 'application/pairing+tlv8'}
2023-05-10 10:44:38.828 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify [1/2].
2023-05-10 10:44:38.859 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request POST for path '/pair-verify': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '125', 'content-type': 'application/pairing+tlv8'}     
2023-05-10 10:44:38.859 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify [2/2]
2023-05-10 10:44:38.862 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Pair verify with client completed. Switching to encrypted transport.
2023-05-10 10:44:38.895 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request GET for path '/accessories': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local'}
2023-05-10 10:44:39.316 DEBUG (MainThread) [pyhap.hap_handler] ('192.168.1.89', 50170): Request PUT for path '/characteristics': {'host': 'Home\\032Assistant\\032Bridge\\032E8CE33._hap._tcp.local', 'content-length': '59', 'content-type': 'application/hap+json'}

And after I don't see anymore 192.168.1.54 :/ Everything is up to date :)

I think HomePod force connect to Home Assistant Bridge and kill my Iphone connection but don't work properly after that ? 🤔

Do you need more log ? :) (I cannot found a way to make some test or modification on homeassistant OS)

TempleZhou · 2023-06-03T08:21:42Z

pip install HAP-python==4.6.0

junweier · 2023-06-04T15:34:34Z

pip安装HAP-python==4.6.0

That's too cool. This problem has been bothering me for a long time, and I have to give up HomeKit now
If my homeassistant is running in the Docker of Raspberry Pi 4b, how do I upgrade HAP-python

Dryusdan · 2023-06-11T14:38:19Z

I check and the new homeassistant OS use the HAP-Python 4.6.0

I test this week :)

bdraco · 2023-06-11T15:10:12Z

You could install the latest HomeKit code as a custom component as well if you can’t upgrade hass

sammcj · 2023-06-26T00:00:59Z

HAP-Python 4.7.0 was released which seems to be what HA is using now, unfortunately pairing still seems to be broken.

bdraco · 2023-06-26T00:09:37Z

If you had a problem with pairing before, you might try deleting the bridge and making a new one

jordank195 · 2023-07-05T17:12:56Z

A workaround seems to be if I individually add each device in accessory mode. I took inspiration from Yoush's Scrypted, where only accessory mode works. As I only have a few devices, I'm okay with this as a workaround, but I know other users have >100's, so this might not be feasible.

bdraco · 2023-07-05T17:20:11Z

A workaround seems to be if I individually add each device in accessory mode. I took inspiration from Yoush's Scrypted, where only accessory mode works. As I only have a few devices, I'm okay with this as a workaround, but I know other users have >100's, so this might not be feasible.

If you can isolate which entity is causing the bridge to fail and post the raw state from the developer tools states panel we can probably make a workaround for that specific case.

dredjohn21 · 2023-08-08T22:05:57Z

@bdraco what is the best way to help log issues? From HA HomeKit Bridge screen enable “debug logging”? Or do I need to add any extra logging to configuration yaml?

This GitHub issue seems closest to my situation:
I’ve been using this integration for over a year with no issues, but recently (past month) we’ve noticed in the Home app all of our devices are showing as “no response”. I can solve the problem by either rebooting HAOS or reloading the HomeKit Bridge integration.

This seems similar to issues reported above so reluctant to add a new issue - but would like to contribute logs if helpful to confirm/clarify source of issue.

(I’m using latest version of HAOS and have AppleTV & HomePods at home; all on latest production release software)

bdraco · 2023-08-09T00:55:04Z

I’ve been using this integration for over a year with no issues, but recently (past month) we’ve noticed in the Home app all of our devices are showing as “no response”. I can solve the problem by either rebooting HAOS or reloading the HomeKit Bridge integration.

This seems similar to issues reported above so reluctant to add a new issue - but would like to contribute logs if helpful to confirm/clarify source of issue.

That sounds more like a network issue that a problem with a specific device.

When you reload it will force it to publish a new mdns entry. If your HomePods and Apple Tvs can't multicast to the HA instance, it won't see the DNS questions and never multicast new answers. As soon as the DNS records expire everything goes unavailable. By reloading you are forcing the mdns records to be published again.

dredjohn21 · 2023-08-09T22:49:36Z

I’ve been using this integration for over a year with no issues, but recently (past month) we’ve noticed in the Home app all of our devices are showing as “no response”. I can solve the problem by either rebooting HAOS or reloading the HomeKit Bridge integration.
This seems similar to issues reported above so reluctant to add a new issue - but would like to contribute logs if helpful to confirm/clarify source of issue.

That sounds more like a network issue that a problem with a specific device.

When you reload it will force it to publish a new mdns entry. If your HomePods and Apple Tvs can't multicast to the HA instance, it won't see the DNS questions and never multicast new answers. As soon as the DNS records expire everything goes unavailable. By reloading you are forcing the mdns records to be published again.

I think you were right. I rebooted all my Linksys Velop nodes and haven’t had an issue since yesterday.

Curious: do you know anyway to monitor for this via home assistant so I can trigger a reboot of my router? (I know how to reboot but not what to look for as a trigger with multicast problems, or if that comes through to HAOS)

issue-triage-workflows · 2023-11-07T23:10:40Z

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.

Dryusdan · 2023-11-09T13:09:53Z

I solve the issue for me. I update to the latest version of HomeAssistant. I nuke my entirely home Homekit with the profile share by @jay7210 and recreate it and it's work fine !

Thank for all :)

issue-triage-workflows · 2024-02-07T15:07:31Z

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.

home-assistant bot added the integration: homekit label Dec 21, 2022

home-assistant bot assigned bdraco Dec 21, 2022

Mariusthvdb mentioned this issue Jun 4, 2023

Somfy Homekit controller connection lost #93891

Closed

issue-triage-workflows bot added the stale label Nov 7, 2023

issue-triage-workflows bot removed the stale label Nov 9, 2023

issue-triage-workflows bot added the stale label Feb 7, 2024

issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 14, 2024

github-actions bot locked and limited conversation to collaborators Mar 15, 2024

HomeKit integration devices unresponsive #84387

HomeKit integration devices unresponsive #84387

Comments

brsnik commented Dec 21, 2022 • edited Loading

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

home-assistant bot commented Dec 21, 2022

Nbr1Sniper commented Dec 24, 2022

gaoyixiang commented Dec 25, 2022

andersovreseth commented Jan 1, 2023

andersovreseth commented Jan 1, 2023

Nbr1Sniper commented Jan 1, 2023 via email

miquellaboria commented Jan 7, 2023

shuiguojiao commented Jan 9, 2023

kylecwhite commented Jan 9, 2023

andersovreseth commented Jan 9, 2023

kevin7s-io commented Jan 9, 2023

qis90 commented Jan 26, 2023

bdraco commented Jan 26, 2023

brsnik commented Jan 27, 2023

joshbish commented Jan 30, 2023

brsnik commented Jan 30, 2023

RoyHP commented Apr 23, 2023

RoyHP commented Apr 23, 2023 • edited Loading

bdraco commented Apr 25, 2023

RoyHP commented Apr 27, 2023

bdraco commented Apr 27, 2023 • edited Loading

foru17 commented May 3, 2023

RoyHP commented May 3, 2023

Dryusdan commented May 10, 2023

ouchkilljoys commented May 17, 2023

junweier commented May 28, 2023

jay7210 commented May 28, 2023

TempleZhou commented Jun 3, 2023

TempleZhou commented Jun 3, 2023

TempleZhou commented Jun 3, 2023

junweier commented Jun 4, 2023 • edited Loading

Dryusdan commented Jun 11, 2023

bdraco commented Jun 11, 2023

sammcj commented Jun 26, 2023

bdraco commented Jun 26, 2023

jordank195 commented Jul 5, 2023

bdraco commented Jul 5, 2023

dredjohn21 commented Aug 8, 2023

bdraco commented Aug 9, 2023 • edited Loading

dredjohn21 commented Aug 9, 2023

issue-triage-workflows bot commented Nov 7, 2023

Dryusdan commented Nov 9, 2023

issue-triage-workflows bot commented Feb 7, 2024

brsnik commented Dec 21, 2022 •

edited

Loading

RoyHP commented Apr 23, 2023 •

edited

Loading

bdraco commented Apr 27, 2023 •

edited

Loading

junweier commented Jun 4, 2023 •

edited

Loading

bdraco commented Aug 9, 2023 •

edited

Loading