search

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
71.13k stars 29.8k forks source link

Homekit "No Response" most of the time #45461

Closed RemcoMusic closed 3 years ago

RemcoMusic commented 3 years ago

The problem

I'm trying to get the Homekit integration to work. I'm feeling like I have tried everything. First I had the Home Assistant Supervised OS installed on my Raspberry Pi 3B+. On that device Homekit worked for some little times but most of the time it also gave a "no response" in the Home app. I have tried everything on that RPI. Than I tried to switch to my home lab. This is a Centos 8 server with Oracle Virtual Machine running Home Assistant Supervised OS with the network adapter bridged. Every other device is working properly and automatically gets discovered by Home Assistant no problem! But with the Homekit intergration on my Iphone 11 -> IOS 14.3 and Ipad Air -> IOS 12.5.1 I get the "No Response" on every light and cover. Sometime it works but for the most time it is not for long and than the "No response" comes back. Read the Additional information for all the post and forum stuff I tried.

Environment

System Health

version 2021.1.4
installation_type Home Assistant OS
dev false
hassio true
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 5.4.86
arch x86_64
timezone Europe/Amsterdam
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Hass.io host_os | Home Assistant OS 5.10 -- | -- update_channel | stable supervisor_version | 2021.01.5 docker_version | 19.03.13 disk_total | 30.8 GB disk_used | 3.2 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Duck DNS (1.12.4), File editor (5.2.0), Mosquitto broker (5.1), Terminal & SSH (8.10.0)
Lovelace dashboards | 1 -- | -- mode | storage views | 2 resources | 0

Problem-relevant configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# SSL Certificaten
http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

notify:
  - name: family
    platform: group
    services:
      - service: mobile_app_remco

logger:
  default: warning
  logs:
    homeassistant.components.homekit: debug
    pyhap: debug

Traceback/Error logs

