Smart Home

HomeKit shows 'No Response'

Fix HomeKit 'No Response' the operator way — one accessory vs all, the home hub, and the IPv6/mDNS/AP-isolation network causes behind it.

Problem summary

HomeKit 'No Response' splits on a single question: is it one accessory or many? One usually means that accessory or its Thread/Bluetooth path; many at once means the home hub or the network — IPv6 disabled, mDNS/Bonjour blocked across VLANs, or AP/client isolation cutting the local peer-to-peer HomeKit needs. Power-cycle Thread accessories and wait for the mesh before assuming a dead device.

Operator snapshotEvidence first

First proof

Count what's failing: one accessory, or many across brands?

Screen to open

Home app > Home Settings > Home Hubs & Bridges

Expected signal

You can tell whether it's a single device or a home-wide failure.

Stop boundary

If multiple Thread devices fail, treat it as mesh fragmentation, not one device.

Layer path

1'No Response' is a reachability state, not a dead device — Apple's own article splits it by whether one accessory or several manufacturers fail, and that fork points at completely different fixes.

2Several manufacturers failing at once is almost always the home hub or the network: HomeKit needs IPv6, mDNS/Bonjour name resolution on the LAN, and local peer-to-peer between devices and the hub.

3One accessory failing is that device or its transport — a Thread accessory that lost the mesh, a Bluetooth device out of range, or a Wi-Fi accessory that dropped off.

4Thread accessories need patience: Apple specifies powering the accessory off for ~5 minutes and then waiting ~10 minutes for the Thread network to stabilize before judging it failed.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Classify the failure

Check: Decide if it's one accessory or many across brands.

Expected result: You know whether to chase the device or the hub/network.

If not: If unsure, assume network-wide first (cheaper to rule out).

Restart hubs and router

Check: Power-cycle Apple TV/HomePod hubs and the router/modem.

Expected result: Accessories return after the hub and mDNS/IPv6 re-establish.

If not: If only some return, continue to the network checks.

Verify the network basics HomeKit needs

Check: Confirm IPv6 is enabled, AP/client isolation is off, and mDNS reflects across any VLANs.

Expected result: Devices and the hub can discover and reach each other locally.

If not: Fix whichever is wrong; these three cause most home-wide No Response.

Recover a single Thread accessory

Check: Power it off 5 minutes, re-power, wait ~10 minutes near a border router.

Expected result: It rejoins the mesh and responds.

If not: If still failing, see /smart-home/no-thread-border-router-found.

Stabilize the home hub

Check: Ensure a reliable, awake hub (a wired Apple TV) rather than a sleepy HomePod on 'Automatic'.

Expected result: Remote control and automations stay reliable.

If not: If the hub changed after an update, see the Apple Home upgrade page.

Decision tree

If: Everything across brands shows No Response.

Then: Home hub or network-layer failure.

Action: Restart hubs + router; verify IPv6, mDNS, and that AP isolation is off.

If: Only third-party (non-Apple) accessories fail.

Then: Local connectivity blocked (VPN/security software, AP isolation, mDNS).

Action: Check a VPN or third-party security app on the controlling device; disable AP isolation.

If: One Thread accessory fails, others fine.

Then: That accessory lost the Thread mesh or is out of range.

Action: Power-cycle and wait ~10 min; confirm a border router is online and nearby.

Safe stop: If multiple Thread devices fail, treat it as mesh fragmentation, not one device.

If: It started right after a Home/iOS update.

Then: The Apple Home architecture upgrade changed the hub or locked out a device.

Action: See /smart-home/apple-home-upgrade-devices-offline (iPad-hub loss, guest OS minimums).

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
All accessories No Response after a router change.	Router IPv6 setting, AP/client isolation, mDNS reflection state.	Network (IPv6 / isolation / mDNS)	Re-enable IPv6, disable AP isolation, reflect mDNS across VLANs.
Only non-Apple accessories fail.	VPN or third-party security software on the controller; SSID isolation.	Local connectivity blocked	Disable the VPN/security app's local blocking; turn off AP isolation.
Intermittent No Response, worse when away.	Which device is the 'Automatic' home hub and whether it sleeps.	Home hub selection	Add/keep a wired Apple TV as a reliable hub; stop relying on a sleepy HomePod.
One Thread lock/sensor unresponsive.	Distance to the nearest border router; mesh fragmentation.	Thread mesh / range	Power-cycle and wait; add a mains-powered Thread router; merge the mesh.

Reference

Commands and settings paths

Identify the home hub

Home app > Home Settings > Home Hubs & Bridges

Where: On your iPhone/iPad.

Expected: At least one hub shows 'Connected' (Apple TV or HomePod, not an iPad).

