I have a certain wifi lamp (Xiaomi Mi Desk 1S) which is very prone to "unanswered" problems. The lamp shows "no response" in HomeKit applications very often, but works through its own application at the same time. It will reappear in HomeKit if I turn it on / off with a physical button or recycle power, but will have "no response" soon again. Recently, it started happening almost every time I open the Home app, I'm sure many of this sub have experienced similar issues and the consensus is that this is caused by the weakened mDNS implementation in the accessory or router firmware. The affected accessory will usually not appear or disappear frequently if you browse the Bonjour services. Looks like I've found a solution: ** TL; DR I've always set up Avahi on my server on the Raspberry Pi to advertise exactly the same service data as and my disappearing device. ** Detailed steps below (implies that you are familiar with the Linux command line) - Use the free Flame or Discovery apps on iOS to confirm that your HomeKit accessory is missing from the list of mDNS services. To me, this correlates almost perfectly with "no answer." If the _hap._tcp service is always present at the "unanswered" time, then you have another problem and it won't help. Also, this solution isn't relevant if all of your devices aren't responding at the same time - Capture service data. This is an optional step, you can export these details from the Discovery app. Install avahi-utils: `sudo apt-get install avahi-utils` Use avahi-browse to list _hap._tcp services and find the accessory with a common" unanswered "issue. Write down all the details `avahi-browse -v -t -l -r -p _hap._tcp` - Add the service to Avahi:` cd / etc / avahi / `` sudo nano hosts` Add the hostname and IP of the accessory ( must be static!) in the hosts file. You will find details in the captured data 10.0.1.123 myhost.local `cd services` Create a new service file, the name does not matter, I used 'hap'` sudo nano hap.service` Add XML content in a format similar to the example below using the details you captured above. We used a slightly different service name to avoid adding numbers automatically MiDeskLamp1S _hap._tcp MyHost.local 80 c # = 1 ff = 1 id = 54: 16: 20: 22: E2: ED md = MJTD01SYL pv = 1.1 s # = 4 sf = 0 ci = 5 < txt-record>sh = / E5Jkg == - When you save the file, the new "duplicate" service will run immediately. You can see it in iOS apps. When the service registration of the accessory is visible, two services will be displayed in the Flame application (Discovery seems to fold them together), when it disappears, you will only see your registration. duplicate recordings Once I made it work, I didn't see a single "unanswered" accessory for a few days. It used to fail almost every time I opened the Home app!