C7 - Release 2.3.9.162 - HomeKit stops working

[WarEagle]

HomeKit is still failing on this release after a day or two with all Z-wave devices shown as not responding and requires a reboot of Hubitat. No other changes to my network. HomeKit used to be rock solid back around 2.3.9.138, if memory serves me.

[Guffman]

Others are having the same experience with recent Hubitat releases, see this thread:

Done with Hubitat Homekit for now

I gave it a fair shake, moving all of my devices from two locations (and hubs) from Homebridge to the native Homekit support on day one of availability. Moving it all back to Homebridge today. [IMG_1338] I've read most posts here to figure out how to make it work reliably but it's just too brittle. Even with hourly restart and various other "fixes", even with just one device (Garage Door), it eventually shows "Not Responding" for the device(s) and Bridge. Nothing fixes it, short of a complete …

and my specific issues here:

Done with Hubitat Homekit for now

Update: Since I have a Homebridge instance already setup for Ring stuff, I used the Homebridge plugin for Hubitat - authored by @tonesto7 - to re-map all of the devices that were configured in the built-in Hubitat HomeKit app. I then deleted the HomeKit app on both my C-7 and C-8 hubs. Been using this for about 48 hours now, and no more "No Response" errors in the IOS and MacOS Home apps. This is the only change I've made to my overall home automation network. Prior to the availability of the…

@bobbyD , if it would be helpful to provide more info to assist in diagnosis, please let me know.

[bobbyD]

@WarEagle

HomeKit used to be rock solid back around 2.3.9.138, if memory serves me.

Would you be able to help us narrow it down by reverting to previous known "rock solid" version from the Diagnostic Tool to confirm that your HomeKit experience remains as solid as it used to be? If it does, then we can investigate what has changed. If it doesn't, then we would know that the recent updates aren't the problem: Hubitat Diagnostic Tool | Hubitat Documentation

[jtp10181]

They may need to know more about your setup.

Do you have any apple Home Hubs? (ATV or Homepod's)? If so, what kind and how many?

[WarEagle]

@bobbyD I upgraded to 2.3.9.164 yesterday and so far I haven’t seen unresponsive devices in HomeKit. I’m unsure if there is any difference between .162 and .164 regarding HomeKit but I’m going to let it run for a few days and see if it remains stable. The hourly restart is still enabled at this time.

[WarEagle]

I have one ATV-4K on my network connected via GbE.

[bobbyD]

@WarEagle

any difference between .162 and .164 regarding HomeKit but I’m going to let it run for a few days

Please keep us posted. There was a change to improve HomeKit connectivity that was added in .162. No other changes have been made post 162, though our engineers are still exploring other ways to make HomeKit accessories more resilient to potential network disconnects.

[WarEagle]

@bobbyD The HomeKit integration was working fine until today and then devices displayed the “No Response” message. I see that 2.3.9.166 “Tweaked Bonjour announcements to improve HomeKit connection stability,” so I’m going to uprgrade from .164 to .166 and see how that goes.

[jrvisconti]

I’m having the same problems with HomeKit but I was running 166.

Every 6-12 hrs all the devices become unresponsive until I reboot the hub. Restarting HomeKit doesn’t resolve the issue.

Today I rolled back to 162, so far so good.