Skip to content

If you can log in to the manufacturer’s app, but see “no response” in the Home app, it’s a good sign of mDNS issues, because that’s how HomeKit devices are discovered, but not how manufacturers do them.

If you can log in to the manufacturer’s app, but see “no response” in the Home app, it’s a good sign of mDNS issues, because that’s how HomeKit devices are discovered, but not how manufacturers do them.

Whenever I see people complaining about the dreaded “unanswered” errors in the Home app, my first question is always “What router are you using?” If you’ve participated enough in this sub, I’m sure it’s your first question. However, the solution is not as simple as “Update your network”. Routers, mesh systems and other top network equipment are not necessarily good _ for HomeKit_. When I tested Eero, Asus, Ubiquiti and others, they all had bad mDNS implementations, despite otherwise very solid solutions. Yes, they can all provide excellent coverage, signal strength, the whole experience. But their mDNS issues are the reason why you still see people complaining about HomeKit even after they have “upgraded” to one of the solutions that all people on the wireless network claim to be the best. It works great for anything … except HomeKit, which to me was a dealbreaker. Personally, I ended up going with a Synology router and it was bulletproof. I see “no response” for any of my devices. YMMV. I’m sure there are other solid options. I would love to know your experiences.