Closed RemcoMusic closed 3 years ago
homekit documentation homekit source (message by IssueLinks)
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)
Which firmware version do you have on your unifi access points?
Are you running the buggy 4.3.24.11355 firmware?
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
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.
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!
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).
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?
Do you have bridged camera?
Do you have bridged camera?
I don't have any connected camera's to my home network
Do you have any tv media players on the bridge?
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.
@bdraco Several days have been past tried again different things:
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?
Can you try a dev build with https://github.com/home-assistant/core/pull/45731 ?
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
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.
@bdraco Several days have been past tried again different things:
- 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.
- 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?)
- 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...
@bdraco Several days have been past tried again different things:
- 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.
- 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?)
- 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.
5.43.23.12533
on the the switchs and aps and its working rock solid for me
5.43.23.12533
on the the switchs and aps and its working rock solid for me
With your new release?
Before and after the new release it was solid. Its just much faster with the new release
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?
Changes should be in the latest dev image https://hub.docker.com/layers/homeassistant/home-assistant/dev/images/sha256-9e739e49936dda65960e2f39271fedc3ca10e85ec1acfa6cdd9ae203c834d03e?context=explore
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
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:
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 |
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
Do you have any of these turned on?
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.
Do you have any of these turned on?
![]()
in my case, I've tried all combinations of settings, incl. all OFF (which I think is default) to no avail.
Do you have any of these turned on?
![]()
I do have High Performance Devices turned ON the rest is OFF
5.43.23.12533
on the the switchs and aps and its working rock solid for meare 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.
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.
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 |
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
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
@bdraco I have some good news! Since I have updated my Home Assistant to:
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 |
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!
The new version will be out March 3rd
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
Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHass.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 | 0Problem-relevant
configuration.yaml
Traceback/Error logs
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: