I don't think you have any issue - 2% of uptime is barely anything. My own installation runs at about the same, while things like Hue Bridge and Echo Speaks automations use far more CPU time.
I suggest you check with @bobbyD in Hubitat Support to see if there is a way to dial back the "Severe Hub Load" alert frequency/limits.
And FWIW, I do run all of my cloud-connected devices on a secondary hub (eg. Ecobee Suite, Echo Speaks, Hue Hub, SONOS, iAqualink, etc.), but from the metrics that are newly available, it's clear that they all could run on my primary hub (I keep them separate because of the cloud latencies that can sometimes be lengthy).
I was also debating on moving cloud connected services to my old C-4. But I have seen very little impact for having Ecobee, Echo Speaks, Tempest Weather and other various weather API's, IFTTT, etc. on my primary hub. I have yet to see any alerts from the hub load.
I wouldn't move Ecobee Suite to a C4 if I could avoid it. ES does use a lot of CPU time to parse through the over 300 attributes presented by the Ecobee API, and the C4 processor is slower than the C5/C7. If you aren't having any problems, I suggest leaving things as they are...
Also, you shouldn't need to increase your cycle times to 10 minutes - that could actually make things worse (a higher probability that more things will change and need to be updated to the devices). 1-minute cycles should work just fine... I honestly think the "Severe Hub Load" alert is misleading, unless you have LOTS of other apps & devices.
Would you mind posting screen shots of the top of the Device stats and App stats reports so I can see for myself the scope of the overhead? Best if you turn on ALL of the Display statistics options, and try to capture the top 5-10 devices/apps listed?
Your stats look perfectly normal, very similar to my own stats on two different Hubitats (1 with 1 thermostat, the other with 3). Adding everything I can see together, the total Ecobee Suite is using less than 2% of wall clock time.
FWIW, At 10 minute cycles, your vents could take up to 20 minutes to react to thermostat changes, making vent changes sluggish at best, or useless. I always recommend 1 minute cycle times when using the Smart Vent helper.
I expect that changing to 1-minute cycle times will add minimal additional compute overhead, but whatever it is, that will be the price of automation. Since your total system is using only a fraction of available CPU time, the added overhead isn’t going to slow down your system noticeably. And if you get alerts, I suggest contacting Hubitat Support - the CPU alerts are a new feature, and they may need to tweak the settings a bit. @bobbyD in Support is very helpful...
Hey just wondering what folks are using for the log size for the Ecobee Thermostat device? I have the defaults on mine and have the warning showing up that my database is growing:
Any chance of a setting in the app to adjust these values on the sensor and thermostat devices its added? I just updated mine (2 tstats, 13 sensors) and it was a bit tedious.
I am not aware of any means for an app to control this. The latest release of Hubitat will alert you if the database gets too large, and then will offer you a means to change this default globally. There is also a new app provided by Hubitat that allows you to edit preferences for multiple apps/devices. If those don’t work, you might want to make a suggestion to the Hubitat team.
I recently setup a Ecobee Suite Contacts & Switches Helper app to turn my thermostat off when a group of external contacts are open.
I have two questions:
Is it possible to add a restriction to the helper app (or through another means) to only run the helper app when the hub is in a certain mode (for example: Day and Evening)?
Is it possible to only have the helper app run if the a sensor is reporting a temperature (via a PWS) above the current internal temperature?
I'm sorry, but these are not features of this Helper.
I workaround would be to create a Rule Machine Rule that turns on/off a virtual contact sensor based on the conditions you desire, and then to have the Helper handle turning on/off the HVAC whenever that contact opens/closes. Note, however, that you could simply turn off the HVAC yourself from the Rule...
The error messages that start with 1xxx refer to connection problems on sites that use the Cloudflare proxy. One of them is the Error 1020 Access Denied. This indicates that you've violated a firewall rule and your request is blocked.
Ecobee has identified it as an issue upstream, so hopefully we won’t have to log back in once it’s fixed.. Depends on if the fix impacts the refresh token.