Failure means: No connected hub means no remote control, automations, or Thread.

Safe next step: Add or wake an Apple TV/HomePod; an iPad is no longer a valid hub.

Check local reachability to an accessory

ping6 <accessory-link-local-or-IPv6>

Where: From a Mac/computer on the same LAN/VLAN.

Expected: The accessory answers — IPv6 is up between you and it.

Failure means: No reply suggests IPv6 blocked, isolation, or a routing/VLAN gap.

Safe next step: Re-enable IPv6, disable AP isolation, or put hub+accessory on one VLAN.

Confirm mDNS/Bonjour discovery

dns-sd -B _hap._tcp (HomeKit Accessory Protocol)

Where: From a Mac on the LAN (or use an mDNS app).

Expected: HomeKit accessories are listed as they advertise over Bonjour.

Failure means: Empty results across a VLAN mean mDNS isn't being reflected.

Safe next step: Enable an mDNS reflector between the VLANs or keep them on one network.

Hardware boundary

Hardware and platform boundary

Change only when

Add a wired Apple TV 4K as the home hub when remote access/automations are flaky on a HomePod-only setup, or when you want a dependable Thread border router.

Evidence that matters

A mains-powered, wired hub (Apple TV 4K) for stable hub + Thread border-router duty, and a router that allows IPv6 + mDNS on the smart-home network.

Evidence that does not matter

Accessory megapixels/wattage marketing — reliability comes from the hub, IPv6/mDNS, and a healthy Thread mesh, not headline specs.

Avoid

Relying on an iPad as a home hub (no longer supported) or leaving AP/client isolation on for the smart-home SSID.

Related tool

Use the linked tool to turn this runbook into a guided check for your exact setup.

Device setup troubleshooter

Last reviewed

2026-06-03 · Reviewed by HomeTechOps. Built from 2026-06 research verified against Apple Support 102056 (No Response) and 102287 (Update Apple Home); leads with the one-vs-many-manufacturers fork, the exact Thread power-cycle timings, and the IPv6/mDNS/AP-isolation network causes. Re-verify the hub-eligible device list before publishing.

Sources/assumptions

Assumes an Apple Home with at least one home hub (Apple TV or HomePod) and accessories over Wi-Fi, Thread, or Bluetooth.
Apple's published Thread-accessory recovery timings (power off 5 minutes, then wait ~10 minutes for the Thread network to stabilize) are used as-is.
Network causes are stated as setting classes to check (IPv6, mDNS/Bonjour, AP isolation), not as a claim that a specific router brand blocks HomeKit.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Apple Support: If a HomeKit accessory shows No ResponseUsed for the one-vs-several-manufacturers diagnostic fork, the Thread accessory power-cycle timings (5 min off, 10 min to stabilize), home-hub restart, and the router/VPN/security-software checks.Connectivity Standards Alliance: Matter 1.5 (cameras, closures, energy)Used for the Matter version timeline (1.4 Nov 2024 to 1.5 Nov 2025 cameras/TLS to 1.5.1 Mar 2026) and Matter's IPv6 + mDNS requirements relevant to VLAN segmentation.Bitdefender: Thread 1.4 slow rolloutUsed for the 2026-01-01 cutover (new Thread border routers must be Thread 1.4 certified) and Thread 1.4 credential sharing that fixes the 'new hub = new mesh' fragmentation.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Confirm the layer (radio, IP, app) before deep config.
4. Stop when the evidence says the risk moved.

FAQ

Why do all my HomeKit accessories show 'No Response' at once?

When everything fails together it's rarely the accessories — it's the home hub or the network. Restart your home hubs (Apple TV / HomePod) and power-cycle the router/modem. Then check the network-layer causes: HomeKit needs IPv6, mDNS/Bonjour to resolve on the LAN, and local peer-to-peer between devices — so disabled IPv6, mDNS not bridged across VLANs, or AP/client isolation will knock out the whole home. See Apple's No Response steps.

Only one accessory says 'No Response' — what now?

Isolate that one device. If it's a Thread accessory, Apple's own fix is to disconnect it from power for about 5 minutes, reconnect, then wait roughly 10 minutes for the Thread network to re-stabilize before judging it. Confirm it's in range of a Thread border router (Apple TV 4K / HomePod), and that it isn't stuck on a fragmented Thread mesh — see no Thread border router found.

Does it matter which device is my home hub?

Yes. Remote control, automations, and Thread all depend on a working home hub, and an iPad is no longer a valid home hub on the current Apple Home architecture. If 'Automatic' hub selection keeps landing on a HomePod that sleeps or is poorly placed, having a wired Apple TV present as a reliable hub usually steadies things. If the hub itself changed recently, see the Apple Home upgrade.