Homekit mdns not working. I have (at least) 3 VLANs/WLANs.

Homekit mdns not working all other bridges allowed me to readd them no problem. Try switching the mDNS advertiser used in the HomeKit plugin settings. Despite the HomeKit errors, direct communication with the devices via their proprietary app was flawless. 20 and voila everything started working again perfectly. They work fine most of the time aside from the occasional “not responding”. 4GHz and 5GHz bands. Native homekit things like door sensors work fine - all the time. HomeKit isn’t working for the majorly of my devices. Devices that connect to C can use HomeKit devices, but not AirPrint. However, I think you have to add network_mode: I’ve heard good things about Meross (and I have one of their smart lamps that I’ve had zero issues with in the last year) but these plugs do not work. 2 Likes. mDNS repeater working fine on the USG. I can get the app up and running with no problem with my old back up and with a new setup, however I can’t get anything to add to HomeKit. I had them on 5GHz, now switched to 2. 6. Some talk about Docker containers, custom mDNS repeaters, etc. Homebridge cannot respond to the incoming verification Homekit request Connect HomeKit Device without mDNS . Netgear Orbi Routers Are Not Natively Compatible With Homekit The camera was connected via HomeKit in HA, I unpair it In the web interface of the integration, I paired the detected camera (g4), it became visible in the list When I click on the stream, I get a black screen, when I click on "probe" I container is not allowed to advertise its own HAP mDNS record to the host. I looked at when the most recent firmware upgrade was (which was 8/11/21 in my case) and noticed two separate firmware upgrades released on the same day for my router (a usual no-no). Due to the complex nature of this, it is a crosspost with r/Ubiquity - NoT is VLAN 40, NoT wifi - kids is VLAN 50, kids wifi (This is all provisional, open to suggestions if people have them. I actually kill my power at the breaker, start up my internet/router once that is up, I start all my HomeKit items. HomeKit works fine across vlans given you have it correctly configured. I use a Starling Home Hub as a HomeKit bridge for some Nest devices that aren't (yet?) supported, such as door, alarm, and temperature sensors. one day everything stopped connecting and i had to reinstall homebridge and get it back up but the removal of the previous bridge was the last time it was part of homekit. My Homekit server port, mDNS, and mDNS interfaces are all default values. This can be a product issue (restarting the device helps), a hub issue (restarting the home hub helps), or a networking equipment problem. Do you know if this will let homekit work across VLANs? natedub; Newbie; Posts 2; Logged; Re: Guide to mDNS/Apple Bonjour with I´m unable to get my ER605 to work with my Apple Homekit devices. mDNS is working. An Apple TV is the homekit hub. Tried all the solutions from above and Homekit not working with docker · Issue #15692 · home-assistant/core · GitHub but could not get it working. In gratitude, i detailed the changes for those users who are somewhat noobs with the console I edited: I have had similar issues and while I can’t explain it, a simple reboot of everything will not work. I’m not saying HomeKit is never at fault but the odds say it’s usually your network. The mDNS relay in the firewall only comes into play when the traffic needs to traverse VLANs. 04 avahi-daemon running on the k8s node with mDNS reflection enabled Navigation Menu Toggle navigation. yaml and added lines The mDNS can be made working should used avahi reflectors in the configuration. remote still works. 10 about 2 months ago homebridge was working on bluefin with the docker create app button in the ui. If you open that add. Note that for mdns, udpbroadcastrelay should not have a 'source address' set: leave it blank. michaeldavie (Michaeldavie this does not work i dont know how mDNS exactly communicates. I have (3) Zooz switches on the hub so far. Let’s call them A, B, and C. It’s most commonly implemented as Bonjour (Apple) and Hi, today I started my journey for the update of my v3 instance to v4. Unfortunately the mDNS seems to stop working too and homekit can’t see the homekit controls for that device either. Homekit accessories work fine just the cameras part of the homekit are acting up on ER605. 21 and it still While I have an IT and networking background, I am not a network engineer. homekit binding. I have to disable mDNS service, save and reenable mDNS. I have appletv in same room right next to 1 set and the1 of the 3 lost homekit connection today. mDNS is not working. All items has no response so I deleted the bridge from my Home App. All appear to be working correctly in the Hubitat hub. @home-assistant close Closes the issue. A quick Google revealed a thread here in which Zyxel responded that this AP doesn't support mDNS, I´m unable to get my ER605 to work with my Apple Homekit devices. Sign in I added the following container to my docker-compose. mDNS tells home app that openHAB exists and which IP address and port it has; home app cannot access Then, I discovered that this seems to be a longstanding problem with mDNS not working properly on the UDM identified at least 10 months ago. My Apple TV is my hub. So far, mDNS service has been supported on ER8411 V1 1. homekit (mDNS) problem over several APs This thread has been viewed 70 times Petronie Mar 30, But seems that solution is pretty simple - is enough just to disable all airgroup options and then it works! Homekit is working from all APs without issue. Running openHAB 3. 5. 2. They’re so simple to set up and they work for a little. The Pi has static IP, GW and DNS in the IOT VLAN Before moving to 24. It sounds like mDNS got hosed. Closed 1 of 2 tasks. But 12-24 hours after they work, they just randomly stop responding in the Home app. It is designed to be a local protocol. 2. 2 inside a docker container). _tcp. No matter what I try, I end up with “Accessory Not Found”. But I feat that I’ll lose the 6 months of work that I spent getting my automations configured if I do that. Ideas? Update 1: I tried rebooting router and access point. I have downgraded to my v3 Don't go crazy with UPNP, IGMP snooping or any feature you couldn't describe on a whiteboard yourself how it works. json mDNS service is turned off in the UI IGMP-Proxy enabled on the USG Firewall rules to allow Established/Related data FROM IoT TO Private VLAN mDNS Port (5353) open to the IoT VLAN I have a decent Homekit setup in my home along with Homebridge 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. I can confirm the host name and service name don’t matter so you can choose any. I am running with --net=host. i would google something like “docker blocks broadcast” Homekit isn't expected to work across vlans. HomeKit obviously - Run a mDNS debug tool on that VLAN - See what it sees. Of course this was after I ordered a replacement. Also, truly just want the iPad to be able to see the mDNS zone of the home network, don’t want to fully connect the local mDNS zone to the home network, but assume I could put some restrictions in to do that. UDM-Pro AirPrint and HomeKit not working across VLANs . Accessories from several manufacturers not responding. 5353 port enabled in firewall. When you click on "Apple HomeKit", it queries the It finds any other service but not hap (until I "probe" it). There are solutions but they are custom ones in SSH and not officially supported by Ubiquiti. 3, and ER605 V2 2. Yah, no. I found out there is a physical reset button beneath the normal switch which apparatus to have fixed my issues for now. But I like to have Homekit have direct control. I'm not clear from your post, if you've allowed the actual communication ports between the device(s)? If you have a second raspberry pi / linux machine on your network, you can check that mDNS and multicast are working by installing avahi if you don't already have it and running avahi-browse -all. For now I have control through Homebridge. I’ll use my trio of Elgato Key Light Air devices as an example, but it applies to all devices (printers, Google Cast destinations, etc. Finally, confirm that Pondering on further solutions and not wanting to try and reset Homekit data from iCloud (meaning reconnecting all 20-plus devices again), I started to backtrack to when the issue started. Nevertheless, it is advised that you look into Homekit-compatible routers for a more seamless experience. Typically I need to do this if UniFi has firmware updates. mDNS is a tricky protocol – essentially it’s DNS, but instead of going to a name server for resolution, devices using mDNS send out a multicast packet to the network and wait to see who replies with the answer. Ciao should provide the best experience, however in some network setups it does not work and Bonjour HAP should be used instead. 1 Like. html page again and click on "Apple HomeKit", the camera starts working again the Home App. This is not about if something is wired or not wired, but how your network is configured. Thanks, it helped. The symptoms: Frequent but random "Not Responding" errors in HomeKit. Before it was failing almost every time I opened Home app! Update: still works perfectly. I also have a very old Mac mini on wifi that basically runs the TV. I have several automations set up in the Home app that do not work reliably at all. However, Ubiquiti hasmoved away from some of the internals present in their USG, and as such a fewthings aren't working quite as expected; one of those being the mDNS Reflector. 74. 25. mDNS / Bonjour discovery was flaky, with devices randomly disappearing and reappearing. Not necessarily. after a firmware Because Homekit uses mDNS to open random ports in addition the the control port. not sure whether it just outgoing communication, so, dont need to be accessible from outside or also incoming communication. Well, basically no matter which mdns I use, it’s working all fine apart one specific use case: During the night I have my I've seen dozens of posts trying to get mDNS to work between LAN and GUEST VLANs on the UDM Pro. The most frustrating failure is the one I have set up for sunset. Many users end up having separate networks for LAN and IOT. justinmartin (Justin Martin) April 8, 2018, 1:35am 8. I've tried to install Avahi service on GL-SFT1200 and enabled reflector for 4 interfaces (allow-interfaces=br-lan,wgclient,wlan0,wlan-sta0) but mDNS discovery doesn't work. After the update my homekit stopped working. 5 running inside microk8s on Ubuntu 20. I have the same problem (trying to setup homekit using 0. I am not clear if I need to utilize AirGroup in my home environment. Note: I use network_mode: host. mDNS is a protocol used to discover services on a local network without the need of a central DNS server. After reading reviews this seems to be a very common issue. I have new equipment running all the latest firmware. Both hubs have to be on the same subnet and you have to make sure mDNS isn't being blocked. I dared to "upgrade" my network and migrated over to the UDMP. And now I am not able to re-add it again. You should see a Home Assistant Bridge device in there with domain _hap. I'm mainly struggling with product connected via ethernet and a hub (Philips Hue and Plejd). Turns out 5. Internet Printing Protocol does work, though. jlg89 opened this issue Aug 15, 2020 · 16 comments Closed I think it would be helpful if I can figure out whether or not HomeKit is actually trying to talk to HOOBS, and/or whether or not HOOBS is responding. Once the server was up and running the lamp was responding perfectly again. If this still isn't working delete the existing home on Homekit and then reset the QR code for the hubitat in the integration. on my iPhone or HomePod) I’d expect HAP and mDNS ports to be still open on the Aqara hub. I realize there is an mDNS config in the homekit-bridged setup, but I don't know what goes where? Does anyone have any ideas? Thank you! Cheers, Peter. If recordings dont work, it's generally because of a few reasons, follow the steps to determine where it is failing before asking for help: The motion wasn't triggered. Accessories from one manufacturer not responding. Reply reply iSteve-O The problem is that HomeKit can't discover/setup new device due to mDNS issues I guess. Is there a way to connect a homekit device by ip directly? I have HA running in a docker container and no mdns getting to it and just need to be able to connect to my ecobee. As a curiosum AirPrint does not work either out of the box from my HOME vlan for my HP laser printer being on my IOT vlan. 55). Block LAN to WLAN Multicast and Broadcast Data is NOT checked mDNS repeater was added to the config. Learn what to do if you see "No Response" next to a smart home accessory made by another manufacturer in the Home app. If you don't see many devices show up, you have a network problem, and I'd follow one of the suggestions I suspect that this has something to do with broadcasts not hopping from one network to another; no biggie, I thought, and enabled mDNS repeater on my opnSense router - however, still, no dice. 2, ER7206 V1 1. 73. The Apple TVs serve as my HomeKit controllers, with multiple other devices linked. I'm trying to enable mDNS settings, but I can't figure out how to configure it correct. I think it’s the OS. If the VPN isn't configured to handle mDNS traffic correctly, HomeKit might not be able to discover and connect to the cameras. 6). Devices implementing mDNS need to listen to these packets and respond where appropriate. The HomeKit hub in this case is an Apple TV on the trusted VLAN (see below). so, please check in karaf console with “list” that homekit is running; or something with mDNS works fine but mDNS does not include SSDP, which is an entirely different multicast protocol. Accessories work locally, "not responding" remotely, Home Hub is not talking to HOOBS, maybe mDNS issue #759. 21 firmware on my nanohd was blocking it, rolled back to 4. e. 4GHz only to the IoT devices, than I created a zone for the interface like as the Guest zone, I also tried to use some firewall rules/ports (as I've read online) but they are still Hi. Hmmm Have been running multiple VLANs since day 1 with a USG3, US-16 switch, and 3 APs (Pro, LR, and Lite). avahi-daemon running on docker host with reflector enabled. I figured once I moved over that I wouldn’t have an issue getting it working again. ) I am a HomeKit user, I have a HomePod mini as the main controller, some wifi smart thermostats, and a wifi video doorbell. They both were closed and the hub was not visible in Bonjour network service browser Hello, i have purchased two sets of 3 blinds (homekit over thread) and they have been working well complete with automations. because Mdns does not need to traverse the WAN it just Local Hi, it's the n time that I try to figure out why if I isolate from my main network the IoT devices, then they are superslow to respond (like 3-4 secs to turn on/off a light), see gif below I configured the 2. Eventually timed out. Today, I found this UDM-Pro and Apple Homekit mDNS Configuration guide from September I noticed that all HomeKit devices which connect directly via Wifi stopped responding. I have a new HomePod Mini for a HomeKit Hub. ; @home-assistant rename Awesome new title Renames the issue. if container is not allowed to advertise itself, then we just have to add the mDNS entry into it. mDNS is just the announcement of where to find the announcing device, on what port, sometimes things like supported encryption, etc, however. If I turn off that setting the mDNS a works and homekit works but now all devices on that WVLAN can see each other. I’m running openHAB 3. On macos this can manifest as seeing the mdns response in wireshark but not in atvremote (or whatever app you're using for discovery). TrueNAS SCALE uses Avahi as its mDNS stack. I restarted the Home Assistant container again today and it appears to be working. SirTeddyBear August 10, 2024, 5:41pm 10. Not sure what it was, but right before it started to work I did a container restart in Portainer. I am running OH on a windows machine. When the Starling reboots (esp. 0, network version 6. AirPrint printer B has laptops C has HomeKit devices. Using WireShark shows me that the Home app does not send any mDNS requests until an (already discovered) device is clicked on. bakman2 6 November 2019 13:45 2. 12 level for the network management. Yes Home App and HomeKit require mDNS to work properly. Basics: 3600 running 6. Armed with this knowledge I eventually found that this is a fairly obscure issue that has been plaguing people for years, especially when it came to wireless printing (AirPrint). However, a couple of time they completely bricked and would not even work manually. The Homebridge is running on a Raspberry Pi 4B connected by ethernet to the UDMP and the port on the UDMP is configured for the IOT VLAN. I would expect with the rule above to see the _ewelink mDNS advertisments flow through but they do not. mDNS is still not being broadcast, but the garage door is showing in HomeKit as working. Devices on B can use neither. One thing we noticed that one of the software we use for scanning on our network where it will list all devices on our network and its' ip address, mac number, hostname, and mdns. 3. more important here is not the port but the way of communication - broadcast. Apple Home. If you're using aseparate network and VLAN for your IoT devices,whic If my phone is connected to the AP which has role of controller then it is everything working perfectly, but if my phone is connected to any other AP (roaming) then Homekit stop I took my server offline for rebuild at some point and merely in minutes the lamp had “no response”. ; @home-assistant setup “HomeKit bridge” from UI using the integration option, no errors, got the pin/QR in notification panel, scanned the QR from my iPhone XR home app, and click connect, it spins for a min and says ‘Accessory Not found’ removed the homekit bridge from integration, restarted HA, then went directly to the config. Hi All, mDNS service is added to Gateway since Omada SDN Controller v5. If accessories from one manufacturer aren't responding. As a result, Apple HomeKit was very flaky. just need to be able to Hi Bella, Sorry I should have specified - it means the devices appear in the Home app as “not responding” which as far as I understand means mDNS is not working for those devices. HomeKit support for the impatient. In previous posts, I discussed why and how to set up multiple VLANs and now all those Internet-connected devices are away from the LAN where The Netgear Orbi routers do not come with official Homekit compatibility but Netgear Orbi routers and satellites upgraded to firmware v4. Well, as they are right now, they can communicate without issues. Howdy, Spent the better part of 5 days, trying to figure out why homekit devices would connect to my hub and then a minute or so later go not responding, tested tons of settings, IGMP snooping, multicast toggling etc. I have an automation that is to run one hour before sunset every day to turn on most of the house's lights (by turning on the "sunset" scene). While everything is working fine, I want to understand why these lookups are happening. Mini came out, I bought a few for home and my thermostat just started to report The mDNS repeater service is active. 6, which requires both your Omada Router and Omada Controller upgrading to SDN 5. I'm trying to enable mDNS settings, but I can't figure I have no idea what changed since mDNS is still not being broadcast, but the MyQ has been working in HomeKit for three days now. conf and restart the avahi daemon systemctl restart avahi-daemon. For anyone facing issues with HomeKit and mDNS for homekit devices/accessories in another network/VLAN. 11. I have also forget about communication between different VLANs via FW and simply have client and server in same Essentially, routers can sometimes do wonky stuff when dealing with Bonjour/mDNS (this is what your phone uses to find HomeKit devices in your network) services across the 2. I am a new Hubitat user with experience with SmartThings. There are too many network variables to consider which are out of Apple’s control. HomeKit bridge advertises the host-IP. Also I noticed that my ESP32 devices would do the same in HA. How to determine what is being blocked? Or capture traffic not being passed to IoT vlan? Problem: Home Assistant isn’t auto-discovering devices on my network. So while all native HomeKit devices work fine the ones that rely on Homebridge show "No Response" and that makes no sense. Create the following service under Profiles-> Use homekit integration with mDNS. The snapshots are working as expected, and tapping on a camera quickly loads its live stream (because I have each specific stream pre-buffered in the ONVIF plugin settings for each camera). If Home Assistant broadcasted mDNS through all interfaces, no need to have a stand-alone avahi doing it. So essentially a problem communicating between devices. g. I have Could this work for running samba with avahi/mdns advertisements in a k8s cluster? Wont the mDns advertisements have ClisterIPs on them? How would computers outside the cluster route smb TCP traffic to the ClusterIPs? The HA container is running on the host's network to get homekit working. Networking-wise, various routers and access points have had multicast issues, and several vendors have had to fix multicast bugs in . I wasn't able to get anything to work following the other posts, but I wanted to share what worked for me for my UDM Pro (UniFI OS version 1. Then it works. ). The “same network as the iPad” will be whatever Wi-Fi / hotspot network I’m currently tapping into on any given day. Edit: And of course a few hours after I post this it stops working again. **HomeKit Restarted Homekit Hub 3 times Rebooted rpi 4 I could try removing and re-adding Homebridge to HomeKit. I have (at least) 3 VLANs/WLANs. I think it has to do with networking My assessment is as follows: This is not a problem with the reachability of the IoT devices because: the IoT devices are found and working with HA, even while HomeKit shows “No Response” the elements that I However, when I tried to get it to work with HomeKit, it was not found by HomeKit and I got an "HFErrorDomain error6" when I tried to link Hue with HK. Left all the APs on existing firmware (4. There is no restriction from main to IoT vlan. 1 fundamentally changed the way HomeKit communicates, to get around the poor mDNS controls built into a lot of routers? Because nothing in hardware or firmware has changed on my network, and a software update has transformed the way HomeKit performs. mDNS tells home app that openHAB exists and which IP address and port it has; home app cannot access openhab on the IP address and port from mDNS; so, first check - mDNS. Just enable them in /etc/avahi/avahi-daemon. My HomeKit devices report "Not Responding" occasionally. I have had my ups and downs with HomeKit, but I recently stumbled upon something that undoubtedly will make HomeKit, and hopefully my home network better (still not silver bullet). . My setup is: IPv4-only WAN (PPPoE) Homekit can't access the devices from main vlan. 4 to see if it makes a difference, I have dedicated channels for the 2. Matter devices and routers advertise over IPv6 mDNS, but this does not work across VLANs because there doesn't seem to be any IPv6 mDNS repeater/reflector, at least that I've found so far. Furthermore I am running homekit integration. I have used the discovery app on my Mac and I can see the HomePods showing. When restating OH, homekit doesn’t work. Code owners of homekit can trigger bot actions by commenting:. changing homekit hub from homepod to iPad The problem. 0 Release Build on Docker container on a Synology. My concern/focus of optimization was trying to limit the amount of mDNS, but yes, I've merged the 2 networks right now and did it a try monitoring and looks about the same number of packets, the difference being that the packets aren't being forwarded/replicated to another network, but the broadcasts are Once I’ve got it working I haven’t seen a single “no response” for the accessory for several days. I’ve never had an issue like this before, it’s usually one device or bridge. Configuration: Home Assistant v2021. Anyone can have wifi and wired devices in the exact same subnet. Been up and down the github page and I feel like I'm missing something i did have it working perfectly for a good long while (like 9 months) and i didn’t change anything on the network side. gateway. If you get the "no response", it is most likely due to the home-kit-hub not actually So the assumption would be that 15. In such situations it is needed to make the mDNS messages to travel between subnets. How To Set mDNS Advertiser. 2 milestone in a docker container (network mode: host), on a raspberry pi. 21 and it still didnt work, went down to 4. I removed from homekit and tried to repair just sat ther indicating connecting. Pairing does not succeed: Accessory Not Found. It then works for some time and then stops working. I can't be the only one who is facing issues with different VLANs and HomeKit devices or am I? My configuration (example): - Homebridge VM: VLAN1 - iOS/iPadOS devices: VLAN2 - HomeKit devices: VLAN3 How to make it work that my "smart" devices are able to communicate through different VLANs. 6 do work with Homekit products. 1. It’s not working with Docker and dedicated port control. Works across The UDM-Pro is an impressive piece of networking hardware. 5 IAP's (225's) Single VLAN. However Apple does need to step it up where it has control. However they do connect to the AP and the router, and they have IP addresses, and they can reach the internet. While connected to my management network with the Discover-SD app I see a bunch of mDNS services (Homekit, printing etc) and when connected to my IoT network I see Homekit and a custom _ewelink protocol (my garrage door). Devices on A can AirPrint, but not use HomeKit. Recently changed from "Tunnel" to "Bridge" mode. Avahi/mdns is configure to broadcast across subnets. So I reverted back to the previous version that I used (0. Apple and HomeKit manufacturers are not selling devices that require networking engineering certifications to make work. Is it specific to my setup? Does this happen because of the way HomeKit integration and/or HAP-python are implemented? Are the apple devices to blame? If your devices are connecting to the internet and working, and HomeKit is not working, it is highly likely one of these Your switch or the AP is not handling the multicast part right. Reply reply Plus the random airplay and screen sharing not working from my 15. yaml after following the instructions in that forum post, and magically my devices were working again via homekit bridge mdns-repeater: container_name: mdns_repeater image: angelnu/mdns_repeater network_mode: host environment: hostNIC: eth0 dockerNIC: docker-a5e9846c Matter over WiFi, however, requires IPv6 to operate. Should these methods still work? Saturnus June 16, 2022, So when adding HA Bridge to Homekit, the IP address that Homekit got from mDNS record was the IP Are there any settings or things to enable/check to ensure mDNs / Bonjour / Multicast is working correctly. None are guest, they are all corporate. I shut everything down, and then slowly turn it back on. Contribute to homebridge/homebridge development by creating an account on GitHub. For whatever reason, as soon as I changed the mdns server to avahi, everything worked and I was able to easily and quickly pair each camera with HomeKit. LG TV uses SSDP so enabling mDNS won't do anything to forward SSDP packets. Use homekit integration with mDNS. That's why it's not working. Enroll the hub in homekit first before you add devices. TL;DR Version: Your iOS devices should be able to connect to the HomeKit Devices on port 80 and 443, and mDNS should work between VLANs. I read already a lot about the mdns of the homekit integration vs openHAB’s own mdns service. 1 as they are fully adapted to Controller HomeKit relies on the mDNS (Multicast DNS) protocol for device discovery, which might not work as expected over VPN connections. I’m trying to get the hub talking to HomeKit. To get AirPrint to work, I have for my local unbound DNS forwarder added the following lines of Since upgrading to iOS 14 my HomeKit says home hub not connected Since I updated to ios 14 my HomeKit now says home hub not connected most of the time. You can set the mDNS Advertiser from the "Homebridge Settings" section in the HomeKit DOES NOT “just work”. Anyone know how to fix this. Not all routers are not up to the task or have problems. I'm using avahi to repeat mDNS messages across subnets, everything else is routing rules. 13), but the UDM-P is up at the 6. I'm not using any controller or cloud services. 2) and homekit setup worked inside docker on that release. I did set the IPv4 Scrypted server address. If your HomeKit or Matter accessory isn't responding in the Home app. Fiddling with the UniFi Network Application (which I use to configure my APs, its hosted in my opnSense), I found that there was an option for "Multicast DNS" that was only enabled on The device is clearly on WiFi, but it’s mdns that HomeKit uses to find everything, and that’s what’s not working right. Both the Hunter-Douglas Hub and the Chamberlain MyQ Hub continued to work well. then it is. Everything went fine and most of the stuff was working immediately. 0. Looks like HomeKit is not using them when addressing the accessory Actually, for me HomeKit was pretty reliable in iOS 13, don’t have any complaints Also, if it was an issue with HomeKit somehow (e. The Hue app on my iPhone worked fine all this time. When I run the HomeKit integration program, I hit add accessory in I do not think homekit setup is related to network_mode: host in this case. It is lights are working , but this is causing my automations not to work, and things also stop working when I leave the house. HomeKit Live Streaming Timeout (Recordings may be working) This is always a issue with the I think this helps the homekit system work better, though I do not know why it is not just relying exclusively on mDNS/Bonjour. Any ideas why it there are 2 reasons it could stop working: mDNS is not working. 6 (the firmware adapted to Omada SDN Controller v5. Turns out 5. Suggest you change to a unmanaged switch first or directly connect the AP's to firewalla. Try disabling IGMP Snooping on your router. This makes me think that the initial discovery (to show devices to click on) is not done by mDNS but by some other method. 4ghz and 5ghz SSID's and these are my Wi-Fi settings I got mine working. TIA Ya that is not going to work with homekit, without a bunch of networking hoops jumped through. HomeKit relies on mdns heavily. it is not running.