If your HomeKit devices show "No Response" in the Apple Home app, this guide covers the most common causes and fixes from the community.
Quick Fixes to Try First
- Restart the unresponsive device – Unplug it, wait 10 seconds, plug back in
- Restart your Home Hub – Unplug your HomePod, Apple TV, or iPad (whichever is your hub)
- Restart your router – Many "No Response" errors are network-related
- Check the manufacturer's app – If the device works there but not HomeKit, it's a HomeKit-specific issue
Understanding Home Hubs
HomeKit requires a Home Hub to function properly, especially for remote access and automations. Your hub is one of:
- HomePod or HomePod mini
- Apple TV 4K (2nd gen or later for Thread support)
- Apple TV HD
- iPad (if set to stay home and connected)
Check your hub status:
- Open the Home app on iPhone
- Tap the three dots (...) → Home Settings
- Scroll to "Home Hubs & Bridges"
- Look for your hub – it should show "Connected"
Home Hub Issues (Common Cause)
A malfunctioning Home Hub is one of the most common causes of widespread "No Response" errors.
One user on the Apple Community reported: "When I changed the Preferred Home Hub back to the original, all devices that had been showing No Response showed No Response again. This indicated the issue was with that specific home hub. I unplugged that Apple TV, waited a few seconds, and plugged it back in. After letting it boot back up, all devices were responding."
Try switching your Preferred Home Hub:
- Go to Home Settings → Home Hubs & Bridges
- If you have multiple hubs, note which one is "Connected"
- Unplug that hub temporarily – another hub should take over
- Check if devices respond with the new hub
- If they do, restart the original hub before plugging it back in
Network and Router Issues
HomeKit uses mDNS (Bonjour) for device discovery. Network issues that block mDNS cause "No Response."
Router settings to check:
- mDNS/Bonjour – Must be enabled and allowed between devices
- Client isolation – Disable "AP isolation" or "client isolation" on your WiFi
- IoT VLAN – If devices are on a separate VLAN, mDNS must be bridged
- Band steering – Can cause issues with some devices; try disabling
One user reported: "I turned on mDNS across the two subnets, and Bingo!, everything started working as expected."
Simple router reboot often works:
One user found: "The latest fix I found is simply rebooting the router which does also bring life back to my devices!"
Devices With vs Without Hubs
Users consistently report that devices with their own bridge/hub are more stable in HomeKit:
Typically stable (have their own hub):
- Lutron Caseta (with Smart Bridge)
- Philips Hue (with Hue Bridge)
- IKEA Tradfri (with Gateway)
More prone to "No Response" (WiFi direct):
- Meross switches and plugs
- Wemo devices
- ecobee thermostats
- Eufy cameras
- Other WiFi-only HomeKit devices
One user noted: "Devices with their own hubs tend to be extremely stable over the years, while devices without hubs constantly run into 'No Response' errors."
Bluetooth and Thread Devices
Some HomeKit devices use Bluetooth or Thread instead of WiFi.
For Bluetooth devices:
- Ensure Bluetooth is enabled on your iPhone/iPad
- These devices must be within Bluetooth range of a Home Hub
- HomePod mini and Apple TV 4K (2nd gen+) support Thread, which extends range
For Thread devices:
- Thread requires a Thread Border Router (HomePod mini, Apple TV 4K 2nd gen+)
- Thread devices create a mesh network – more devices = better coverage
- Check Thread network status in Home Settings
Check Manufacturer's App First
If a device shows "No Response" in HomeKit but works in the manufacturer's app:
- The device and your network are fine
- The issue is specifically with HomeKit communication
- Try removing and re-adding to HomeKit (see below)
If the device doesn't work in the manufacturer's app either:
- The device itself may have an issue
- Check WiFi connectivity at the device location
- Try power cycling the device
Firmware Updates
Outdated firmware can cause HomeKit issues. Check for updates:
- Open the manufacturer's app for the device
- Check for firmware update options
- Install any available updates
- Wait for the device to restart and reconnect
Remove and Re-add Device
If a specific device keeps showing "No Response," try removing and re-adding it:
- In the Home app, long-press the device
- Scroll down and tap "Remove Accessory"
- Factory reset the device if needed
- Add the device again using the Home app
Note: You'll need to reconfigure any automations that used this device.
Full HomeKit Reset (Last Resort)
If nothing else works and multiple devices are affected:
- Restart all Home Hubs (unplug, wait 30 seconds, plug back in)
- Restart your router and any network switches
- Restart your iPhone/iPad
- Wait 5 minutes for everything to reconnect
If still having issues, you may need to reset your HomeKit home entirely and re-add all devices. This is time-consuming but can fix persistent issues.
Common Patterns
All devices "No Response" at once:
- Likely a Home Hub or network issue
- Restart your hub and router
One device intermittently "No Response":
- Check WiFi signal at the device location
- Check for firmware updates
- Consider removing and re-adding the device
"No Response" when away from home:
- Home Hub may be offline or unreachable
- Check your home internet connection
- Verify hub shows "Connected" in Home Settings
Community Discussions
- If your HomeKit or Matter accessory isn't responding – Apple Support
- All devices are "No Response" in HomeKit – Apple Community
- Fixing HomeKit devices showing "No Response" – Apple Community
- HomeKit Devices Not Responding? One of These Things Will Fix It – How-To Geek