2021-01-23 13:38:09 DEBUG (MainThread) [homeassistant.components.homekit] Begin setup HomeKit for HASS Bridge VXG6
2021-01-23 13:38:12 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 5 seconds
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Name to HASS Bridge VXG6
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to default
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: FirmwareRevision to 2021.1.4
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Manufacturer to Home Assistant
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Model to Bridge
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to homekit.bridge
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [homeassistant.components.homekit.accessories] Add "switch.sonoff" as "Switch"
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Name to SL-Remco-Main
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to default
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: FirmwareRevision to 9.2.0
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Manufacturer to Tasmota
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Model to Sonoff T1 1CH
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to switch.sonoff
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [homeassistant.components.homekit.accessories] Add "switch.sonoff_2" as "Switch"
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Name to Entertainment-Wall
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to default
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: FirmwareRevision to 9.2.0
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Manufacturer to Tasmota
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Model to Sonoff Basic
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to switch.sonoff_2
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [homeassistant.components.homekit.type_switches] switch.sonoff_2: Set current state to True
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: On to True
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [homeassistant.components.homekit.accessories] Add "light.shellydimmer2_e098069509cb" as "Light"
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Name to Woonkamer-licht-1
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to default
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: FirmwareRevision to 20201007.085431
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Manufacturer to Shelly
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Model to Shelly Dimmer 2
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: SerialNumber to light.shellydimmer2_e098069509cb
2021-01-23 13:38:12 DEBUG (SyncWorker_4) [pyhap.characteristic] set_value: Brightness to 100
2021-01-23 13:38:12 INFO (SyncWorker_4) [pyhap.accessory_driver] Loading Accessory state from `/config/.storage/homekit.0fffc829626e635d4f9b465ed0de09c3.state`
2021-01-23 13:38:12 DEBUG (MainThread) [homeassistant.components.homekit] Driver start for HASS Bridge VXG6
2021-01-23 13:38:12 INFO (SyncWorker_2) [pyhap.accessory_driver] Starting accessory HASS Bridge VXG6 on address 192.168.1.100, port 51828.
2021-01-23 13:38:12 DEBUG (SyncWorker_2) [pyhap.accessory_driver] Starting event thread.
2021-01-23 13:38:12 DEBUG (SyncWorker_2) [pyhap.accessory_driver] Starting server.
2021-01-23 13:38:12 DEBUG (SyncWorker_2) [pyhap.accessory_driver] Starting mDNS.
2021-01-23 13:38:13 INFO (Thread-8) [pyhap.hap_server] Got connection with ('192.168.1.158', 49247).
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.hap_server] Request POST from address '('192.168.1.158', 49247)' for path '/pair-verify'.
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.hap_server] Pair verify [1/2].
2021-01-23 13:38:13 INFO (Thread-9) [pyhap.hap_server] 192.168.1.158 - "POST /pair-verify HTTP/1.1" 200 -
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.hap_server] Request POST from address '('192.168.1.158', 49247)' for path '/pair-verify'.
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.hap_server] Pair verify [2/2]
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.hap_server] Pair verify with client '('192.168.1.158', 49247)' completed. Switching to encrypted transport.
2021-01-23 13:38:13 INFO (Thread-9) [pyhap.hap_server] 192.168.1.158 - "POST /pair-verify HTTP/1.1" 200 -
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.hap_server] Request GET from address '('192.168.1.158', 49247)' for path '/accessories'.
2021-01-23 13:38:13 DEBUG (Thread-9) [pyhap.accessory_driver] Get accessories response: [{'aid': 1, 'services': [{'iid': 1, 'type': '0000003E-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 2, 'type': '00000014-0000-1000-8000-0026BB765291', 'description': 'Identify', 'perms': ['pw'], 'format': 'bool'}, {'iid': 3, 'type': '00000020-0000-1000-8000-0026BB765291', 'description': 'Manufacturer', 'perms': ['pr'], 'format': 'string', 'value': 'Home Assistant'}, {'iid': 4, 'type': '00000021-0000-1000-8000-0026BB765291', 'description': 'Model', 'perms': ['pr'], 'format': 'string', 'value': 'Bridge'}, {'iid': 5, 'type': '00000023-0000-1000-8000-0026BB765291', 'description': 'Name', 'perms': ['pr'], 'format': 'string', 'value': 'HASS Bridge VXG6'}, {'iid': 6, 'type': '00000030-0000-1000-8000-0026BB765291', 'description': 'SerialNumber', 'perms': ['pr'], 'format': 'string', 'value': 'homekit.bridge'}, {'iid': 7, 'type': '00000052-0000-1000-8000-0026BB765291', 'description': 'FirmwareRevision', 'perms': ['pr'], 'format': 'string', 'value': '2021.1.4'}]}]}, {'aid': 962901275, 'services': [{'iid': 1, 'type': '0000003E-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 2, 'type': '00000014-0000-1000-8000-0026BB765291', 'description': 'Identify', 'perms': ['pw'], 'format': 'bool'}, {'iid': 3, 'type': '00000020-0000-1000-8000-0026BB765291', 'description': 'Manufacturer', 'perms': ['pr'], 'format': 'string', 'value': 'Tasmota'}, {'iid': 4, 'type': '00000021-0000-1000-8000-0026BB765291', 'description': 'Model', 'perms': ['pr'], 'format': 'string', 'value': 'Sonoff T1 1CH'}, {'iid': 5, 'type': '00000023-0000-1000-8000-0026BB765291', 'description': 'Name', 'perms': ['pr'], 'format': 'string', 'value': 'SL-Remco-Main'}, {'iid': 6, 'type': '00000030-0000-1000-8000-0026BB765291', 'description': 'SerialNumber', 'perms': ['pr'], 'format': 'string', 'value': 'switch.sonoff'}, {'iid': 7, 'type': '00000052-0000-1000-8000-0026BB765291', 'description': 'FirmwareRevision', 'perms': ['pr'], 'format': 'string', 'value': '9.2.0'}]}, {'iid': 8, 'type': '00000049-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 9, 'type': '00000025-0000-1000-8000-0026BB765291', 'description': 'On', 'perms': ['pr', 'pw', 'ev'], 'format': 'bool', 'value': False}]}]}, {'aid': 431735541, 'services': [{'iid': 1, 'type': '0000003E-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 2, 'type': '00000014-0000-1000-8000-0026BB765291', 'description': 'Identify', 'perms': ['pw'], 'format': 'bool'}, {'iid': 3, 'type': '00000020-0000-1000-8000-0026BB765291', 'description': 'Manufacturer', 'perms': ['pr'], 'format': 'string', 'value': 'Tasmota'}, {'iid': 4, 'type': '00000021-0000-1000-8000-0026BB765291', 'description': 'Model', 'perms': ['pr'], 'format': 'string', 'value': 'Sonoff Basic'}, {'iid': 5, 'type': '00000023-0000-1000-8000-0026BB765291', 'description': 'Name', 'perms': ['pr'], 'format': 'string', 'value': 'Entertainment-Wall'}, {'iid': 6, 'type': '00000030-0000-1000-8000-0026BB765291', 'description': 'SerialNumber', 'perms': ['pr'], 'format': 'string', 'value': 'switch.sonoff_2'}, {'iid': 7, 'type': '00000052-0000-1000-8000-0026BB765291', 'description': 'FirmwareRevision', 'perms': ['pr'], 'format': 'string', 'value': '9.2.0'}]}, {'iid': 8, 'type': '00000049-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 9, 'type': '00000025-0000-1000-8000-0026BB765291', 'description': 'On', 'perms': ['pr', 'pw', 'ev'], 'format': 'bool', 'value': True}]}]}, {'aid': 4258732156, 'services': [{'iid': 1, 'type': '0000003E-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 2, 'type': '00000014-0000-1000-8000-0026BB765291', 'description': 'Identify', 'perms': ['pw'], 'format': 'bool'}, {'iid': 3, 'type': '00000020-0000-1000-8000-0026BB765291', 'description': 'Manufacturer', 'perms': ['pr'], 'format': 'string', 'value': 'Shelly'}, {'iid': 4, 'type': '00000021-0000-1000-8000-0026BB765291', 'description': 'Model', 'perms': ['pr'], 'format': 'string', 'value': 'Shelly Dimmer 2'}, {'iid': 5, 'type': '00000023-0000-1000-8000-0026BB765291', 'description': 'Name', 'perms': ['pr'], 'format': 'string', 'value': 'Woonkamer-licht-1'}, {'iid': 6, 'type': '00000030-0000-1000-8000-0026BB765291', 'description': 'SerialNumber', 'perms': ['pr'], 'format': 'string', 'value': 'light.shellydimmer2_e098069509cb'}, {'iid': 7, 'type': '00000052-0000-1000-8000-0026BB765291', 'description': 'FirmwareRevision', 'perms': ['pr'], 'format': 'string', 'value': '20201007.085431'}]}, {'iid': 8, 'type': '00000043-0000-1000-8000-0026BB765291', 'characteristics': [{'iid': 9, 'type': '00000025-0000-1000-8000-0026BB765291', 'description': 'On', 'perms': ['pr', 'pw', 'ev'], 'format': 'bool', 'value': False}, {'iid': 10, 'type': '00000008-0000-1000-8000-0026BB765291', 'description': 'Brightness', 'perms': ['pr', 'pw', 'ev'], 'format': 'int', 'minStep': 1, 'unit': 'percentage', 'minValue': 0, 'maxValue': 100, 'value': 100}]}]}]
2021-01-23 13:38:13 INFO (Thread-9) [pyhap.hap_server] 192.168.1.158 - "GET /accessories HTTP/1.1" 200 -
2021-01-23 13:38:13 DEBUG (SyncWorker_2) [pyhap.accessory_driver] Starting accessory.
2021-01-23 13:38:13 DEBUG (SyncWorker_2) [pyhap.accessory_driver] AccessoryDriver started successfully
2021-01-23 13:38:13 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state switch.sonoff=off; friendly_name=SL-Remco-Main @ 2021-01-23T13:38:09.886208+01:00>
2021-01-23 13:38:13 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state switch.sonoff_2=on; friendly_name=Entertainment-Wall @ 2021-01-23T13:38:10.989913+01:00>
2021-01-23 13:38:13 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state light.shellydimmer2_e098069509cb=off; friendly_name=Woonkamer-licht-1, supported_features=1 @ 2021-01-23T13:38:12.671309+01:00>

