Homekit mdns reddit. Now the HomeKit devices disappear after about 30 minutes.

Homekit mdns reddit I have a pfsense router that has avahi-daemon running and am using it for mDNS reflection across VLANs. I currently have an eero that I use for nothing but HomeKit devices because any HomeKit Device on the Asus router wouldn’t work for more than 2-3 days at a time, and it’s connected to the Asus router via Ethernet and I have no issues, pointing to something with the WiFi portion of the Asus Router (Ethernet HomeKit hubs work fine) I started out on a similar track myself - multiple VLANs all kept nice and securely separated. r/HomeKit. I have been playing with wireless bridges using DD-WRT previously, and then I was not able to discover HomeKit devices on the other Same with Hue and Hue within HomeKit. Now the HomeKit devices disappear after about 30 minutes. Because mdns won’t route, your two devices never discover each other. Avahi is still running - Unfortunately the mDNS seems to stop working too and homekit can’t see the homekit controls for that device either. For immediate help Private in protest to Reddit’s handling of API rules. The server address was set in scrypted settings in every attempt. It works perfectly except for the fact that it can't use mDNS. Toggling Avahi on/off restores correct functionality. x). Also make sure your scrypted is set to network type host, HomeKit uses a lot of random ports so its tough to forward them all otherwise. These may or may not be needed: for IOT_IN ruleset, I opened up ports 80, 443, 51827 for HomeKit as well. Everything works as expectedwith the exception of the hub showing as “no response” in HomeKit frequently. 128 if your remote client connected to vpn and has an ip address of 192. It took an extraordinarily kind redditor sharing their configuration settings for me to figure it out. Fortigate For better or for worse Homekit (and other Apple tech) relies on mDNS. A reddit dedicated to the profession of Computer System Administration. I’ve also tried the default setting for mdns but it made no difference. You'll need both because stuff like sonos speakers use igmp multicast for discovery and communication and that won't be sent between vlans. mDNS uses broadcast packets, which do not cross subnet (like your VLANs). Try turning that on and see if it fixes it. Get support, learn new information, and hang I have a pfsense router that has avahi-daemon running and am using it for mDNS reflection across VLANs. Join us on mDNS is a broadcast protocol that is restricted to the subnet. Unfortunately the mDNS seems to stop working too and homekit can’t see the homekit controls for that device either. Cameras are working in the scrypted ui but still will not pair in HomeKit. 1 and so on. Reply reply Top 6% Rank by size . I've upgraded to pfSense 2. Your AppleTV will work as your hub for Homekit and will try to communicate with devices for Airplay. Between the lack of mDNS and IGMP proxying, a lot of IOT devices are not going to work unless you add something like a raspberry pi or a server running avahi (for mDNS) and pimd (for igmp proxying). HomeKit relies on mDNS to auto discover hubs and other IP-connected devices that advertise HK services on your network. 2. I reset everything, replaced nearly everything, nothing would work. _tcp' on the 'local. I was armed with this article HERE. After turning on the optional dnsmasq DHCP server on my USG router, with the "Enable Hostfile Update" option as well, the USG DNS server will now serve up the *. Only the 2. Make sure you setup your mDNS repeater in your router as well. It requires a proxy or reflector to transmit between subnets. Meanwhile there are other Thread devices and HomeKit Hubs in between. mDns is how homekit devices will be discovered and controlled by HomeKit hubs despite being in seprate vlan. The (un)official home of #teampixel and the #madebygoogle lineup on Reddit. This port is used for Airplay but the counters are incremented when I tested HomeKit. Private in protest to Reddit’s handling of but I think every border router capable device publishes a meshcop. However, the functionality does not appear to work as expected on the UDM-Pro (opposed to the USG, which seems to work as advertised). mDNS broadcast is off, no crazy forwarding rules, it’s bone stock right now. _tcp: $ dns-sd -Z _homekit. As you point out that can leave consumers stuck in the middle finding our own solution. I have set up a Bonjour service for HomeKit and tried to create different mDNS rules but I still can't see my cameras via the Home App when I'm on a different VLAN. Any help would be greatly appreciated. I recently got an M1S hub and successfully connected it to my Wifi network as well as added it to HomeKit. Eero routers and mesh systems are super popular, but they seem to cause some people the types of network issues that we see the most on here like no-response devices and MDNS (how your HomeKit devices advertise themselves to everything else) is not designed to route between subnets. So the HomeBridge plugin communicates with the device via cloud commands, and sends the responses to the AppleTV / HomePod as mDNS. My current config is: The mDNS/HomeKit/AirPlay problem will keep impacting more wifi devices until I restart the router and satellite. all my other stuff (hubs (hue, aqara), macs, ipads, iphones) are on the 5ghz wlan or hardwired. I have switch between the mDNS Advertiser and select a specific network interface but nothing seen to work. I have my devices on my IoT network, but my 3 Apple TVs are on my main LAN and no issues. (Homeassistant and iOS devices are on different VLAN). I've done a bit of reading around and seen that Bonjour/mDNS doesn't work across subnets, and I'd need to run an mDNS reflector like Avahi to let my work laptop see the devices when it's on the VPN. As you said, you need an mDNS reflector. So I have Hmm, my guess would be that you don’t have Multicast DNS (MDNS) enabled. I have 2 HomePod Mini’s that are my HomeKit hubs. _tcp local. This subreddit has gone Restricted and reference-only as part of a mass protest against Reddit's recent API changes, which break third-party apps and moderation tools. My understanding was the whole point of MSDS was to decentralize. Each of my networks are receiving around 20k mDNS packets in a time frame of 30 minutes. ly/HomeKitDiscord If you can connect in a manufacturer’s app but see "no response" in the Home app, it’s a good sign of mDNS problems because that’s how HomeKit discovers devices but not how manufacturers do. I am trying to get this to work where I can use siri shortcuts and Hey Siri by using the Home app. local becoming appletv1, etc. Join us on discord: bit. I also set the mDNS interface to Server Address. 4GHz and 5GHz bands. Every other homekit device (HomePods, HomePod minis, Apple TV, thread bulbs, and other cameras) works on this new IoT Wifi network but the Eve cameras turn back “Accessory not found. Note: Reddit is dying due to terrible leadership from CEO /u/spez. Allow mDNS with your IOT_LOCAL rules via access to 224. If you google [your router model] + HomeKit + mdns there’s a good chance you can get your stuff working. Edit: Figured it out! Two things: I needed to allow the Bonjour/mDNS port, 5353 UDP, in my IOT_LOCAL firewall rule. 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 Use free Flame or Discovery apps on iOS to confirm that your HomeKit accessory disappears from mDNS services list. Everything plays really nice in the homekit ecosystem so long as mDNS is in the picture. The “same network as the iPad” will be whatever Wi-Fi / hotspot network I’m currently tapping into on any given day. I installed VLAN package and configured my vlans as eth0. mDNS is required for discovery as well as firewall allow rule for tcp/udp port 5353 in the local direction of the vlan the HomeKit relies on mDNS (aka bonjour or zeroconfig) to find devices on the network. Cheers Not sure if anyone here can help, but I’ll give it a shot. Hi, this is my first time setting up Homebridge. All Apple features use mDNS to discover each-other: AirPlay to HomePods/ATV, printers, Homekit cameras, continuity features between macOS and iOS, iTunes server, and so on. Additionally (after a bit of tweaking), I've been able to get the Homekit Bridge connected between Homekit and HASS. I did set the IPv4 Scrypted server address. Short Answer - perfect world it makes sense. For HomeKit though, that's a problem because apparently HomeAssistant MUST use mDNS to discover the HomeKit device. I have my AppleTV in my IoT network so I have a rule to allow my AppleTV to connect outbound on port 3722. Enabling IPv6 on Firewalla did not resolve. I have a Synology with DMS 7 so i have try both types of installations (using a spk package and the docker image) and i cannot connect Homebridge to Homekit. Is it because your network bridge is using the Docker networking instead of your Host networking on your Homekit network? Crossing VLANs is REALLY hard for Apple (for some reason). I am fairly certain this is due to the docker container only exposing certain ports. If I turn off that setting the mDNS a works and homekit works but now all devices on that WVLAN can see each other. This isn’t supposed to happen, but some routers don’t properly route mDNS across interfaces (LAN to WLAN, etc Some SOHO routers like my Linksys Velop (MX4200) that has both bands joined together works really well with HomeKit. For my google home that's not a problem because I can just give HA the IP of the google home (it doesn't change) and it'll connect and work fine. I also used the Hue app itself to pair the bridge, via the "HomeKit & Siri" option in the settings, as opposed to adding it via the HomeKit app. HomePods, Apple TVs, iPhones/watch/iPads should be all in same vlan and ssid so that they play nice via bounjour/mdns and ensure home is not complaining about network mismatch. Does anyone know the exact configuration I need to apply? Do I need to create multiple mDNS rules going each way or is one catch-all suffice? Help would be greatly appreciated. 5 and my mDNS reflector (Avahi) was previously working well across my IoT and LAN subnet. A third rule that may be needed for HomeKit is allowing traffic from your apple TVs to the local (router) direction for all connections to TCP/UDP port 5353. Not sure if I have this all covered correctly. As others have suggested, head over to the eero Reddit, describe your My Homekit server port, mDNS, and mDNS interfaces are all default values. I have setup mDNS rules for Apple Homekit and also setup switch ACL rules but struggling to get the HomePods which are on SSID IOT to work with iPhone on LAN SSID. The initial Matter setup of a device seems to only need IPv4 so the Home Assistant bridge isn't used, as far as I can tell. and magically my devices were working again via My home automation is primarily a zwave network so no worries about it contacting the outside world and I use a Pi with a zwave hat and zwave. /r/StableDiffusion is back open after the protest of Reddit killing open API access, which will bankrupt app developers, hamper moderation, and exclude I am using pfsense as my network router, vlans, and avahi pkg is handling mdns. I used Avahi on a Raspberry Pi that's wired connection to the main router. 251 or UDP port 5353. ” These are 4 new cameras out of the box, not four cameras that should need resetting. 4Ghz for some reason, but it went away with a new router. 3 so not sure if this is a mismatch and capwap should be set to 224. Factory Reset the device and set the wifi network name and password to what it was before (this way you don't have to re-setup all of your devices, but can make sure the router doesn't have some weird setting configuration). Sweet! TL/DR: leaky mDNS requests were getting shuffled out to the internet as requested by several homekit related devices. It's been pretty consistently stated on the UI Community forums and on here that that settings blasts your multicast traffic to the WLAN interface as well, which isn't very secure. HomeKit was fine, it was my network. After turning on the optional dnsmasq DHCP server on my USG Make sure to find mDNS option in your router settings and enable it. mDNS is still not being broadcast, but the garage door is showing in HomeKit as working. After upgrading and connecting it as a HomeKit hub, I got notifications about cameras being online and the one which had been offline for days is now online in HKSV and the Apple TV 4K now shows as the Connected hub (which is on my wired network) and the HomePod mini is now in Standby as a HomeKit hub. So I have been banging my head against the wall on this issue and looking for a push in the right direction. I can also see similar symptoms sometimes happen if one of the HomeKit devices switches between router and satellite for some reason without rebroadcasting Just as the other posts are stating, enable mDNS and you should be good. I did manage to get HomeKit kind of running, not sure how, but it is much slower at updating compared to my previous I am using Apple Homekit, which relies on multicast, mDNS / Bonjour for IPv4 and IPv6. Check your logs and see if you get an indication as to why HA can't talk to your HomeKit hub. But, i am confused as to how. I can test and curl the homekit port for homekit but the device just vanishes from How to make it work that my "smart" devices are able to communicate through different VLANs. Unrelated because I know it’s an Amazon product, but the integration with my Blink cameras is great. . It's also a mDNS reflector and not an mDNS repeater, which is set up in the config. after I upgraded homebridge a few days ago, whole platform is finicky as heck, UP/DOWN/UP/DOWN status notifications for cams that are streaming to iCloud via homebridge. So mdns by default would not let your remote client see your printer on 192. To After taking a closer look I noticed that Hubitat was dropping from mdns, "_hap. 168. Dont the homekit devices mdns act as point to point? I. Private in protest to Reddit’s handling of API rules. 0. ' domain, so you can query for HomeKit devices as such: $ dns-sd -Z _hap. It was surprisingly less painful to remove it than I thought it would be, and HomeKit allowed me to re-add it without any errors. In turn, that might also require these thread devices to be added via the Matter framework rather than native HomeKit, which could be more hassle I was convinced it was HomeKit. Then, everything will start working well again for another two weeks or so. Based on the above, I still have the following sitting on Default VLAN / Main wifi network I no longer allow Reddit to profit from my content - Mass exodus 2023 -- mass edited with https://redact. It’s all basically unusable and I’m at the point where I’m thinking of squashing my unifi upgrade plans. My doubt is regarding the amount of mDNS traffic I saw with Wireshark (filtering by mDNS). On the Linux server, I set the mdns to avahi since I made sure I had it running on the server prior to running docker compose. ly/HomeKitDiscord Members Online. It routinely had trouble setting up HomeKit devices on 2. For immediate help and problem solving, please join us at https Prior to 15. Most posts about Homekit and Homepod issues come down to wifi and networking issues. mDNS repeater should also be enabled for all VLANs your homekit/airplay devices are in. responds to pings but sometimes/always unresponsive in homekit. A huge class of problems with unresponsive devices seem to be related to router-specific behaviors around how multicast traffic is handled, without which HomeKit’s use of the mdns (“Bonjour”) protocol I am still using the ac86u as an AI node and it doesn’t seem to bring back any of the issues it’s had with homekit devices and cameras. Everything had been rock solid on HomeKit for months (16. I've got my three bulbs hooked into HASS and I can control them from the webUI. 1. Where I lose the thread is where I run Avahi, and how I configure it. Question/Help Every so often, mdns will append -1, -2 etc to hostnames for devices, such as appletv. Previously homekit bridge worked fine with mdns repeater. i did this bevor the new architecture update, and this solved a lot of issues. 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. When unbound is working, both the VLAN and LAN behave as I’d expect, with proper internet So in this video, he suggests turning on the mDNS service in the UI. If using that "Discovery" app, just click/tap into that section and the info is right there. I have apple devices and use Home Assistant to make HomeKit actually useful (what you can do officially with it is pretty useless honestly). js with HASS to put it all into the HomeKit world it’s super reliable although not as cheap as Wi-Fi or zigbee but it’s been around for a long time and the mesh network is a treat down at 924mhz. If something changes by June 30th, the content will be restored. Looks Does this happen because of the way HomeKit integration and/or HAP-python are implemented? Are the apple devices to blame? While I have no other bridges/devices integrated into the TL/DR: leaky mDNS requests were getting shuffled out to the internet as requested by several homekit related devices. Edit: And of course a few hours after I post this it stops working again. 251 instead. Destroy them with 1-star reviews on any and all app stores. Disabling 5 GHz resolves HomeKit discovery issues at the expense of wireless performance. mDNS Advertiser Avahi or Ciao . I have migrated my system to a Raspberry Pi 4 from a 3 and are now facing issues with my node-re-contrib-homekit+bridged nodes. I recently got a few homekit enabled devices, but I have had other IoT devices that dont work with homekit so this hasnt been an issue. I have been playing with wireless bridges using DD-WRT previously, and then I was not able to discover HomeKit devices on the other side of the bridge. Huge L on my part. As others mentioned, if you’re relying on DHCP with no static address reservations, your Homebridge host could very well get a new IP address, which would then cause all current connections between your iOS/tvOS/macOS devices and these IP-connected Try turning off WMM QoS. Please use our Discord server instead of supporting a company that acts against its users and unpaid moderators. Again, this might be Reddit formatting in my post but try to retype quotes around ipv4 in text editor on your machine, don’t copy from here Yah, no. I want to upgrade the light switches, get some LED lamps, and eventually I do want a HomeKit enabled security system. I ended up resolving that by powering off all HomeKit devices (except for the thermostat and sensors), bringing the minis up first, then the Apple TV, and then everything else . For HomeKit hubs, look for the service type of _homekit. Read the wiki, read the FAQ, dumpster-dived all over reddit and elsewhere, and am basically looking for any recommendations as to ‘make sure to set these and make sure to disable these’ as pertains to the Asus XT8 routers/nodes in a mixed IoT/HomeKit environment, as I think I’ve gotten as far as I can on my own and things ‘generally work’ but I’m still seeing some sporadic Since rebooting the router immediately helps, i guess there is some correlation. local DNS request that used to fail. It was different for my old router that needed me to separate the bands for HomeKit to not act out. Question/Help Hello everyone! I have a small HomeKit setup currently at my house, but I am moving soon and intend to go all out with lighting, switches, door locks, cameras, and more Besides a good signal Homekit devices needs multicast packet routing (key to mDNS, zeroconf, bonjour, etc) to be well handled. New to Mac. _tcp". homekit: debug. Like multiple times in a day frequent. ly/HomeKitDiscord HomeKit Devices on Unifi Network - Recommendations . 251, and my AP Capwap IPv4 Multicast group address is 239. For me this correlates with “no response” almost perfectly. Of course this was after I ordered a replacement. If I keep both the avahi-daemon running and the docker image on the home assistant that runs mdns-repeator, I get a ton of traffic across all of the VLANs that I am reflecting mdns traffic. To your second question, there is no alternative. HomeKit mDNS advertisements and subsequent queries use the destination multicast address 224. You can use an mDNS repeater to get around this, this is the Multicast DNS setting under Global Network Settings, include all networks. Mostly everything works well except for HomeKit. Some switches may even block “unneeded“ broadcast traffic. Reply reply BlankStarBE • Make two “homes”, since you have a HomePod on each WiFi, you can control everything wherever you are. If the mDNS doesnt work right, do a complete reset and start over with the mDNS settings on with your initial setup. logger: default: info logs: homeassistant. For the life of me I can’t figure out how to get HomeKit to work. Anyone know the beat way to approach this? You had to make sure you pass through Avahi (instructions in the scrypted docker compose) otherwise it'll fail and fall back to the normal mDNS setting. It knows these other devices exist because of mDNS, which is multicast traffic that you're likely reflecting across networks. I have experienced this with Asus routers. Is there any way I i moved all homekit accessories to the 2,4ghz wlan, apple tv hardwired, homepods choose by themselves which wlan they join. I am setting up the same type of network. I know this happens when it thinks there is a conflict, although in my network there isn’t a conflict. After that, you’ll need to check your firewall rules. To HomeKit, it appears like the device is just using local mDNS to communicate, when in actuality, the HomeBridge plugin is converting HomeKit commands via mDNS to cloud commands and getting / setting the device I am using Apple Homekit, which relies on multicast, mDNS / Bonjour for IPv4 and IPv6. I did some poking around using Bonjour Service apps and the Eve App itself. Homekit devices must talk with mDNS as written below/above in the other comment. See my post just a few mins ago - I successfully used airplay across vlans in a test network. Explanation - at minimal to have HomeKit play nice. Another solution for Logitech homekit cameras specifically is using an old apple AirPort router and plugging it physically into the ac86u and then connect the Logitech cameras to that router. udp mDNS on your network even when not elected the enabled. I've certainly read similar things on this your devices to route outside your network. components. If my HomeKit devices are on another wifi network in a VLAN, & my iPhones, iPads are on my standard household wifi, will I still be able to connect my iPhone to a HomePod Private in protest to Reddit’s handling of API I'm trying to understand what the best practices are for setting up a HomeKit configuration. Members Online. More posts you may like r/HomeNetworking This subreddit has gone Restricted and reference-only as part of a mass protest against Reddit's recent API changes, which break third-party apps and moderation tools. 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). I was unable to find HomeKit enabled cameras that met my criteria and just gave up and got the Blink cameras. Since each packet should be sent to all devices only once, some mesh networks drop packets instead of broadcasting them, HomeKit replies on mdns heavily and your networks ability to route the traffic to where it needs to go can be a problem when it comes to transmission of such data across nodes. Not sure if the latter made a difference in the pairing process, but I think it did. HomeKit is broken. Based on the fact that you have HomeKit tiles that (apparently) originated from HA, it had to have worked at some point. Apple can you HomeKit uses the service type of '_hap. The solution is probably a mDNS repeater or reflector but where do I install it? On a VM, If the goal is to add HA Bridge to Homekit, we might need to find a way to change the advertised IP in mDNS to Host IP or use another solution in this thread that manually Ensure mDNS repeating across VLANs is enabled and firewall rules set to allow HomeKit traffic between IoT and trusted VLANs. I would rather run avahi-daemon on my router. Unfortuantly, I am struggling a bit to see which Wifi Mesh solutions support multicast (using IGMP_proxy?). 54. Edit: this editor is the biggest piece of shit on the planet. My ATV was the Home hub, but I noticed that my Thread leader was the furthest node from my ATV (~40ft). The reality is that a network can work great for lots of things, and if the router has a a poor mDNS implementation or configuration that IS a problem with the network routing. There are zero signs my outside network sees or can connect to the HomeKit integration entities that HA generates. an IGMP_proxy. Start to move away from Reddit’s website or app. Or check it out in the iptables -A INPUT -i enp2s0 -p udp --dport 5353 -m conntrack --ctstate NEW -j ACCEPT // Allow multicast for Avahi/mDNS/Homekit iptables -A Private in protest to Reddit’s handling of API rules. Go to HomeKit r/HomeKit. mDNS (what Apple brands as Bonjour) is a zero-config networking protocol. ly/HomeKitDiscord came back quickly but the second (Staria bedside) was not responding despite my phone actually seeing its mDNS record - I guess the Home hub couldn’t see it After a while I moved the service files back and the Staria lamp came back in the I was poking around somewhere and noticed something that may cause me some pause. gateway file. For the hell of it, I yeeted this post to ChatGPT and it mentioned that HomeKit uses mDNS for device discovery, which doesn't work over a VPN as Multicast and VPNs don't really play nicely. Siri responsiveness for HomeKit on my Apple Watch and Mac for a while. 4Ghz band is enabled currently and mDNS is on. This subreddit has gone Restricted and reference-only as part of a mass protest against Reddit's recent API changes, which 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. All the items (openhab home automation) I expose to homekit via node red keeps dropping UniFi has a built-in mDNS Service that uses Avahi behind the scenes. Turn on mdns and add the HomeKit bonjour service to the existing service list. Configured Avahi to reflect the mDNS messages and it's working fine. I use a lot of HomeKit at home. now with the new architecture my smart home is again more reliable and stable I've got mDNS and IGMP snooping enabled for the three VLANS Everything is working fine on the HASS side of things. I have since unwound my entire VLAN setup simply so I can have a working home network without installing VMs on my unifi boxes. My current set up is a simple one SSID with everything connected to it one way or another (wifi & 8-port unmanaged switch). it won’t route. Enable IGMP Snooping and mDNS for both, content filtering off, standard network Notes for HomeKit and Sonos and Lutron. 1, I did encounter A LOT of unresponsiveness after unplugging the minis to make the Apple TV the main HomeKit device. It has seemed to solve the 2+ year problem with my Rachio 3 sprinkler controller — It would show clearly connected to the WiFi but a “no-response@ in HomeKit. e, there is no central msdn records, unlike DNS? I recently enabled a VLAN for IoT devices, including HomeKit (requiring mDNS), and now find that either mDNS (as verified with Flame app on my phone) or regular dns via unbound will work, and it seems to be random and determined during the power cycling of my OPNsense appliance. Long Answer - maybe. Garageband app SOLVED! - I was left with no choice but to remove the "unresponsive" HomeBridge from my HomeKit under bridges & hubs, and re-add it. dev/ Reply reply works fine out of HomeKit but sometimes/always unresponsive in homekit. For me it seems to have something to do with mdns as I had to swich on mdns reflector on my Edgerouter X. The terrible mDNS situation with the UDM family completely ruined my plans though. May also not hurt to check the hue hub and make Get the Reddit app Scan this QR code to download the app now. July 30-August 3 (Changed switch) Router: Firewalla Gold Switch: TP-Link TL-SG2428P AP: 3 x TP-Link Omada EAP245 Controller: TP-Link Omada OC200 Status: No change, HomeKit issues persist I enabled mDNS so that I could have HomeKit work with devices across different subnets which works fine. If that doesn't work you could try: Make sure that your router has the most up-to-date firmware. 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. 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. onedoy wfbdm ovjkt imtl jfu yjndze ifrdc ixay uvqq gvbhu