Fix HomeKit accessories showing "No response"
Updated 2 July 2026
"No response" is the most common HomeKit problem, and in the vast majority of cases it is a network problem, not a broken accessory. HomeKit discovers devices with multicast DNS (mDNS, also called Bonjour), so anything on your router that blocks or filters multicast traffic makes accessories vanish even though they are powered on and connected to Wi-Fi.
Start by narrowing the scope: force-quit and reopen the Home app (or any HomeKit app), then check whether one device is unresponsive or all of them are. If everything shows "No response", the cause is your network or your home hub. If it is a single device, the cause is usually that device's power, pairing, or Wi-Fi band.
The fix, in order
- 1
Power-cycle in the right order
Restart your router first, then any bridges (Philips Hue, Aqara, Lutron), then your home hubs (unplug the Apple TV or HomePod for 20 seconds), and finally the affected accessory. The order matters: hubs and bridges need the network up before they reconnect, and accessories need their bridge up before they re-announce themselves.
- 2
Enable mDNS / Bonjour on the router
HomeKit cannot work without multicast DNS. On most routers the setting is called "mDNS", "Bonjour", or "Multicast DNS" – on UniFi it is under Networks as "Multicast DNS" (an mDNS reflector). Make sure it is enabled on the network your accessories and hubs share.
- 3
Disable AP or client isolation
Guest networks and some "IoT" presets enable "AP isolation" or "client isolation", which blocks devices from talking to each other. HomeKit requires device-to-device traffic on the local network, so this must be off for the SSID your accessories use.
- 4
Use WPA2/WPA3 mixed mode, not WPA3-only
Many accessories, especially older or 2.4GHz-only ones, cannot join a WPA3-only network. Set Wi-Fi security to WPA2/WPA3 transitional (mixed) mode.
- 5
Keep 2.4GHz on and tame band steering
A large share of Wi-Fi smart home devices are 2.4GHz-only. Keep the 2.4GHz band enabled, and if your mesh system aggressively "band-steers" (sometimes called Smart Connect), soften it or temporarily split the SSIDs so 2.4GHz devices get a stable network to sit on. If devices keep dropping, also try disabling 802.11r fast roaming for the IoT network – cheap Wi-Fi chipsets often handle it badly.
- 6
On managed networks: fix IGMP snooping and VLANs
On UniFi and other managed gear, IGMP snooping can silently drop multicast after about a minute, so devices connect and then flip to "No response". Either disable IGMP snooping on the IoT network, or configure it fully (flood known protocols, forward unknown multicast to router ports). If accessories and hubs sit on different VLANs, mDNS must be reflected across them – if you are not sure how, keep everything on one subnet. VLAN-separated HomeKit without an mDNS reflector is the most common self-inflicted failure.
- 7
If a single device still fails
Open the manufacturer's own app and check the device there. If it responds in the vendor app but not in HomeKit, remove it from the Home app, factory-reset it, and pair it again. If it does not respond anywhere, the problem is power or Wi-Fi signal at the device.
Why it happens after a router change
If everything worked until you replaced the router or ISP box, the new router almost certainly ships with different multicast defaults: mDNS off, a guest network with isolation on, WPA3-only security, or merged bands with aggressive steering. Walk the steps above against the new router's settings and accessories typically come back without re-pairing. Devices that show "No response" until you open the manufacturer's app are a classic sign of blocked mDNS: the vendor app wakes the device over its own cloud connection, while HomeKit's local discovery stays blocked.
Remote access shows "No response" but home works
If accessories respond while you are home but not when you are away, the problem is your home hub, not the accessories. All remote traffic routes through a hub (Apple TV or HomePod). Check Home Settings → Home Hubs & Bridges and make sure one hub shows "Connected" – if none do, follow the hub troubleshooting guide below.
Frequently asked questions
Why do my HomeKit devices say "No response"?
Usually a network issue: the router is blocking multicast DNS (mDNS/Bonjour), AP isolation is on, the network is WPA3-only, or band steering keeps kicking 2.4GHz-only devices. If all devices are unresponsive at once, restart the router, bridges, and home hubs in that order, then check those router settings.
Why does an accessory work in the manufacturer app but show "No response" in HomeKit?
The vendor app talks to the device through its own cloud, while HomeKit uses local mDNS discovery. If the vendor app works but HomeKit does not, your router is blocking or filtering multicast traffic – enable mDNS/Bonjour and disable AP isolation.
Does HomeKit work across VLANs?
Only if mDNS is reflected between the VLANs and multicast is forwarded correctly. Without an mDNS reflector, accessories and hubs on different VLANs cannot discover each other. If you do not run managed networking gear deliberately, keep everything on one subnet.
Do I need to re-pair accessories after changing routers?
Usually not. If the new network has the same SSID and password, accessories reconnect by themselves once mDNS, isolation, and security settings are correct. Re-pairing is only needed when the accessory itself lost its network credentials.
Related guides
Control HomeKit from iPhone, iPad, Mac, and Apple TV
Itsyhome is a fast, native smart home controller with live cameras, sensor history, automations, and Home Assistant support on Mac. Free on Mac, one-time Pro unlock across all platforms – no subscription.
Download Itsyhome