Additional information

I have a Ubiquiti ecosystem. Unifi controller version: 6.0.43 The several posts I have already read and tried are the following:

probot-home-assistant[bot] commented 3 years ago

homekit documentation homekit source (message by IssueLinks)

probot-home-assistant[bot] commented 3 years ago

Hey there @bdraco, mind taking a look at this issue as its been labeled with an integration (homekit) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)

bdraco commented 3 years ago

Which firmware version do you have on your unifi access points?

Are you running the buggy 4.3.24.11355 firmware?

RemcoMusic commented 3 years ago

Which firmware version do you have on your unifi access points?

Are you running the buggy 4.3.24.11355 firmware?

4.3.24.11355 indeed

bdraco commented 3 years ago

Upgrade to 4.3.26.11358

https://community.ui.com/releases/UAP-Firmware-4-3-26-11358/e05cd041-ea54-460c-85f4-7f3fd97261e8

Bugfixes [UAP-G2] Fix intermittent broadcast and multicast packet drop on gen2 APs, introduced in 4.3.24. This impacted users with non-UniFi DHCP servers which use broadcast for DHCP, along with IoT devices that rely on multicast for discovery.

RemcoMusic commented 3 years ago

Upgrade to 4.3.26.11358

https://community.ui.com/releases/UAP-Firmware-4-3-26-11358/e05cd041-ea54-460c-85f4-7f3fd97261e8

