...and thank you for the update.
@gopher.ny Spoke too soon. Turned on TV which triggers a few Homekit accessories. 3 Hubitati accessories in that Homekit room all went "no response".
Update: Now all 28 accessories from the Hubitat are no response.
Looks like Iām in the same situation. Had to restart my HomeKit integration to get rid of the no response this morning.
So I re-IP'd my Hubitat hub to a static IP, for reasons unrelated to Homekit. Home app was still showing accessories offline, so I did the Hubitat beta nuclear option of resetting the QR code. I'm now unable to pair the Hubitat hub with Homekit. I get "Accessory not found". I removed the Hub from the Home app.
I've:
- Rebooted the Hubitat hub multiple times
- Reset the QR code a couple of times
- Restarted the integration a few times
- Ensured relaxed security was enabled (also toggled on/off)
It gets stuck at "connecting to bridge".
Ideas? Hubitat 2.3.4.123
This looks as if the home hub (Apple TV or HomePod) can't connect to the Hubitat hub. Can you ping the home hub from Settings - Network setup - Network test page?
Pings work just fine to both Apple TVs. Just for fun I pulled the power on my two Apple TVs in case they were confused. Still did not help.
Ok so I got it working, but not sure how. First, it's no surprise that my Hubitat is on a private IP address on my home LAN. It was on DHCP for the longest time, but I was re-doing my firewall and stuff the last couple of days and moved it to a static IP on the same (and only) subnet in my house. That's when generating a new QR code and adding to Home started to fail.
Tonight I was cleaning up my NextDNS (cloud DNS provider) settings, and added an internal FQDN for my hubitat hub (hubitat.home.local) that resolves to my private LAN IP. This way I can access Hubitat from my LAN via http://hubitat.home.local. Plus I have a few webhook calls to Webcore that did use the Hubitat IP but I've changed those over to FQDN as well.
I then logged into the Hubitat UI via the FQDN, scanned the QR code again, and viola! Home app connected to the Hubitat bridge. I have no idea if Homekit uses IPv4, IPv6, or FQDNs when available to connect to hubs.
Now I don't know if these changes actually fixed it, or just a coincidence. But thought I'd share.
Just to be clear for those not familiar with NextDNS, I'm NOT opening any external ports in or outbound for Hubitat. It's just a DNS resolver and returns the private IP address of my Hubitat hub.
Since being able to add Hubitat back to Homekit, 99% of the time all Hubitat accessories have been no response. Relaxed security is, and always has been, on. All Homebridge accessories are rock solid with no blips.
1 Like
The issues with setting a static IP on the hub generally revolve around name resolution so by adding a name resolver you appear to have corrected that and allowed the hub to participte again.
Right, but Homekit still has issues since all 27 Hubitat accessories have been no response since I was able to add them back into the Home app.
I have the same issue. The HomeKit integration stops responding. The devices can be operated from the hubitat interface, not from the homekit side. Restarting the integration works, bit only for a short period of time and the the integration has to be restarted to get it to work for little under an hour or so.
Do you have relaxed security turned on? Also are you on the latest platform? Are you running 16.2 with the new architecure on your iphone and homepod/apple tv?
Yes relaxed security is on, yes the 16.2 architecture update is implemented and yes i was running the latest update as up to 25th of december.
I will be monitoring the behavior of the update i received today (half an hour ago)
Thx for responding at least. Will post my findings here after a few days.
1 Like
@gopher.ny Hubitat bridge in Homekit seems more stable the last couple of days...don't think I've seen a no response episode (but haven't been watching it like a hawk). I'm still not presenting any motion/LUX or presence sensors, which seemed liked they caused problems in the past. Now on 2.3.4.127. Were any issues found and fixed with motion/lux/presence sensors that would let me try those again?
After Apple withdrew the 'update to new architecture' I wonder what's happening. Has anyone seen anything reported for a fix (from Apple)? I must be one of the lucky few. I updated phones, Apple TV's, HomePod Mini's to the latest version to enable me to do it, but never clicked that self destruct button after reading a few comments regarding issues on this forum.
Apple just withdrew it a few days ago, and placed it on an internal watch list of major issues. Apparently software going on this internal watch list is extremely rare, and usually reserved for systemic hardware problems. GIven the complexity of Homekit, it wouldn't surprise me if its a few weeks or month or two before Apple comes out with a public fix. These issues were happening to people during the beta, so I think it's real egg on Apple's face that they didn't listen to the beta tester issues and went GA with it.
Personally going to the new architecture and 16.2 was completely flawless except for Hubitat homekit. Homebridge, Scrypted, and all my other hubs/devices are rock solid.
2 Likes
There are so many 'my devices are showing not responding' posts on the community at the moment. It'd make sense for Hubitat to state that the issue is for the most part linked to Apples Homekit architecture update and requires their fix - the Homekit app is in beta after all...
There was an issue with lux sensors reporting 0.0001 level instead of 0, which is fixed in the 2.3.4.127. While my setup never had the issue described, this could've been the cause.
IMHO there are two issues here:
100% of my No Response issues are from the beta Hubitat integration. I have a dozen Homebridge bridges, Scrypted, Flic Hub, Hue hub, etc. and not once have any of those had issues with the Apple upgrades. I even use the Hubitat to Homebridge app, and all the Hubitat devices through Homebridge are also rock solid. So I'm 99% sure my no response issues are due to Hubitat Homekit code problems.
Now that being said, there ARE most certainly A LOT of people with devices with 16.2 new architecture that are very much borked. Clearly Apple recognized they botched the roll out with bad code. All of those 'no response' issues have nothing to do with Hubitat. And certainly Hubitat users could be seeing 'no response' due to Apple code issues, not Hubitat code issues.
1 Like
Ok. I'll add all my motion sensors back to Homekit via Hubitat .127 and see what happens. I'll leave out the presence sensors for now.
1 Like