Igmp snooping homekit android reddit. primary LAN is a Corporate type.

Igmp snooping homekit android reddit If they are connecting to services outside your LAN then that might be an issue but most devices should be firewalled off from the internet in the first place. But that means they also need to optimize multicast traffic internally, so they have IGMP snooping enabled on the virtual switches now. shooting the same media stream to multiple clients. Reason was the multicast enhancement function (which keeps a list of subscribed multicast addresses per client using igmp snooping) which works initially as the client sends a igmp join but fails after the client roams to another ap. 0 as the querier address, this can cause issues, especially if you have multiple devices acting as Igmp queries. On the switch cli the unifi switches decide randomly which one is the querier, sometimes it was the first ip address in the network and sometimes the last. I'd also like it to be fan-less or at least not use the fan during normal operations. I had this issue with my asus router back when I was using homebridge, and I read in the homeassistant forum that people with this issue where having success by disabling IGMP snooping. I made sure I had several ports opened for the IoT devices to reach out to the main LAN (where Homebridge and Scrypted are running on my NAS). Switched various Unifi settings on and off: IGMP snooping, Multicast Enhancement, Optimise IoT Wifi Connectivity, followed by rebooting the UDM Pro and Apple Devices Shut down HomeBridge Update UDM Pro to the latest non-beta firmware Verify that Discovery could see the devices (_hap. As far as I understand it there’s two parts to IGMP snooping 1) the snooping which does the filtering and 2) the querier/mrouter which send out igmp reports that all the multicast listeners respond to which keeps the switch from filtering the stream to that port. 8GHz networks (along with IGMP snooping). Have you toggled any settings related to “IGMP Snooping”, and tried it for however long you normally need to observe the problem? You could also try disabling EAPOL Key Retry if that’s an option for you. 3) from the settings of the router, but without success. json Use stp, not rstp If you have firewall rules then open lots of ports! TCP 3400,3401,3500,30000-65535, UDP 1900-1902,30000-65535 Also, if you use vlan, enable logging Consider using the task scheduler to check and restart igmp (google igmpcheck. At first, nothing bridged to HomeKit via Homebridge or Scrypted worked at all. For more information I have turned off IGMP Snooping, enabled Short GI, Disabled Client Isolation (Obviously), disable SPI Firewall, enabled all ALG and VPN pass-through. Normal Internet traffic is unicast meaning that a packet is delivered to a single recipient. Situation now: netgear 16 port switch, managed, IGMP Snooping enabled. Yes, they do, but only link-local multicast. I have 2. Homekit relies on mDNS, which is UDP/multicast (non-routable / doesn’t cross networks, can be optimized or broken with IGMP snooping, etc). I have rules to allow communication between all the networks back and forth. I activated the snooping(v. Apple TV 4K as HomeKit hub, always on, connected via Ethernet Block LAN to WLAN Multicast and Broadcast Data - disabled Enable multicast enhancement (IGMPv3) - enabled Enable IGMP snooping - enabled Dedicated 2,4 Ghz wireless only for HomeKit devices (with access control via Mac filtering) Latest firmware on all devices I had the same issue but with wired devices. Try using VLC on a laptop to tune into the TV channels, run a packet capture and watch for the IGMP joins/leaves. It's typically used on a managed switch. Setting "Enable IGMP Snooping: Enable" on my 5G network (that the doorbell is on) caused it to not be available anymore. Although this doesn't make sense as from my understanding, IGMP snooping only optimizes network traffic with a lot of broadcasts, doesn't For both networks, main and IOT, I have IGMP Snooping enabled. I have the Asus XD4 mesh network and I get no response in my LifX apps frequently. Multicast Enhancement has been enabled since I set up my networks. Router is Unifi system, mDNS is turned on, igmp snooping and multicast enhancement is turned off. That involves enabling IGMP snooping on my router (I believe, I've got a Zyxcel lmk if I'm wrong). Based on the fact that you have HomeKit tiles that (apparently) originated from HA, it had to have worked at some point. It seems like there should be another global setting somewhere to turn on IGMP Snooping for the whole system. with correct IP address of the VM. I don't have any evidence or sources but I believe having static IP addresses for your devices improves their network reliability, and make them easier to work with homebridge. One of my specific reasons for changing to UniFi was to try to fix my home network issues. This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. I have enabled IGMP snooping and Set it to V2 on Both switches within the VLAN. Change the bridge number could help; whic you would remove the old bridge and add the bridge with the new number. homekit: debug. Apr 24, 2024 · IGMP snooping; Quality of service (QoS) Additional AmpliFi Mesh points; How to Configure AmpliFi Alien to Enable HomeKit. I don’t have any evidence or sources but I believe having static IP addresses for your devices improves their network reliability, and make them easier to work with homebridge. Hi all, I have a HomeKit light switch that constantly gets 0% experience due to “DHCP Timeout” despite still being usable and obtaining an IP address. Once these settings have been configured go to each of your HomeKit devices and assign them a manual IP based upon the MAC address (you can do this in the DHCP list). To avoid having the broadcasts triggering your iOS devices all the time, you can enable IGMP-Snooping in your router settings, if supported. Turning this on enables mDNS "reflector" which is insecure because it also reflects (broadcasts) mDNS packets on the WAN side of the router. Everything had been rock solid on HomeKit for months (16. My hypothesis is that Apple (HomeKit) sets a session expiration timer with each end point and when the Ecobee attempts to re-register when the session expires, the message is mal-formatted and dies between the thermostat and eero causing the thermostat to Both, if it works then you can enable 5ghz IGMP snooping and see if the no response comes back. I had previously disabled this in my router settings because it was causing homekit devices (through HASS) to become unresponsive. The switch is getting old, some leds dont light up anymore while connected with an utp cable. I’ve had a similar issue though I don’t have four thermostats (just one main unit with four remote sensors). e. PS if you have been having issues with Homekit Devices. 168. IGMP snooping should also not be necessary (as that basically limits Multicast data) Try turning off IGMP Snooping on the Network config. The problem therefore is in the final router GL. When I google IGMP snooping and Ubiquiti it does not give any clear answers if this is supported in the GUI or has to be enabled using «hacks». Just randomly drops connection in HomeKit. Note: To enable HomeKit on your AmpliFi Alien router you will need to be on the same WiFi network and have at least one Apple Home bridge compatible device (Apple TV or HomePod Mini). Unifi’s support is hideous. Location - California ISP - Spectrum Router - Tp-Link Archer C4000 - AC4000 MU-MIMO Tri-Band WiFi Router I am going through my routers settings and came upon these IGMP settings Ihave no idea what they mean or what they are my question is shoud i enable all of them some of them or a combination of them and if so what version should i use V2 or V3. 🙄 The biggest culprits are IGMP Snooping and Multicast Enhancement settings on routers that try to limit broadcast traffic and end up causing more issues by blocking that traffic. Ensure Other lights function properly using app + Siri. 1. I’d say the only plus for this camera is native HomeKit support and saving to iCloud. Multicast Enhancement converts to unicast, IMHO that breaks HomeKit discovery when adding new devices. solution was to make sure a igmp querier runs by configuring igmp on the root switch IGMP is a protocol that is used to configure multicast networks. I will see tonight after work if enabled IGMP snooping improved anything. Configure your ASUS router 2. Firewalla is dedicated to making accessible cybersecurity solutions that are simple, affordable, and powerful. It still works but its irritating me that some leds dont work anymore. I am not sure where to look for that in OpenWRT, but I will check. This will fix everything. For me it works better when u enable multicast enhancement and IGMP snooping and disable mDNS. This allows switches to identify multicast groups used in each port. As IGMP Snooping takes the load of the router, and allows the groups to talk amongst themselves, I'm guessing that Alexa makes much use of IGMP to keep it synched. Turnign IGMP on the WAPs on/off didn’t help. Works like a charm. 4. Enable IGMP Snooping: Enable. logger: default: info logs: homeassistant. Multicast on the other hand allows a single packet to be delivered to any member of that multicast group. For the main Wi-Fi, I have Multicast Enhancement enabled. I’ve been tearing my hair out the past few weeks trying to figure out why HomeKit devices would sometimes be unresponsive or very slow to respond and AirPlay devices failed to connect when trying to cast to them 95% of the time. I've had no problems since I turned this on two days ago. “Use Private Address” just randomises the MAC address presented by your iDevice to your Wi-Fi AP. Airtime Fairness: Disable (this one worked for me) Enable multicast routing (IGMP Proxy): Enable-Save it, then restart your Asus router. VM is configured to have separated IP than TrueNas machine. primary LAN is a Corporate type. I did some poking around using Bonjour Service apps and the Eve App itself. then the big day came this morning, I reset the usg to factory, plugged it in, unplugged the orbi and adopted the usg with the controller. 4 GHz and 5 GHz under the same SSID, devices join whichever they want and HomeKit works fine. To learn the router port the switch must receive an igmp general query, meaning you need an igmp querier in the network. Any ideas for what I can do? Just to note, the following was already in place beforehand: mDNS was enabled, IGMP Snooping was enabled on the UniFi VLAN network, the UniFi wireless networks both have multicast enhancement (IGMPv3) turned on, but I don't know whether any of these actually make a difference, I'll test that later. Hello! Thanks for posting on r/Ubiquiti!. The trick with UDP is it’s ‘best effort’, there are no retries, and my guess is at some point some of the switching is not broadcasting the packets (maybe to avoid a loop). 0. 4GHz and 5. Yes, it does. sh). This works flawless with iptv from KPN (Netherlands). For low-end wifi accessories it might be more stable so you might achieve the same result potentially but it really depends on if your Yeelight device can be used via HA / Homebridge and how robust is the plugin you choose. Try the smart plugs set up again. Looking for a not-too-expensive 8-10-port switch which can supply active PoE on at least 4 ports, and that supports IGMP-snooping. Any router settings related to “multicast”, “IGMP”, perhaps even “broadcast” are worth flipping one by one to test if problems goes away. This has nothing whatsoever to do with HomeKit, which uses TCP (and UDP for cameras) which do not know anything about MAC addresses. I can't find any more config anywhere for multicast. We enabled IGMP Snooping via the Unifi backend on vlan 17 and our tvs are not playing any stream. Had a similar problem, mdns not working due to multicast not working. Hi all, I'm having some annoying issues setting up shelly devices. I did not have IGMP Snooping enabled so I enabled that. Why is that? I have IGMP snooping on, but when I toggled ‘enable multicast routing’ as suggested in another forum all of my IOT devices disconnected. I can see the camera on phone in "Discovery" app in _hap. if you have a PIM router, the querier should be the PIM router. lowest IP will be elected to be the Igmp querier, some switches enable the querier function be active as default and use 0. Just upgraded to a Dream Machine SE and I'm looking to tweak the settings for home use. Jun 9, 2022 · I started having problems in the past month or so where HomeKit showed everything as ‘no response’. IGMP Querier is only needed when multiple switches are snooping, as snooping stops the IGMP reports from flooding through the layer 2 domain. Disabled IGMP Snooping Disabled Multicast and Broadcast Control It is suspected the Multicast and Broadcast Control is tbe single problem. I have IGMP Snooping enabled on my VLANs. The switch watches (aka snoops) IGMP messages and determines where multicast traffic isn't needed. The GUI MDNS option on the UDM seems to enable the MDNS reflector. Spent ages trying to re-add but it wouldn't work until I disabled the snooping again. I have many others HomeKit devices (Meross and others brand) connected to the same or others PCLs around the house, so I know that up until the PCL everything works. I have the IGMP Proxy setup on the IPTV tab under Services. Multicasts are a huge part of HomeKit and IGMP snooping can cause problems HomeKit only supports 100 devices per bridge As I have a tendency to just dump everything in HA over into HomeKit, looking into the first and third possibilities was easy and could be implemented in one swell foop; the first being one I was very suspicious of because I Enable multicast routing (IGMP Proxy): Enable. Note: It did start working better when I scheduled a restart of the access points 2x a day. It is IPTV services that are heavy multicast, global-link users and for those configuring IGMP Proxy (=surviving over router) and IGMP Snooping (=not unsubscribing all clients when one does) matters. My television provider requires IGMP Snooping to be active for multicast traffic. No reports then nothing for snooping to snoop and it eventually filters everything. EDIT: Wireshark is your friend. Home App - Verify rooms are synced from other apps (especially “Studio”), and that your lights - including Canvas - are in the correct room. Unless your pfSense box is routing between one or more IP networks w/HomeKit devices, multicast isn't relevant. To the point where I tried another brand mesh system and while the HomeKit works great, I find myself having to restart the network every other day. They seem to be working towards supporting IP multicast TV at some point since that’s something used in a few regions. you will need a Igmp querier in the layer2 network. It is not supposed to hop through router. Go figure. The switch can then avoid sending that traffic down certain ports. Additionally (after a bit of tweaking), I've been able to get the Homekit Bridge connected between Homekit and HASS. After turning it off, half a second later homekit started working again. The idea of Home Assistant / Homebridge is to add HomeKit support for devices that don’t have native HomeKit implementation. 0Ghz during setup if able and seperate the two if able to on a mesh network (if applicable) 2. I use Homekit so I need to enable MDNS so my IoT devices work across VLANs. Test. 4ghz and 5ghz dual band smart connect enabled, WMM enabled and not sure if it needs disabling? (read about it so Yes, I’ve tried a bunch of different settings. Reddit iOS Reddit Android Reddit Premium About Reddit Advertise IGMP snooping - again to do with It’s 2023 and HomeKit’s UI for navigating recorded videos IGMP Snooping is used to optimize the flow of multicast traffic within a L2 domain. Along with IGMP Snooping for all networks as well. Feb 11, 2020 · I checked the switch fabric to make sure IGMP snooping is off (it was) and I checked the Wifi APs. This often fails as the primairy hub changes after an update or reboot and traffic is still routed to the wrong hub. I dug into the TP-link switch menu as well and found that IGMP snooping wasn’t enabled so I did that (in preparation for segregating iot devices). This may help as well! Network optimisation is off, all homekit devices are on the same vlan, multicast is on and igmp snooping is on as well. xxx) Wifi. But should mDNS be enabled for the network they should be visible on or from? Even though it is enabled, it currently still does not work. Check your logs and see if you get an indication as to why HA can't talk to your HomeKit hub. I still have the occasional issue where the Home Hub in the area of the lights (Homepod Mini) decides to randomly switch from 2. Multicast streams are forwarded only to network devices that should receive them. _udp for Thread devices)[ Honestly, internet DNS should matter very little to internal HomeKit devices. components. Enable efficient multicast forwarding (IGMP Snooping): Enable. Enable IGMP snooping on my switch (unrelated, but thought it was worth a shot because I've read IGMP snooping or setting up IGMP proxy in pfSense helped resolve some of these issues for some people). The difference is it is L2 versus L3. I don't even know if that would do anything in this case. _tcp for most and _hap. Can some network gurus help me out here? I want to setup my router and switches properly because I have ipcams, homekit and chromecast devices etc which should utilize multicast traffic. Igmp snooping on its own is not alwsys enough. " Final update: I continued to have these HomeKit issues through all combinations of IGMP & MLD Snooping configurations on the TP-Link switch. Don't go crazy with UPNP, IGMP snooping or any feature you couldn't describe on a whiteboard yourself how it works. Connect to HomeKit. Without a querier the seitches may have to resort to flooding even with snooping enabled on the vlan. I personally ended up using the ubiquiti camera and homebridge to get it into HomeKit. Then I learned to turn on "IGMP snooping" and "Multicast DNS" on all my networks and suddenly my bridge devices came right up. Enable IGMP Snooping Other noteworthy configs. The vendor says that if we want to run several TV boxes on the network using our own network it needs to support IGMP snooping. I have a UniFi Dream Machine Special Edition with multiple access points, mDNS on, IGMP snooping on, band steering on. Not sure what changed. Camera is listed in ready to adopt in HomeKit app. When I deal with IPTV I personally like to just flood each switch with all the TV channels and let them handle the IGMP snooping on their own. Philips HUE App - Settings > Voice Assistant > Siri & HomeKit. The only issues I have are occasionally the DHCP renewal doesn't coincide with a UPnP request, so I either have the reboot the HomePod or the UDMPSE, and everything works fine. For the IOT Network, here are my settings: +1 for a lot of detail. 4GHz over to 5GHz, which causes everything to crap out. There is a thread somewhere in this subreddit that goes into great detail, but once I changed settings according to that thread, a lot of my lingering performance issues with Homekit were resolved (i. HomeKit has been working great on my network for over a year now if one device is having issue, I doubt it’s HomeKit problem because other devices works as expected, try this in order, reboot, update firmware, if this doesn’t work contact support For me, one thing that helped tremendously was disabling IGMP snooping. Bonus points for all the other ubiquiti cameras working like a charm in HomeKit too. Any clue would be appreciated. ) If your gear has working IGMP/MLD snooping, then leave it turned on. Try each of the above separately and see if it gets you any closer to a working setup 😃 I found that turning this on, and all the connected devices having 'IGMP Snooping' turned on fixed the problem. They seem to have really gotten worse since whatever the last UDM-Pro update was. 0Ghz SSIDs are named differently, disable/forget the 5. For a snooping switch to learn where to send reports it needs a router port. In theory, I understand what is multicast and IGMP snooping etc, however, when it comes to practice, I am confused. 4GHz and 5GHz networks are split, IGMP Snooping is enabled, setting wi-fi to channel 6 vs auto, and enabling multi-cast if not already, disabling some ‘supposedly smart but likely not’ options on my mesh generally improved stability. WPA/WPA2 or OPEN only. 4Ghz band b/g/n, 5Ghz not supported. Exact same setup and result as you. Usually, once I wait and the network settles in, the HomeKit / AirPlay issues get resolved. 4 ghz is more reliable. 4 ghz wireless settings to the attached screenshots. There seems not to be any other settings related to IGMP or multicastDNS… You need to keep “Block LAN to WLAN Multicast and Broadcast Data” deselected, Enable IGMP Snooping and turn on mDNS Thanks, u/mzezman The IoT VLAN is set as a Guest type. IGMP snooping tries to redirect mDNS queries to the correct devices instead of it letting it broadcast over the network. You can ssh into the switches and access the “Cisco like” cli and see IGMP status “show ip igmp snooping groups” and it doesn’t appear to be flooding multicast to all ports, so maybe it’s fine. Settings > Networks > Edit Network > Enable IGMP Snooping turned ON for both LAN - Main and VLAN - IoT Services > mDNS > Enable Multicast DNS is turned OFF. I've got my three bulbs hooked into HASS and I can control them from the webUI. Have been dealing with “No Response” intermittent issues with a fairly basic home UniFi network setup, particularly with Logi cams. Any receiver connected to the stack works well. IGMP is for multicast, i. What can be relevant is your LAN/WLAN switches/APs, and IGMP/IGMP snooping. Leaving it off is not the end of the world, but even turned off, some switches (like QNAP) still wrecked havoc. iNet GL-SFT1200, and I think it’s related to the IGMP snooping not working properly. I should mention that everyting has fixed ip assigned (hubs and accessories) and both apple tv’s are wired directly to the switch ( homepod mini is on wifi, but again, on the same At first, nothing bridged to HK via Homebridge or Scrypted worked at all. Recently discovered a setting on the LAN called “IGMP Snooping” which was enabled. I am not sure what I am missing to keep my devices connected to HomeKit. Multicast traffic often isn't transferred between SSIDs and/or bands, reasonably enough, and quirks are router specific. I have all the networks in the "Global Network Settings" Multicast DNS settings. The switch doesn't interfere with IGMP. Meanwhile there are other Thread devices and HomeKit Hubs in between. I have 1 router, 3 switches, 4 cameras, and about 200 clients consisting of light bulbs, IoT devices, games consoles, computers, phones, and tablets, which includes AirPlay and Chromecast devices. IGMP Snooping is on under network settings -> advanced. Multicast Enhancement (IGMPv3) is on under Wi-Fi settings -> advanced. Optional: set static IP addresses for your HomeKit devices. Asus Router: Setting lan domain name to local helps with mDNS as well Also using channels 1,6, or 11 on 2. The Sending Device and receivers are in the same VLAN so there is no routing involved. I currently have a Cisco SG110D-08HP which is almost perfect, except that it lacks IGMP-snooping. I have IGMP Snooping and Multicast Enhancement disabled. For people who changed this setting and then found HomeKit magically works, it is pure placebo. My ATV was the Home hub, but I noticed that my Thread leader was the furthest node from my ATV (~40ft). Does anyone know if this feature is in the pipeline for the Orbi… Because of this, many Wi-Fi APs will do "IGMP Snooping" to watch which machines are sending Internet Group Management Protocol (IGMP) requests, expressing their desire to tune into a given multicast stream. I’ve tried it with all those settings enabled, IGMP snooping off and uPNP on, IGMP on and uPNP off, both IGMP and uPNP off. Apple and HomeKit manufacturers are not selling devices that require networking engineering certifications to make work. But only when the Firewalla Gold was the router. Edit: this editor is the biggest piece of shit on the planet. When you use an IGMP querier, the act of an IGMP snooping switch forwarding IGMP joins to the querier is similar to the act of a PIM router forwarding PIM joins to the RP. Mar 27, 2020 · For me it was my netgear switch which had IGMP Snooping turned on. This setting tries to intelligently limit where multicast packets are sent. • Smart Devices [untrusted devices] (VLAN 40) smart home devices, cameras, homebridge [IGMP Snooping On & DHCP Guarding OFF] • Guest (VLAN 50) [IGMP Snooping & DHCP Guarding OFF] Global Network Settings: • IPv6 Support [off] • Multicast DNS [on] • IGMP Snooping [off] Global Switch Settings: • DHCP Snooping [off] Enable IGMP Snooping and mDNS for both, content filtering off, standard network For the VLAN-Protect, set Option 43 host address to your UNVR or Protect Host IP (which should be on your management VLAN at 192. This will help minimize any miscommunication between devices and across the 2. But it was these settings (Ubiquity) that fixed the issue Ofcourse I have been running all my devices for over a year with these settings “on”. gateway. But then again HomePod personal requests and airplay worked fine in both cases so I dont think the IGMP options above have any impact in the most recent versions on HomePod functionality. Depending on the router, on might be the fix where on another, it’s off that fixes it. Does anyone know if this feature is in the pipeline for the Orbi… Enable igmp proxy in config. I have three separate networks, separated by VLAN's. opening the app and having a ton of devices waiting to connect or I had Multicast DNS and IGMP Snooping both enabled; after I found the article and turned them off, my Nanoleaf bulbs are MUCH more reliable. Feb 19, 2018 · Enable multicast routing (IGMP Proxy): Enable; Enable efficient multicast forwarding (IGMP Snooping): Enable; Optional: set static IP addresses for your HomeKit devices. I know on the USG you can enable the MDNS repeater via the json config file, but there does not seem to be an option on the UDM. x). I tried enabling IGMP Snooping like some folks suggested; nothing seems to work. RPI4, homebridge, homepodshelly app and homekit - Asus RT-AX58U router 2. Turning the iPhone off for a few mins has helped me sever several times. That’s fine as long as everyone does IGMP properly. You should assign each switch doing IGMP snooping an address on the LAN (static is best for infrastructure- just make sure DHCP doesn't collide, like u/tbspy said). I was successfully to add smart plugs to both Homekit and Kasa app, it also work with IFTTT without any issues. I have 2 SSIDs each on their own VLAN and then I have a third VLAN for my security cameras. Nobody's mentioned IGMP. HomeKit throws "Accessory is unreachable. Our smart firewalls enable you to shield your business, manage kids' and employees' online activity, safely access the Internet while traveling, securely work from home, and more. I was surprised that continued with the all-in TP-Link Omada stack in a default state, aside from SSIDs. Home App - Test to ensure everything works Also ensuring 2. Overheating and terrible viewing angles for example. _tcp. Thanks, in For problems with meross homekit stuff do the following: Enable IGMP Snooping: Enable Airtime Fairness: Disable Enable multicast routing (IGMP Proxy): Enable Those names are specific to an asus router, you will have to figure out the equivalent on yours. Unless you have a specific use case you know for sure won't work without it, don't enable it as breaks a whole lot of other things such as in-house Plex streaming 1 (ironically. I disabled IGMP snooping and that solved everything. I haven't a clue the technical details, but it "feels" like the mDNS / IGMP snooping records take time to propagate across the network and to devices. A receiver connected to the the downlinked switch does not work. Create an IOT wifi network associated with your VLAN-IOT Network. Disable IGMP snooping if enabled Router WiFi Settings: Please make sure your 2. Depends on the network. I've tried everything: IGMP snooping, enabling STP, enabling multicast DNS, turning off all smart optimisation features. After reading this I started looking into my UniFi home network setup and ended up turning off “Enable multicast enhancement (IGMPv3)” for each wireless network. Everything on latest firmware as of today. 4Ghz and 5. tl;dr there, constraining multicast traffic to those actively participating in respective groups. Sometimes it's under your control ("IGMP snooping") and sometimes it's totally undocumented. This is due to the massive broadcasting of the HomeKit nodes via Apple's mDNS protocol. My Sonos controller on Mac never works unless I’m using the multicast relay or switch the WiFi on the Mac to the IoT network. I think the multicast is the problem, but yeah, nothing but problems with HomeKit since I “upgraded” . If you turn it on and Matter devices behave badly, that could be due to buggy firmware. Tap on Apple HomeKit from the property I've got mDNS and IGMP snooping enabled for the three VLANS Everything is working fine on the HASS side of things. I have to see whether it stays like this, but the almost immediate correlation between me switching IGMP Snooping off and homekit working is quite promising. I have airtime fairness turned off, but cannot turn WMM off. No support for WEP or WPS. It now makes more sense to me why you sometimes have to enable an IGMP querier even in an L2-only environment when using multicast. mpjm wlc wni wlmcc xhl ongyakm khxbnn qwvbs czuhk zfop