Bugfixes [UAP-G2] Fix intermittent broadcast and multicast packet drop on gen2 APs, introduced in 4.3.24. This impacted users with non-UniFi DHCP servers which use broadcast for DHCP, along with IoT devices that rely on multicast for discovery.

I have upgraded to that new version. I have response now from the devices. But I can't yet tell if the problem is completely fixed since it sometimes worked and than it didn't work again. Let me get back to this after one day? But it does looks promising. Thanks for the fast help!

PierreScerri commented 3 years ago

I do not have Ubiquiti and I also have the same issue. It seems that the homekit link between HA and the Home.app tends to break (especially after a restart). I get random notifications in HA with the QR code as if it is being setup for the first time. Wifi Access is via a Grandstream 7610 AP connected to my router (Sagemcom Hybrid 5370 Air).

RemcoMusic commented 3 years ago

Upgrade to 4.3.26.11358

https://community.ui.com/releases/UAP-Firmware-4-3-26-11358/e05cd041-ea54-460c-85f4-7f3fd97261e8

Bugfixes [UAP-G2] Fix intermittent broadcast and multicast packet drop on gen2 APs, introduced in 4.3.24. This impacted users with non-UniFi DHCP servers which use broadcast for DHCP, along with IoT devices that rely on multicast for discovery.

It seems to be a little bit better. Sometimes still the "No Response" messages comes up with all the devices but a little bit less than before. Is there a way to debug this?

bdraco commented 3 years ago

Do you have bridged camera?

RemcoMusic commented 3 years ago

Do you have bridged camera?

I don't have any connected camera's to my home network

bdraco commented 3 years ago

Do you have any tv media players on the bridge?

RemcoMusic commented 3 years ago

Do you have any tv media players on the bridge?

No, sorry that I didn't include this in my original post.

I have tested several cases with only the demo thing turned on. Than added one light. Than I removed everything again and tried it with only 1 cover etc.. But it all had the same result.

RemcoMusic commented 3 years ago

@bdraco Several days have been past tried again different things:

  1. I had an enterprise level LoRaWAN installation running on my network for work. I thought maybe that could interfere. But now that I have disconnected the setup it made no difference.
  2. I have tried to play with the mDNS and Multicast Enchanment option on my unifi controller again no difference. (could you maybe give a definitive conclusion on which setting to put on or off?)
  3. Tried updating the unifi controller to version: atag_6.0.45_14358 made no difference

I'm still curious to find the problem since I have been searching for weeks now. Do you have a way to debug even further?

bdraco commented 3 years ago

Can you try a dev build with https://github.com/home-assistant/core/pull/45731 ?

RemcoMusic commented 3 years ago

Can you try a dev build with https://github.com/home-assistant/core/pull/45731 ?

I'm running on the Home Assistant OS if I join the beta channel is that good enough?

Because I don't see a way to upgrade to the dev branch on the Home Assistant OS

bdraco commented 3 years ago

Take a snapshot and then change the channel ha supervisor options --channel dev

You may need to wait until tomorrow for the new code to be available in a dev build.

cbb09 commented 3 years ago

@bdraco Several days have been past tried again different things:

  1. I had an enterprise level LoRaWAN installation running on my network for work. I thought maybe that could interfere. But now that I have disconnected the setup it made no difference.
  2. I have tried to play with the mDNS and Multicast Enchanment option on my unifi controller again no difference. (could you maybe give a definitive conclusion on which setting to put on or off?)
  3. Tried updating the unifi controller to version: atag_6.0.45_14358 made no difference

I'm still curious to find the problem since I have been searching for weeks now. Do you have a way to debug even further?

I’ve had the exact same issue. I don’t believe it’s home assistant. The only thing that solved the problem for me was to downgrade the UniFi controller to 5.14.25. The APs run 4.3.21, but they may be ok with .26 as well. I haven’t tried that yet. What threw me off was that it was the controller and not the AP firmware that causes the issue. Not sure what exactly is happening though...

