Unfortunately, anything that hits during that restart will malfunction, resulting in random, rare, and non reproducible failures. This will essentially create "flakiness" for those users where the integration is already working correctly.
@gopher.ny, if you do implement this, please make it an opt-in rather than a default. Thanks.
Understandable, it's beta anyway let's make the automatic restart optional, only if you want to use it, thick the box - easy
Restart doesn't fix mine until hours later. No clue why.
What about instead of an automatic restart every hour you could publish a button on a Hubitat dashboard somewhere that allowed us to re-start the integration? That way, it wouldn't create any of the phantom issues mentioned above but gives those of us that are away from home a way to jump start the HomeKit Integration.
It's a good idea also, to make a kind of virtual "HK app reset button". Anyone for who this solution helps could set their own automation and use this reset button within the time period that suits him and in the meantime, @gopher.ny can further improve the software.
Such a temporary solution I think it would make life easier for many people.
Tonight my integration gets "no response" mode again. After this morning's integration reset everything returned to perfectly normal. 
Mine's kinda weird. Every few days I get the no response. But as soon as I open the app it starts working again. I don't even need to push the restart.
Are you running a hub, or just using your phone?
I have 4 Mini's and an Apple TV.
Should clarify. To make sure it wasn't a coincedence I watch the Home app on my phone for several minutes while it is saying no response. Then I go to my computer, open the HE app and bingo it almost immediately starts working. Have verified this several times. I can see maybe a coincedence once in a while, but it is very consistent.
I just had this happen Sunday morning (when I was at work) and then again this morning. Today it was only on one hub, but Sunday it was both hubs and HomeBridge, except for one child bridge (MyQ). Remotely restarting my HE Homekit beta apps fixed the Hubitat bridges, and the Homebridge ones resolved their issues while I was on my way home. Very strange since this hasnāt happened before with my setup.
Apple released an 'updated' 16.3 public beta today for those that might have updated to that beta prior to Apple pulling the 'architecture update'. Loading as we speak to see if there is any change in the 'no response' issues. 
Mine are updating to 16.3 as well but I haven't had a no response issue since the relaxed security option was implemented
My integration refuses a virtual dimmer. Once i expose it to HomeKit, everything becomes unresponsive. Once i remove the exposure, all is back to normal.
@gopher.ny any thoughts?
Are you using the built in VD driver or a user one?
I got nuthin then lol. Definitely an @gopher.ny issue. I know when I used a virtual button, homekit said it wasn't supported. Thought that was weird. I also assume you have relaxed security on?
Never changed the option Rick, i have changed the virtual device triggers. Thats why i thought to mention it here since i might have stumbled on some āout of rangeā or other issue that might help solve (part of) the puzzle
Well, if you don't have Relaxed security on, I would turn it on. That's solved a lot of problems.
Sorryā¦ i was unclear thereā¦ relaxed security has always been on, never changed that
Ahh, gotcha...
If you do a hub reboot will that automatically do a HomeKit restart?
Download the Hubitat app
