Homekit integration has been exceptionally unreliable for the past few months?

C-7 hub, running 2.3.9.177.

Homekit constantly goes non-responsive after rebooting the hub, usually within an hour or two, so it’s essentially been useless for a few months now. I haven’t made any real network changes equipment or configuration wise, no added devices, etc.

Hue, Lutron, Switchbot, et al. are all still able to communicate with Homekit directly apart from Hubitat when it goes non-responsive. I’ve tried rebuilding the database, ensuring all of my Hubitat applications are up to date, etc with no resolution here.

Any ideas on where I should start diagnosing this? Possibly related, I’ve also had my hub freeze up entirely a few times this week now which I can only assume is related to updating the platform this week.

You're right, it should work extremely well. It has for me and I've done nothing special.

I have 5 hubs, each with a Homekit Integration active. I encounter zero Not Responding status, in months. Largely speaking, I can't remember when I last encountered it. Long before Hubitat had the Integration, I only had Homebridge via Dan.T's product and before that the only choice was Tenesto's Homekit package. The Tonesto one (v1?) was fraught with those issues. The Dan.T one was my beginning of a time without Not Responding. Tonesto came out with v2 but I had no reason to try it, so I cannot comment at all.

When Hubitat announced their Integration, because of those initial restrictions, I continued using Homebridge but I did move a tiny number of devices to the Integration to try it out. It worked as well as Homebridge for me, so slowly, I added the Integration to each of my 4 active hubs. They are all connected today, each with a smallish set of devices. 10, 10, 6, 12 is the device count for my 4 "Production Hubs." 8 devices are connected via Homekit Integration from my "Development" hub. Homebridge is down to small numbers as I slowly peck away at the device list: 17 devices. So that's 46 devices using Hubitat Homekit Integration and 17 using Homebridge. I only select Actuator devices. I do not select Sensor devices. Yes, some Actuators have a sensor too so Homekit sees both, but my intent is to onlyhave devices on Apple that I might want to control.

I've tried to figure out how my situation can be so stable, yet others say variations of "it hardly ever works". There are only two factors I can think of, and neither seem shattering :slight_smile: First, I've been attempting to use HomeKit for 5+ years. It's gone from unstable to stable over that time. The two biggest events are, the Hombridge rewrite by Dan.T and Apple's big update (IOS v16.4 in 2023). Second, I have what I consider a tiny number of devices per hub. Others, with a single hub can't do that obviously. I have no idea if there's any validity to this one because Homebridge was fully stable for me, long before Hubitat released their HomeKit Integration and I had everything going through that one path.

All 5 of my hubs were rebooted about 19 hours ago to the latest platform across a 2 hour period. In other words, I've had 5 opportunities to experience what you experience in the past day. I never had any sign of a problem and when I've looked, while typing this message, all 5 hubs and Homebridge are communicating perfectly.

But again, it should be working well for you, just like it does for me.. you are correct in asking for ideas. Sorry I have none. :frowning:

1 Like

This has been the case for me as well. I have to reboot my hub 2-3 times a day.

Check for any devices you have shared which might be sending out of range values. Examples would be something reporting > 100% battery, or a temp sensor reporting something like -2000 degrees. You can check the event history on devices and scroll through to look for any suspect.

You could also go into the HK integration app and remove any attributes you are not using from devices. Like if you have a switch with power reporting but you don't care about the power values being in HK then remove everything but the switch state.

1 Like

Update - I just did a simple test with a virtual temp sensor. Looks like min is -40 F and Max is 414F. However, setting it to out of range values just results in the min/max being displayed in HK but the connection does not drop. So not a definitive result there, I was hoping to be able to break it on command. I tried -2000, -20000 and 68500

I will say this has gotten a lot worse. I just don't know what kicked it off.

1 Like

I've removed any virtual devices or anything reporting temp or extras. No real change. The other thing of note is that restarting the integration mostly doesn't fix it. A reboot is required now.

1 Like