RemcoMusic commented 3 years ago

@bdraco Several days have been past tried again different things:

  1. I had an enterprise level LoRaWAN installation running on my network for work. I thought maybe that could interfere. But now that I have disconnected the setup it made no difference.
  2. I have tried to play with the mDNS and Multicast Enchanment option on my unifi controller again no difference. (could you maybe give a definitive conclusion on which setting to put on or off?)
  3. Tried updating the unifi controller to version: atag_6.0.45_14358 made no difference

I'm still curious to find the problem since I have been searching for weeks now. Do you have a way to debug even further?

I’ve had the exact same issue. I don’t believe it’s home assistant. The only thing that solved the problem for me was to downgrade the UniFi controller to 5.14.25. The APs run 4.3.21, but they may be ok with .26 as well. I haven’t tried that yet. What threw me off was that it was the controller and not the AP firmware that causes the issue. Not sure what exactly is happening though...

I surely believe that. The upgrade to the 6.0.x of the controller didn't brought a lot of good things. But I want to know what the problem is and maybe it is possible to fix it with Home Assistant.

If the solution of @bdraco doesn't work I'm going to try to downgrade the controller.

bdraco commented 3 years ago

5.43.23.12533 on the the switchs and aps and its working rock solid for me

RemcoMusic commented 3 years ago

5.43.23.12533 on the the switchs and aps and its working rock solid for me

With your new release?

bdraco commented 3 years ago

Before and after the new release it was solid. Its just much faster with the new release

RemcoMusic commented 3 years ago

Before and after the new release it was solid. Its just much faster with the new release

Hmm I can't get my AP's to the version you mentioned, But lets hope. Your fix wasn't in the tag of today correct?

bdraco commented 3 years ago

Changes should be in the latest dev image https://hub.docker.com/layers/homeassistant/home-assistant/dev/images/sha256-9e739e49936dda65960e2f39271fedc3ca10e85ec1acfa6cdd9ae203c834d03e?context=explore

RemcoMusic commented 3 years ago

Changes should be in the latest dev image https://hub.docker.com/layers/homeassistant/home-assistant/dev/images/sha256-9e739e49936dda65960e2f39271fedc3ca10e85ec1acfa6cdd9ae203c834d03e?context=explore

I'm currently installing. Lets see what happens

RemcoMusic commented 3 years ago

Changes should be in the latest dev image https://hub.docker.com/layers/homeassistant/home-assistant/dev/images/sha256-9e739e49936dda65960e2f39271fedc3ca10e85ec1acfa6cdd9ae203c834d03e?context=explore

Still No Response.. Just to summarize which versions of everything I'm running see below:

System Health

version core-2021.3.0.dev20210202
installation_type Home Assistant OS
dev true
hassio true
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 5.4.94
arch x86_64
timezone Europe/Amsterdam
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 5.11 -- | -- update_channel | dev supervisor_version | supervisor-2021.02.dev0203 docker_version | 19.03.13 disk_total | 30.8 GB disk_used | 3.9 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Duck DNS (1.12.4), File editor (5.2.0), Mosquitto broker (5.1), Terminal & SSH (8.10.0)
Lovelace dashboards | 1 -- | -- resources | 0 views | 2 mode | storage

Unifi controller: 6.0.45 (Build: atag_6.0.45_14358) Unifi UAP-AC-Lite: 4.3.26.11358 Unifi UAP-AC-LR: 4.3.26.11358 2x Unifi US-8-60W: 5.43.23.12533 USG Version: 4.4.52.5363511 mDNS: Enabled Multicast Enhancement: Disabled

bdraco commented 3 years ago

Do you have any of these turned on?

Screen Shot 2021-02-02 at 7 52 36 AM
cbb09 commented 3 years ago

5.43.23.12533 on the the switchs and aps and its working rock solid for me

are you running nano APs or similar? I have both AP AC Pros (latest firmware is 4.3.26 (release candidate)) and nano HDs on 5.43.23. The issue is most pronounced with the AC Pros, less so with the nano. In my case it's not only homekit that's acting up, but I noticed some minor glitchiness with some other wifi devices that rely on broadcasts. They disappear completely with the downgrade. Also, are you running all unifi hardware (e.g. router etc.)? Based on comments gathered in other forums, there may be some correlation to not having a unifi router. In my case, I run OPNsense as my firewall/router.

cbb09 commented 3 years ago

