The "No Response" error for Lutron switches in Apple's Home app typically occurs when your router's IGMP Snooping settings block the mDNS (Multicast DNS) discovery packets that Lutron hubs send to communicate with HomeKit. This network-level interference prevents your Apple TV or HomePod from maintaining a stable connection to the Lutron bridge, even though the Lutron app itself works perfectly.
Quick answer
• Reboot your active HomeKit hub (Apple TV or HomePod) to refresh the mDNS device list • Assign a static IP to your Lutron hub in your router settings • Disable IGMP Snooping on your router if the above steps don't work • Applies to: Lutron Caseta Smart Bridge, Smart Bridge Pro, RA2 Select
Symptoms
• Lutron app works perfectly and controls all lights normally • Apple Home app shows "No Response" for all Lutron switches • Siri responds with "I didn't hear back from your devices" • Unplugging the Lutron hub temporarily fixes the issue for about an hour, then it fails again • Other HomeKit devices work normally
Quick checks
Identify your active HomeKit hub: Open Home app → Home Settings → Home Hubs and note which Apple TV or HomePod shows as "Connected"
Verify Lutron hub connection: Check that the Lutron bridge shows a solid green light and is connected via Ethernet
Test Lutron app: Confirm you can still control switches through the official Lutron app
Step-by-step fix
-
Reboot your active HomeKit hub (this fixes the issue 70% of the time)
- Unplug your "Connected" Apple TV or HomePod from power
- Wait 30 seconds
- Plug it back in and wait 2 minutes for full startup
-
Assign a static IP to your Lutron hub
- Find the MAC address on the sticker on the bottom of your Lutron hub
- Log into your router's admin interface
- Navigate to DHCP settings or Device Management
- Create a static IP reservation (e.g., 192.168.1.50) for the Lutron hub's MAC address
- Reboot the Lutron hub by unplugging it for 10 seconds
-
Adjust router multicast settings
- In your router settings, look for IGMP Snooping
- Try disabling IGMP Snooping (many consumer routers handle this poorly)
- For UniFi/Ubiquiti: Enable Multicast DNS if available
- Reboot your router after making changes
-
Test the connection
- Wait 5 minutes after all reboots
- Open Apple Home app and test Lutron switch control
- Try voice commands with Siri
If it still isn't working
Check for network segregation: If your Apple TV is on an IoT VLAN and your phone is on the main network, enable inter-VLAN mDNS routing in your router settings.
Try a different HomeKit hub: If you have multiple Apple TVs or HomePods, unplug the current active hub to force another device to take over as the primary hub.
Factory reset warning: Do NOT hold the button on your Lutron hub for 20 seconds unless instructed by Lutron support — this performs a factory reset and will erase all paired switches and scenes.
Contact Lutron support: If you have enterprise networking equipment with complex multicast filtering that you can't modify.
FAQ
Q: Why does unplugging the Lutron hub temporarily fix it? A: Unplugging forces the hub to re-announce itself via mDNS, but if your router's IGMP settings are blocking these packets, the connection degrades again within an hour.
Q: Will this affect my other HomeKit devices? A: No, most other HomeKit devices use Wi-Fi or Thread and aren't affected by the same mDNS routing issues that impact Ethernet-connected Lutron hubs.
Q: Should I use Wi-Fi instead of Ethernet for my Lutron hub? A: No, Ethernet is more reliable. The issue is network configuration, not the connection method. Lutron hubs perform better with wired connections.
Q: What router brands have the most issues with this? A: ISP-provided routers (Xfinity, Spectrum) tend to have aggressive IGMP filtering. Consumer mesh systems like Eero and Orbi usually work well with default settings, while enterprise equipment like UniFi works best when properly configured.