I have not used the HomeKit integration in a few revisions to notice when this happened it all by devices in HomeKit that are published my Hubitat are reporting no response. Additionally, changing my scene capable dimmers from button controllers to dimmers or switches leaves them all as button controllers still.
I have 3 Apple TVs all participating as HomeKit hubs, so a reboot of Apple TV is it so simple, as they need to be coordinated.
Is this a case where I need to generate A new key? Will doing so break all my devices already defined in HomeKit shortcuts?
Try this... open HomeKit integration app, scroll to the bottom, and enable "Relaxed home hub pairing security" toggle. If it's hasn't done the trick in 30 seconds, restart integration.
Ha! I recreated the pairing ID and re- paired the hub. I had to re andd all my devices in HomeKit, but it all work now. So, it would seem maybe something in the security changed and the relaxed mode makes it backward compatible with those of us that paired back in the early beta??? Anyways it’s working for me now. I didn’t have the patience to wait for an answer — sorry.
This Integration is really cooked but with iOS 16.2 and HomeKit being able to be upgraded to the new HomeKit Architecture matter is now used. I don’t know if natter support local mode, or require cloud to work, but it seems matter would replace all hub integrations with a single standard protocol that enables hub-hub integrations. Any plans to work on implementing matter?
I have an Apple TV and two HomePod Minis. Everything was updated to 16.2 and the new architecture and was rock steady under 2.3.4.120, even with "Relaxed home hub pairing security" turned off. Since upgrading to 2.3.4.122, it's been up and down like a yoyo with everything going unresponsive. I've tried toggling "Relaxed home hub pairing security" both on and off. I've tried restarting the integration. Nothing seems to help for very long.
Same thing here. The Homekit integration was working great until the recent updates. Now all devices are unresponsive after working for several hours. I have tried starting from scratch and adding devices all over again but they all become unresponsive.
I was having similar issues, then I tried unplugging my apple tv that acts as the homekit hub waiting a few minutes then plugged it back in. Has been fine ever since.
I've removed Mode because someone else said that worked for them. I'm keeping my fingers crossed. I have an apple tv and two HomePod minis. I've given all of them static IP addresses just in case something funky is going on there. I doubt that's it, but I'm grasping at straws.
I have modes enabled and it hasn’t caused any problems. I have noticed that unplugging or rebooting the currently active Home hub, so it changes to another ATV or HP mini seems to help smooth things out after adding devices. Devices not wanting to change rooms or names until multiple attempts are made is one thing it has helped with for me. This happens with the Homebridge integration as well, so hopefully some bug fixes will be coming soon from Apple.
I hadn't added any new devices when everything started being unresponsive. I notice that the hub has switched from the TV to one of the HomePods, so we'll see if it settles down again. I'm not using Mode on HomeKit anyway, so I won't miss it.
For room and name changes, I found that if I went in through the settings...
Home Settings --> Home Hubs and Bridges --> Hubitat --> Accessories
From there I could select a device and change the room and it would stick first time.
The hub has switched from the tv to one of the minis and now to the other mini. Every time the hub switches everything becomes unresponsive.
I don't know any way to keep the hub from switching. It pretty much stayed on the TV until the latest update. I guess that was why everything was so solid. Now it seems to like bouncing around.
Friend of mine updated to 2.3.4.122 as well, and noticed that now his HomePod is always the connected hub. Regardless of the connected hub, He stopped working completely. We will be trying the nuclear option as my system works, and I used the nuclear option last week prior to updating to 2.3.4.120. After updating to 2.3.4.122, my system is still working fine. I will update when the QR code reset is complete on his system, and we know if it fixed his issue.
For various reasons, putting my ATV on ethernet isn't really an option.
I pulled the plug on the two HPM and left it for 5 or 10 minutes until the ATV took over as the hub again. Then I restarted the integration and plugged the HPMs back in. We'll see how long it sticks with the ATV as the hub. It's seems pretty stable as long as that's the case.
Reddit has a myriad of threads regarding HPMs taking over as hubs and screwing various things up. There doesn't seem to be a way to keep it on the ATV.
Mine was OK for a day and then everything was unresponsive again.
I went with the nuclear option. My hub was giving "extreme stress" messages when I first reconnected everything. A reboot seems to have fixed that. I hope. Devices were unresponsive during the reboot — which is to be expected — but connected again as soon as the reboot was finished.
Keeping my fingers crossed. I'm not sure what was causing the hub stress. CPU was at 95%.
Thanks!