Do you have any of these turned on?

Screen Shot 2021-02-02 at 7 52 36 AM

in my case, I've tried all combinations of settings, incl. all OFF (which I think is default) to no avail.

RemcoMusic commented 3 years ago

Do you have any of these turned on?

Screen Shot 2021-02-02 at 7 52 36 AM

I do have High Performance Devices turned ON the rest is OFF

RemcoMusic commented 3 years ago

5.43.23.12533 on the the switchs and aps and its working rock solid for me

are you running nano APs or similar? I have both AP AC Pros (latest firmware is 4.3.26 (release candidate)) and nano HDs on 5.43.23. The issue is most pronounced with the AC Pros, less so with the nano. In my case it's not only homekit that's acting up, but I noticed some minor glitchiness with some other wifi devices that rely on broadcasts. They disappear completely with the downgrade. Also, are you running all unifi hardware (e.g. router etc.)? Based on comments gathered in other forums, there may be some correlation to not having a unifi router. In my case, I run OPNsense as my firewall/router.

I have all unifi hardware. Except the controller is running on a centos home server.

short4bmoney commented 3 years ago

Similar issue here; no Unifi APs, though I am running my Wyze cam (HACS) and several other OpenZwave entities to Homekit.

What's odd is manually triggering the homekit.reload or homekit.start services will seem to reset everything back to normal. Only a couple minutes go by and then my OZW devices are all no-response again.

System Health

version 2021.1.5
installation_type Home Assistant OS
dev false
hassio true
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 5.4.79-v8
arch aarch64
timezone America/Los_Angeles
Home Assistant Community Store GitHub API | ok -- | -- Github API Calls Remaining | 5000 Installed Version | 1.10.1 Stage | running Available Repositories | 711 Installed Repositories | 4
Hass.io host_os | Home Assistant OS 5.10 -- | -- update_channel | stable supervisor_version | 2021.01.7 docker_version | 19.03.13 disk_total | 13.9 GB disk_used | 10.2 GB healthy | true supported | true board | rpi3-64 supervisor_api | ok version_api | ok installed_addons | Grafana (6.0.0), Samba share (9.3.0), Terminal & SSH (8.10.0), Google Assistant SDK (2.5.0), Plex Media Server (2.4.1), Duck DNS (1.12.4), Visual Studio Code (2.9.1), File editor (5.2.0), Mosquitto broker (5.1), OpenZWave (0.9.0), NGINX Home Assistant SSL proxy (3.0.1), Let's Encrypt (4.11.0), Node-RED (7.2.8), ESPHome (1.15.3), Assistant Relay (0.7.4), Z-Wave Network Viewer (0.4)
Lovelace dashboards | 1 -- | -- mode | storage views | 5 resources | 1

Configuration.yaml

homekit:
  name: Cabrillo Bay Bridge
  auto_start: false
  port: 51192
  filter:
    include_entities:
      - switch.lzw30_switch_switch
      - light.lzw31_dimmer_level
      - light.living_room_rgb
      - light.living_room_white_strip
      - lock.schlage_connect_smart_deadbolt_locked
      - camera.living_room
      - camera.garage_camera
  entity_config:
    lock.schlage_connect_smart_deadbolt_locked:
      code: #### #redacted
bdraco commented 3 years ago

Make a separate instance for each camera in accessory mode. If the camera snapshot is slow in any way everything will stall until it completes. By making it its own instance it can't block other accessories.

https://www.home-assistant.io/integrations/homekit/#accessory-mode

RemcoMusic commented 3 years ago

@bdraco I have some good news! Since I have updated my Home Assistant to:

System Health

version core-2021.3.0.dev20210203
installation_type Home Assistant OS
dev true
hassio true
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 5.4.94
arch x86_64
timezone Europe/Amsterdam
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 5.11 -- | -- update_channel | dev supervisor_version | supervisor-2021.02.dev0304 docker_version | 19.03.13 disk_total | 30.8 GB disk_used | 2.9 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Duck DNS (1.12.4), File editor (5.2.0), Mosquitto broker (5.1), Terminal & SSH (8.10.0)
Lovelace dashboards | 1 -- | -- resources | 0 views | 2 mode | storage

It started to work again!! I'm really happy. I don't know if you can find out what it was? Because I really would like to know.

Another question do you know when this build will get into the stable version of Home Assistant?

At last thanks for the support!

bdraco commented 3 years ago

The new version will be out March 3rd