I am looking for some advise on how to handle exiting and entering away mode. Currently I have Ecobee Suite Mode/Switches/Program Helper for away mode trigger as location mode change. I use the Mode Manger Legacy app to set mode from the presence base on my family's phones. This has worked well until recently when my family was out out town and we had some extended family staying at our home. After we left I though I could use the Hubitat app to set the mode to home, but that did not work, it kept resetting to away. I also though the Ecobee sensors would set the mode to home when they were triggered, but that did not work and they are not an option as a presence sensor in the Mode Manager app. What is the best way to handle setting the mode to home when people are in the home if my family's cell phones are not present?
The simplest solution is to create a new Virtual Presence Sensor, and coneect it to the home/away logic like your phones are. But instead of detecting presence, you would manually set it present while the guests are at your home. The reset it to not present when they leave.
You won't have the full tracking of their presence, but it should be enough to keep the Ecobee running its scheduled programs...
I am using the smart humidity on version 1.9, the set humidity variable appears to change way more often that it should. I have it set for the avg low temp of the past 3 days. The set value has changed almost ten times in the past 12 hours.
Has anyone seen this and or can they suggest why this might be happening
This a very simple solution. Thank you.
Hello,
Does anyone have a working configuration example for the ' Smart Mode, Programs & Setpoints Helper'?
It looks like it should work but the setpoint doesn't update.
Logs:
It was suggested that I come over here due to the relation of suite manager and a recent 'hub load severe' error. Can anyone help?
We have a C7 and we've started getting a "hub load is severe" error. It's been happening ever since I installed the Ecobee Suite Manager (ESM). The same day I installed it, I had my first severe error that night. At that point, it was just an error though and didn't cause any other issues. Now I'm starting to have zigbee devices skip commands or commands not being sent. I'm minimally using ESM. It only runs twice per day. Once at night to put our Ecobee's into sleep schedule, and once in the mornings to resume program.
I would love to have someone offer options on how to fix this. I have about 180 devices which are about 30% zigbee, 45% Lutron, and 20% virtual devices. The remaining is a few z-wave devices mixed in (door lock and some remote switches). This setup has run for about three years with minimal issue until installing ESM.
I've gone through and deleted 'disabled' rules, removed unused devices still on the network, and uninstalled unused driver. I've disabled logging for ESM and some of the other devices that report frequently. We have two thermostats with two additional sensors for each unit. I've disabled the four remote sensors from ESM so it only monitors the two thermostats and disabled logging and messaging from ESM as well. I just don't know what else to do.
That's weird that you are getting a severe load because those images you shared show that all of your Apps are only running at 4.4% and your devices at 0.5%. Therefore, even though the Ecobee Suite Manager is responsible for 50% of your busy in apps, that's 50% of 4.4% so hardly a strain on the hub.
The same goes for the devices; the two Ecobees are 10.2% of 0.5% so ~0.05%.
I know not helpful but it is strange.
That's what strange. I won't claim to understand the logs as in depth as you've explained, but from what I could tell, there's really no reason for it to be flagging those errors. Especially with the Suite Manager only running twice per day (I realize it reports more than that throughout the day, but that doesn't seem to be an issue). Any ideas would be appreciated! I've done everything I can think of. The errors are less often, sometimes taking two days to come up rather than every night. They usually come at night as well, not sure if that spurs any ideas.
So, a few questions:
- when did you get this severe load alert? During hub reboot? Restarting ESM? Something else?
- Did you get multiple alerts, or just the one? How often?
- Did you observe any abnormal slowness in your Hubitat actions before getting the alert(s)? After? (E.g. lights turning on/off, changing tv stations
- How long after the alert was sent did you observe the stats you show?
- Which Hubitat hub do you have (C5, C7, C8, C8+, other)?
- How many thermostats & sensors is ESM managing for you?
- What is your cycle time configured as? Icff
In my experience, your situation is normal and nothing to be concerned about. The Ecobee factory alert level defaults may just be too low for your installation - I believe there is a command you can use to set the alert level a bit higher.
Copied and pasted to make sure I answered each question. 
-
when did you get this severe load alert? During hub reboot? Restarting ESM? Something else?
The Severe load alerts only seem to happen at night. Overnight. Which is when ESM is set to trigger. When all the lights turn off, the hub goes into night mode. When the hub goes into night mode, ESM triggers to set the two thermostats to sleep (which drops the temp and only watches bedroom sensors). It's not as soon as it triggers, it's at some point overnight after. ESM triggers once more in the morning to resume the program. -
Did you get multiple alerts, or just the one? How often?
As far as I know, it's just the one notification. It comes up and doesn't go away until I restart the hub. It doesn't come back immediately, but usually happens again overnight (which should be the time that the hub is working the least...everyone is in bed, no triggers or rules being run like during the day). -
Did you observe any abnormal slowness in your Hubitat actions before getting the alert(s)? After? (E.g. lights turning on/off, changing tv stations
I have noticed that zigbee commands are being skipped but I haven't been able to tell when it starts in relation to the error. I can usually tell when the error is present because that's when it starts to bog down. -
How long after the alert was sent did you observe the stats you show?
Those stats are the next morning. Probably about 8-10 hours. -
Which Hubitat hub do you have (C5, C7, C8, C8+, other)?
C7 -
How many thermostats & sensors is ESM managing for you?
I have two ecobee thermostats with two remote sensors each. So six devices. I disabled logging and removed the four remote sensors from ESM. So it's currently ESM is only managing two thermostats, and only making two adjustments per day per thermostat. -
What is your cycle time configured as? Icff
I'm not sure what this is? I see logging, polling interval, and debug level. Are one of those what you're asking about?
This is how often ESM contacts the main servers - it sends a request, and waits for a response (ie., it doesn't keep sending messages until it gets a response from the last request).
I STRONGLY RECOMMEND USING 1 (ONE) MINUTE POLLING CYCLE
(And there's no reason to remove all your sensors - they cost fractions of a millisecond each to process).
If this is happening ONLY overnight, I suspect it isn't ESM. Especially since you say it is some time AFTER ESM changes the program...
More than likely it is to do with the nightly database checks and backups that Hubitat does automatically at the time you set under Settings/Backup and Restore. You might want to look in the Previous Logs on your Hubitat for what all was going around backup time.
You could also change the backup time to something during the day, just so that you can watch what goes on when it does backups.
Finally, since a Reboot seems to clear things up, you could get an app to schedule a daily reboot an hour or so after your backups are done...
And, FWIW, pointing the finger at ESM based off of stats that are 8-10 hours AFTER the Alarm event happens, well...ummm...
I'll make the suggested changes and see how it works. Thank you for the help!
I don't mean to come across as pointing the finger at ESM, it's just the logical step. This hub has run with the same devices and (mostly) the same rules for over three years and never thrown this error. The day I installed ESM, it started with the error, daily. After removing the sensors and logging in ESM, the error lessened to every other day (still sometimes daily). Changes to ESM seem to directly affect the error rate despite it not being immediate.
I'm not saying ESM is a problem on it's own by any means, it just seems to be a problem combined with my particular setup.
I added the sensors back in for ESM to monitor. After I changed the polling interval to one minute, I restarted the hub. Within 20 minutes of the restart, I had an error of "elevated" load. Within 40 minutes of the restart, the load severe error was back. I changed the interval to 5 minutes last night around 8pm. So far the error has not come back and I've had an uptime of about 17 hours with no errors. It is showing a larger % busy time than the other apps, but that has still not thrown an error. I will continue to monitor.
I have been running ESM for a long time and have the polling interval set to every 2 minutes. Never hand an issue! I have many routines that run off the Ecobee device that I depend on and the 2-minute interval has never been a problem. I thought it was recommended or defaulted at 2 minutes. Now that the 5-minute setting is not causing any issues you may wish to leave it as is.
First of all, thanks @storageanarchy for this integration! I have been using it for years with 5 thermostats, apart from a minor problem during hub migration (sensors disappeared, had to re-add them), it has been working flawlessly!
Question: Would it be possible to populate the Hubitat device with variables for air quality data, on thermostats that support it?
Hi wondering if anyone knows how to resolve these errors?
The app and device seem to be setup correctly but I cannot issue commands to the thermostat from hubitat
This does not seem to be set up properly, and/or you are not actually using my Ecobee Suite for this thermostat (the deviceId should be a 12-digit ID from Ecobee),
If indeed you are using the Ecobee Suite, I would request that you remove everything related to your Ecobee thermostats, and then follow the Ecobee Suite installation instructions to a T - you will use Ecobee Suite Manager to actually create your thermostat devices...
Is this application still maintained? I see multiple (old) open pull requests and (old) open issues in the repository.
Asking because I'd like to add a delay option to the Contacts & Switches helper actions to prevent HVAC power flapping caused by someone opening and closing a door quickly (e.g. letting the dogs into the back yard). I've been using the Rule Machine with the build-in Ecobee integration. I have a delay of 1 minute (cancellable) before the action occurs.
Asking before I fork the repository and install my updates manually. I'd rather support the project (and the HPM integration), but if it's not maintained (I see there's 152 forks), I won't bother.
Thank you in advance.
Never mind. After RTFM'ing, I see there's already an option. I just misread the label.
