Same with me but in a C7. Only a Hubitat reboot fixes it. I have the hub reboot once a day and it mitigates it but doesn’t fix it as it still happens.
I'm wondering if it might be some weird device type that is causing this. Maybe start with one device, see if its stable, add and repeat until it fails.
Without debug logging of the Homekit app, we really can't tell. The Hubitat team either needs to fix it or give us tools to diagnose ourselves.
5 Likes
So mine dropped off during the night (was working last evening but not this morning). No power outages or nothing that I can trace in the logs.
Tried using the restart integration and just won't connect back. Rebooted AppleTV twice, nothing. Rebooted C7 Hub, now back up and running. So restarting the integration does nothing but rebooting does work??? This is kind of weird especially since it had been rock solid for 3 weeks at least with some power outages during that time, note that the C7, router, cable modem are all on UPS but not the AppleTV, each time everything came back as expected. Also I checked to be sure that Homekit was working before rebooting it.
Have you tried homebridge with Hubitat maker ?
Not for now, I only use homekit for the IOS presence, but also use Locative with Maker API and that is pretty flawless (except once where for some reason Maker API was not receiving anything anymore for some reason, had to reboot to get it working).
Hang in there! Possible fix for “no response” in Beta testing.
1 Like
Already updated the hub with HomeKit 
I updated my HE C8 on Saturday and still no luck with homekit. Homekit did suddenly respond once or twice, but every other time I've gone to use it it says devices aren't responding. I also lost access to some of my Kasa switches. Seems to close to be coincidence.
Duplicate post (with less info here) I responded on the other thread:
1 Like
It's so strange that many of us have the complete opposite... mine never drop. I have 5 Hubs and one Homebridge all connected to HomeKit all the time. I haven't seen a 'not responding' in a long time, probably at least back to when Apple shifted us all to the new code. May of 2023 or so (?)
Prior to that shift, I used to see "no response" often but it was clearly on the Apple side because nothing I did on Homebridge helped. (A year ago was pre-Hubitat integration.)
When I open Home and Home Settings then look at Home Hubs & Bridges it shows 9. That's 5 Hubtat hubs, a Homebridge and then 3 Apple products (2 TVs one HomePodMini). One of my ATV is currently the "master" (connected vs standby).
I must throw in my traditional caveat: I don't use Apple's Home app much. It's just another dashboard to me in many ways. It's my go-to when I'm "showing off" my SmartHome to guests.
I have an outdoor heated pool shower that is controlled by Hubitat. Because it's water and I would really hate to have the valve be open all night, I wrap the valve device with automations to overkill the OFF state. That means I need a way to enable it and block the OFF overkill when people are actually using the pool area. So it's one of the few times I whip out my phone to interact with my home. I use the Home app to Enable the pool shower and then disable it hours later when it's no longer needed. The point of this is to say, especially now, during summer, I'm whipping the phone out once a day and would seriously notice a "not responding" and get angry. 
2 Likes
I just got an unresponsive devices messages when I open the Home app on my Mac. I just select my other home and select back and all is good again.
@jtp10181 just brought something to my attention and I feel kind of dumb for it, but the new update was to keep a connection alive between the HE and a home pod or other apple hubs.
I don't have any home pods or apple tvs, etc. I only have a C8 and my iphone. It seems most other people here have home pods and are figuring out ways to keep the connection alive between apple hubs and HE. Are there others like me just using homekit on their phone and getting "no response" or am I just weird??
When my Homepod went down I did not replace it for a while so I was running without a Home Hub. I am using Homebridge (instead of build in integration) which is normally very solid but without the Home Hub it became flaky. I would get the no response sometimes as well.
No saying there is no room for improvement on that end but it would need a different approach and may never be 100% reliable without a home hub.
1 Like
I was doing this without a pod before and I would have to reboot the phone and my watch and the c8 to clear this up (the watch hated it, I just assumed that it was a no go for the home app).
I recently added a HomePod mini and the not responding went away with the previous “ping send ping ack” fix. I turned that off to see if the issues was fixed with the update and after an initial reboot it has been working flawlessly.
Now to confirm, I removed the mini because the “choose the speakerphone each time” issue was driving me nuts and the issue instantly reappeared for me and was dropping every 2-3 hours. So I settled for the lesser of two evils and tossed the mini back in.
Might not be everyone’s experience but doing it just with the phone/watch for me was painful.
Never heard of this before? I have one HPM as my home hub and I do not get anything about choosing a speakerphone?
Do you have the HPM on your desk very close to where you phone rests maybe?
I have also given up on the built in HomeKit integration and gone back to using Homebridge v2. The built in integration just simply isn't stable enough. Devices dropping offline every day. Have tried setting daily reboot on both my hubs, that doesn't provide a solution. Really too bad, hope they fix this.
They’re certainly trying. There have been attempts to resolve the issue in recent beta firmware builds, including one that was released earlier today.
It's definitely a maddening bug, whatever it is. I've never had an issue with it (knock on wood!), but my HK integration is admittedly super vanilla.
I feel for you folks wrestling with this though -- I know how frustrating it is to deal with an ongoing headache like that (my zigbee mesh was a crazy-making mess for a long time when I moved from my C7 to C8).
Hang in there!
1 Like
Daily reboots help, and I'm running 163 firmware now, which has been a improvement.
