I have switched from using a Hubitat cloud-based integration with Ecobee (either the built-in one or Ecobee Suite) to using a completely local Ecobee integration. The solution I use does require an always on instance of Home Assistant. If you have HA already running, then you can simply use its "HomeKit Device" integration to add your Ecobee thermostat(s) to HA. Then, use the Home Assistant Device Bridge (HADB) to bring the thermostat(s) into Hubitat over your LAN. (Note: One does NOT need an Apple iPhone device in order to use the Home Assistant HomeKit Device integration.)
This provides a 100% local LAN-based integration between Ecobee/HA/HE that has been working very well for my needs. Just be aware that this solution does not provide as full featured a solution as the Ecobee Suite does.
Good suggestion. I am running a Home Assistant Green and already using the HomeKit Device plugin for Aqara and Abode. Will look into that as a way to offload some more from the hub.
On second thoughts I might leave the Ecobee on the Hubitat.
I use Home Assistant for playing around but I try not to use it for anything I depend on. Breaking changes occur pretty much monthly and I don't want my thermostats to suddenly go down and then have to spend all of the time figuring out what is wrong with it to get heating and cooling back up and running.
The latest Home Assistant update broke my iCloud tracking. A month ago it was the Aqara that I am using for the FP2's. A month before that it was the Hubitat integration and it required a HACS update, and I can't figure out how to get the HACS section to notify me of updates.
I will install the HomeKit connection to play around with but I need to solve my speed problem and keep as much, if not all, integrations running on my Hubitat as it is far more reliable than Home Assistant.
just to add latest update.
upgrading from 2.3.9.158 to 2.3.9.160
The hub with just LAN devices, hub mesh, etc, took about 4-5 minutes to update.
The hub with my Z* devices, hub mesh, and rules took about 21 minutes.
I started the "main" hub update before backing up and updating the LAN one, and the download part was at 25% on main hub when the UI booted up on the LAN.
How long does it take you to open a rule for editing, change the title of the rule, etc? I am seeing consistency between your update times and mine and curious if this carries through to other hub activities? Thanks.
It's a second or so on my C-8 Pro. I haven't noticed any delays in the UI or interaction with the hub. It's just the update that takes so long. Same thing on the previous iterations of the "main" hub (C7, then C8 before the pro).
My main hub, the C8Pro, did start originally as a C5, then C7, then C8 and now C8Pro. So we have that in common.
Roughly how many rules do you have? I am wondering if the number of rules you have impacts the speed on the UI. The other area I am looking at is the apps I have installed - in case one of those is slowing down the UI. Some have posted references to certain apps causing this issue.
Over the years I've switched the setting back and forth a couple of times, IIRC. Seems like the connection negotiation between the hub and router can get "stuck" and changing the setting breaks up the traffic jam. Right now my C8 is on Auto and my C7 is on Fixed and both have good/fast connections. YMMV...
Updating from .160 to .162 after changing the network back to auto negotiated was quick. So no idea why it works better now than it did however many releases ago when troubleshooting steps indicated switching to 100 was a possible remedy. It might have been on a previous hub, so ¯_(ツ)_/¯ . But was great this time around.
As my slowdown seems to be hub wide I assuming the update speed is related to this and not the network settings. But I am going to play around with the network settings to see if this improves.
