Looks like there was a error in the API call to Ecobee. I haven't seen a Error 500 in a while but when their API is having issues, I do get errors like that. How often is that message showing up?
Well, the high CPU usage has gone since the thermostat app was removed.
With the thermostat app, I really liked the ability to use any of my temperature sensors to pool an average per HVAC zone. There isn't a way with the Ecobee Suite to use non-ecobee temp sensors, is there?
1 Like
The Ecobee Suite doesn't provide the ability to use other sensors. You can through rule machine do some math but my experience with working with thermostats and home automation is to let each platform do what it can do best. With HVAC I tend to leave it do most of the work on the thermostat. And only use the Hubitat as a sensor reader for other automations or to override the current comfort settings if say we have guests etc.
This question may be a bit naive on the architecture of Ecobee Suite but here goes....ecobee has served me notice that my Gen1 Smart Thermostat Model #: EB-STAT-02 wll no longer be able to connect to their servers after July 31 2024. I will no longer have access to it via their apps or web. It will continue to function as a standalone device.
My question is will this have any bearing on my ability to query and control the tstat via Ecobee Suite (or the native Hubitat device manger)?
The native and Ecobee suite integration use the API from Ecobee cloud services. Once they disconnect the Gen 1 devices you will no longer be able to read and control the thermostat from Hubitat.
Thank you. Confirms my realization that I will have to start my search for a smart thermostat more advanced than what ecobee currently offers. This gen1 tstat has support for multiple stages along with multi fuel source heating devices. The programmable temperature differentials between stages suits my need.
That's a jerk move on their part unless they disclosed - prior to purchase - that you are renting access for X years.
I don't want to sidetrack this thread but if you watch Louis Rossmann's videos you will see he has been crusading against not owning anything due to backing services being shut down and for right to repair.
A question about the timing of mode changes:
I have Modes programmed on my Ecobee, and have it set to trigger the appropriate mode based on the settings of my home alarm - with HE being the intermediary between the Home Alarm & Ecobee.
It all works great, basically I have my alarm trigger a change in the "Mode" and have Ecobee Suite read the "Mode" setting on the HE to set the appropriate Mode on the Ecobee.
However, I've seemingly found a small flaw in this. That is, that Ecobee seems to clear the current program before setting the new program. This causes the HVAC to kick on for 30 seconds before setting back off, and creates undo use of the HVAC.
See the following log:
dev:1652024-07-02 07:12:54.843 AMinfoThermostat Program is Hold: Home
dev:1652024-07-02 07:12:54.598 AMinfosetProgram(home) for EcobeeTherm: Upstairs (XXXXXX) returned true
dev:1652024-07-02 07:12:53.737 AMinfosetProgram(Home) for EcobeeTherm: Upstairs (XXXXX) - holdType: indefinite
dev:1652024-07-02 07:12:53.686 AMinfoThermostat Program is Home (resumed)
dev:1652024-07-02 07:12:53.682 AMinforesumeProgram() - No current hold
dev:1652024-07-02 07:12:52.305 AMinforesumeProgram(true) - succeeded
dev:1652024-07-02 07:12:51.916 AMinforesumeProgram(Upstairs, true) for EcobeeTherm: Upstairs (XXXXXX) returned true
You'll see it issued a "resumeProgram" before a "setProgram", and didn't just issue a new "setProgram" to override the first.
Any ideas on how to avoid this issue? Is this ultimately a bug in EcobeeSuite?
@storageanarchy Flair has now released an API for their vents. And @ljbotero has written the code to utilize that API and control the vents. Would you consider integrating this into the Ecobee Suite at this time?
I noticed when my ecobee thermostat goes offline from the network or powered down, and stays offline for an extended time, the values on my C8 dashboard still shows the last known ecobee temperatures and other values from the ecobee.
How can I get the values on the dashboard to show offline or ???? instead of a stale value values when then this happens? I do understand I can monitor the " * DeviceWatch-DeviceStatus : offline" for an alert.
Hub migration issue
After migrating to a new hub, my thermostat devices disappeared, interestingly, the standalone SmartSensors were kept!
Since the thermostats were used in automations and dashboards, and I have 5 of them, it took me a while create new devices and get my automations and dashboards running again.
Would it be possible to fix this issue?
Hi there,
It's been a few years since I installed the Ecobee Suite Manager. When I initially set it up using the app, I believe it created prefixes on my devices in the Device Label, like:
- EcobeeSensor: Back Hall Sensor (FFNY)
- EcobeeSensor: Ecobee Thermostat Sensor (Thermostat)
- EcobeeTherm: Ecobee Thermostat
I'd like to change these names, specifically by replacing the ":" with a "-". Is it possible to do this without affecting the app or child apps in any way? Bottom line: would making this change cause any issues?
Thank you!
Couldn't you just change the device name for each device?
1 Like
That's exactly what I'm aiming to do 
! As I mentioned earlier:
I'm just trying to practice good smart home configuration methods without triggering a wholesale Armageddon. No one wants their lights to start flashing Morse code or their thermostat to launch a countdown 
!
I've noticed that the speech notifications aren't working correctly. I used to have notifications set up to let me know when an open contact turned the system off. It would report to an echo device and the ecobee speakers. However, it seems like they have stopped working correctly. I get an error message saying, "Simon says skill isn't working anymore." Has anyone else experienced this issue before? Thanks!
Can anybody help me understand how each of the algorithms for Smart Circ and Smart Humidity work? I get them in concept after reading the documentation. But I can’t find the actual calculation logic for estimating fan circ minutes per hour and humidity setpoint, respectively.
Appreciate any insight from those who may know.
Hey @storageanarchy ,
Thanks for what looks like a great driver -- came across this while I was wishing I had higher temperature precision out of the native driver.
Unfortunately I haven't been able to get any devices to appear! I saw in the README that it will take 5-10 minutes+, but it's been much longer, and I'm getting null pointer exceptions during polling that makes me think it'll never succeed. Here's a log excerpt of polls. Happy to provide more logs if you want them.
app:341 2024-09-08 06:57:02.427 PM error java.lang.NullPointerException: Cannot get property 'device' on null object on line 5037 (method pollEcobeeAPICallback)
app:341 2024-09-08 06:57:01.326 PM info Requesting ( equipmentStatus settings program events audio capabilities location alerts runtime extendedRuntime sensors weather ) for thermostat Bee (415505801999) - [false]
app:341 2024-09-08 06:57:01.324 PM info Polling 415505801999 (forced)
app:341 2024-09-08 06:57:01.197 PM trace Checking for updates...
app:341 2024-09-08 06:56:01.156 PM trace prior poll not finished, skipping...
app:341 2024-09-08 06:55:29.099 PM trace atomicState.settingsCurrentSensors == ecobeesensors: No changes detected!
app:341 2024-09-08 06:55:29.097 PM trace sensorsPage(): atomicState.settingsCurrentSensors=[ecobee_suite-sensor-rs2:101-35RH, ecobee_suite-sensor_tstat-ei:0-Bee, ecobee_suite-sensor-rs2:100-35RK] / ecobeesensors=[ecobee_suite-sensor-rs2:101-35RH, ecobee_suite-sensor_tstat-ei:0-Bee, ecobee_suite-sensor-rs2:100-35RK]
app:341 2024-09-08 06:55:28.556 PM trace ====> getEcobeeThermostats() entered
app:341 2024-09-08 06:55:28.535 PM trace ====> getEcobeeSensors() entered. thermostats: [ecobee_suite-thermostat-341.415505801999]
app:341 2024-09-08 06:55:02.622 PM error java.lang.NullPointerException: Cannot get property 'device' on null object on line 5037 (method pollEcobeeAPICallback)
app:341 2024-09-08 06:55:01.365 PM info Requesting ( equipmentStatus settings program events audio capabilities location alerts runtime extendedRuntime sensors weather ) for thermostat Bee (415505801999) - [false]
app:341 2024-09-08 06:55:01.363 PM info Polling 415505801999 (forced)
app:341 2024-09-08 06:55:01.222 PM trace Checking for updates...
app:341 2024-09-08 06:54:01.169 PM trace prior poll not finished, skipping...
app:341 2024-09-08 06:53:02.928 PM error java.lang.NullPointerException: Cannot get property 'device' on null object on line 5037 (method pollEcobeeAPICallback)
app:341 2024-09-08 06:53:01.436 PM info Requesting ( equipmentStatus settings program events audio capabilities location alerts runtime extendedRuntime sensors weather ) for thermostat Bee (415505801999) - [false]
app:341 2024-09-08 06:53:01.433 PM info Polling 415505801999 (forced)
app:341 2024-09-08 06:53:01.251 PM trace Checking for updates...
app:341 2024-09-08 06:52:01.161 PM trace prior poll not finished, skipping...
app:341 2024-09-08 06:51:13.183 PM error java.lang.NullPointerException: Cannot get property 'device' on null object on line 5037 (method pollEcobeeAPICallback)
app:341 2024-09-08 06:51:11.434 PM info Requesting ( equipmentStatus settings program events audio capabilities location alerts runtime extendedRuntime sensors weather ) for thermostat Bee (415505801999) - [true]
app:341 2024-09-08 06:51:11.423 PM info Polling 415505801999 (forced)
app:341 2024-09-08 06:51:11.367 PM trace Checking for updates...
app:341 2024-09-08 06:51:11.223 PM warn isDaemonAlive() - (poll) has died
(I don't understand the line number reference, line 5037 is not in pollEcobeeAPICallback in the Ecobee Suite Manager app code...)
I have an Ecobee3 Lite running firmware 4.8.7.226 and two sensors, and polling interval is set to 1 minute. Any idea what's going on?
Update: Thought I'd see if I could narrow down the issue of my NullPointerException, so I disabled all of the sensors, and the app correctly created the device for the thermostat! Progress!
Then I updated the app to use the two physical sensors I have, and that produced a different NullPointerException:
app:3412024-09-08 08:40:41.289 PMtraceprior poll not finished, skipping...
app:3412024-09-08 08:39:42.645 PMerrorjava.lang.NullPointerException: Cannot invoke method generateEvent() on null object on line 1919 (method pollEcobeeAPICallback)
app:3412024-09-08 08:39:42.588 PMinfoPolling 415505801999 completed
app:3412024-09-08 08:39:42.451 PMinfo18 updates for 2 sensors (Bedroom, Rich's Office)
(My theory was that it was gonna be the virtual sensor for the thermostat itself that ran into a problem, but hopefully that new error is helpful?)
So I went back to no sensors, and then only enabled my "Bedroom" sensor (35RH) and that succeeded!
Then added Rich's Office (35RK)... success!
Finally, added the thermostat itself back in as a sensor... and that worked too!
So I guess I'm fine now, but I'm also not using the app for anything yet, so if you'd like me to do more messing around to troubleshoot, please let me know!
Unfortunately we are on our own as far as support goes for this plugin. The developer seems to have gone MIA and hasn’t responded in months. Best of luck to you on using this, but it does still work and works well. I’m using it myself.
2 Likes
