@hasshoolio wrote:
I’ve always glanced over any homekit related news, posts, and bugs but I just recently read about the homekit_connector in another read about ecobee. I added my ecobee using it to play around. This ended up being rather fortuitous because the upgrade to 102.3 broke the ecobee cloud component.
And now I’ve noticed a few things…
- The state changes and state information appears immediate instead of the 5min poll of the cloud component. (although I still wish we could have realtime motion info from the sensors)
- The card for the homekit_connector doesn’t have exactly the same controls. Is this an HA side thing that just needs updated or a difference in available ecobee apis between homekit and cloud?
- I’m going to dig into point 2 a bit but I have yet to find per-homekit accessory info like we have for the direct-to-components like myq or ecobee.
The first point seems huge to me. It offers local/direct access to things instead of relying on the Internet which is a core benefit of home assistant. It also seems like a sustainable compromise between us wanting local api access to devices and vendor’s tendencies to avoid that and instead offer a ‘service’. If this is as good as it seems, I may consider picking up a homekit enabled myq bridge to avoid the Internet for garage door control too.
What has been other’s experience when moving to the homekit integration of components that would otherwise be cloud/internet-based?
Posts: 1
Participants: 1