"No response" using new HomeKit integration (beta)

I only have a small fraction of my devices exposed through the HE HK beta integration - enough to allow me to observe/test/etc., but not enough where any issues impact the family, basically. The rest are still exposed through Maker API/homebridge. I will say this: there's a fair amount of ... instability? ... in the HK env, generally, right now. I think Apple pulled the HK 16.2 arch upgrade (again?) - so that's certainly indicative of some issues - definitely a challenging time for HE to be putting their integration out! My current plan is to just not touch anything ... remove Apple devices from beta update channels, just wait for stable channel updates to come through with hopefully good, solid releases. I'm not even putting my ATVs back into HK for now.

I've had to nuke & re-setup my home 2x since 16.x stuff (mostly related to 16.2 beta/arch upgrade/invites/etc.) - I don't want to do that again (it's a PITA, even with the Controller for HomeKit backups), so I'm going to play it safe for now :slight_smile:

Yes I just moved 35 devices back to Homebridge. I fought with Hubitat integration from day 1, and Hubitat even poked around the engineering logs on my hub. But it was WAY too fragile. I'm throwing in the towel, which is sad. I really wanted the native integration to work. My dozen+ child bridges on Homebridge are 1000% rock solid, even with 16.2 and the new homekit architecture.

1 Like

Hmm, 63 devices exposed to homekit fine. Running 6 homepod minis and an apple tv, 16.2. It's been pretty solid.

Mine had been for weeks but yesterday it was "no response" most of the day. Reset integration and reboot hub and close and relaunch app did nothing. Today it finally started working again no rhyme or reason.

As @jrh1194 mentioned a couple of posts before, the cable connection of Hubitat (instead wifi) to the router directly solve his issue with "no response". I got a cable connection directly hub -> router from the beginning, and still experiencing issue.
In my case, I got "no response" let's say once a day then I click "restart integration" and everything back to normal.
@gopher.ny i got a small 2 small ideas/suggestions:

  1. why don't you add a couple of lines of code restarting HK integration app automatically let's say once per hour (or 2 hours), or maybe adjustable by user period of time? The restart takes only 1 second or two and every back to normal, nobody will even notice that
  2. is it possible to create watchdog checking connection with HomeKit automatically even every second or minute, and in case of "no connection" restart integration automatically?

I'm not a professional coder so this is just an idea, what maybe will work? :thinking:

I'm inclined to do that just based on the amount of "everything works after integration restart" feedback :slight_smile: Next build.

4 Likes

O'right, let's hope I'm not the only one "after restart works" boy? :thinking: :smiley: ...guys any others?

1 Like

Isnt that a bit like camouflaging the elephant in the room?..
Obviously the integration shows potential but is not yet mature.

I have 6 childbridges on my HK, varying from official bridges like Hue to custom bridges from HomeBridge, Hoobs and HomeAssistant. They are all stable……

Dont get me wrong, i got my C7 just for this, being able to beimg my zwave and zigbee devices to HomeKit and it does just that…. But it needs some love and time improving the integration in stead of putting make-up on mannequin

Very similar situation here. I have two HE/Homekit installations in two separate locations. Both work extremely well for 3-4 days at a time. Then, BAM, no response on one or the other (sites are not network connected in any way). 100% of the time clicking' restart integration' resolves the problem(s) and I'm good for another several days.

I've tried really hard to correlate these 'no response' events to something happening on site, but no luck thus far.

It creates better user experience while I'm looking for the root cause. Doesn't mean I'll stop looking :slight_smile:

3 Likes

What about some sort of polling? If x gets no response, restart integration. Repeat every 10 mins? (Not sure if that's doable or not)

1 Like

Exactly what I meant :facepunch:

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.

3 Likes

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.

1 Like

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. :face_with_raised_eyebrow:

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.