I’m using the thermal comfort app with the expectation that it’s going to adjust setpoints based on the paremeters I’ve set. When. The thermostat changes modes I’ve seen notifications from thermal comfort suggesting it’s setting the expected setpoints, however, I’ve never seen the thermostat actually use these values, it just uses the ecobee programmed setpoints. I’m sure I’m doing something wrong but I’m not sure what.
Nope - it’s a bug. Coincidentally it was reported by the user just before your message 
Fixes will be posted momentarily…
Ecobee Suite updated on 7 May 2020 at 11:05am EDT
I’ve been holding back several minor fixes to minimize the number of updates I release, but now I need to release them all.
Fixes include:
-
Ecobee Suite Manager, version 1.8.42
- Optimized stat.settings change detection
- Better error handling for new installations
- Renamed Smart Switch/Dimmer/Vent to Switch/Dimmer/Fan (see below)
- Fix conversion error in setProgramSetpoints()
-
Ecobee Suite Quiet Time, version 1.8.08
- Fix for multi-word Climate names
-
Ecobee Suite Routines, version 1.8.16
- Fix for multi-word Climate names
-
Ecobee Suite Smart Circulation, version 1.8.10
- Fix for multi-word Climate names
- Fix settings descriptive text for minFanOnTime==0
-
Ecobee Suite Smart Humidity, version 1.8.09
- Fix for multi-word Climate names
-
Ecobee Suite Smart Mode, version 1.8.21
- Fix label display for " (Cool"
- Fix for multi-word Climate names
-
Ecobee Suite Smart Room, version 1.8.16
- Better active/inactive determinations
-
Ecobee Suite Smart Switches, version 1.8.12
- Added status to app.label
- Option to treat ‘fan only’ as ‘idle’
- Fix on/off/restore logic errors
-
NEW FEATURE! added native support for fan controllers
- After realizing that not all fan controllers support the dimmer
setLevel()command, I added support for thesetSpeed()command. - Speed is one of:
low,medium low,medium,medium high,high,off,on,auto. - Not all fanControl devices support all of these speed names, so you will have to choose based on your installed fan controller device.
- The Helper will send the requested speed, followed by an
on()/off()command if the fan controller supports theswitchcapability
- After realizing that not all fan controllers support the dimmer
- changed the Helper displayName to Smart Switch/Dimmer/Fan Helper
-
Ecobee Suite Smart Vents, version 1.8.11
- Tweaked minimumVentLevel type conversions
-
Eocbee Suite Thermal Comfort, version 1.8.14
- Fix for multi-word Climate names
- Add missing function for Do Not Disturb
-
Ecobee Suite Working From Home, version 1.8.11
- Fix for multi-word Climate names
These updates are highly recommended for all users
1 Like
Oops! I always try to read up and see if it’s been reported. The funny thing is, I don’t think it has ever worked so it wasn’t something new for me, just something I got interested in investigating since my fixed setpoints of the ecobee schedule constantly have to be adjusted as the weather is heating up.
Another funny bug I have been noticing is when I have a hold applied (program setpoint is 79, local temp is 80 but wife is cold so temp setpoint is 81) and I have a sleep routine in Smartthings that I press and hold a button on my nightstand and the hub runs my goodnight routine. Using the Mode/Routine/Switches helper, I have my Ecobee move to the sleep setpoints (84F) when Goodnight routine is run. What I’m seeing, however, is that first the hold is removed and for a minute or so it uses the daytime setpoint of 79F before shifting to the bedtime 84F. This causes the cooling to run for a brief moment but this bugs the wife lol.
No worries - multiple reports of an issue help me to focus in on the probable cause better.
As for the momentary A/C, it is technically not a bug. As I noted in the documentation, I chose years ago to NOT support the “stacked holds” feature of the Ecobee, where Holds are never cleared, just stacked up on atop the next. Instead, my code always resets any current Hold before setting a new one by doing a resumeProgram(). So in this case, the current Comfort Setting is 80°F, but you have a Hold: Temp for 81°F. So when you change to the Sleep Comfort Setting, the code first resumes the current 80°F setting, then a few seconds later it changes to the Sleep setting. Frankly, I am surprised that there is enough of a time gap for the HVAC to kick in - the operation shouldn’t take more than a few seconds…
I can try to figure out what is going on, if you could start Live Logging before you go to bed, then send me the logs for the 3 components involved:
- ES Manager
- ES Thermostat
- ES Routines (et al)
Best to PM them to me, or email to my address found in the documentation and app/driver files.
1 Like
Ecobee Suite Updates posted on 16 May 2020 at 7:40am
Fixes include:
-
Ecobee Suite Thermostat, version 1.8.15
- Eliminate duplicate
resumeProgram()when changing programs/climates
- Eliminate duplicate
-
Ecobee Suite Open Contacts, version 1.8.22
- Display current program in label display
-
Ecobee Suite Routines, version 1.8.17
- Fix
getThermostatPrograms()
- Fix
-
Ecobee Suite Smart Mode, version 1.8.22
- Fix
getThermostatPrograms()
- Fix
-
Ecobee Suite Smart Room, version 1.8.17
- More room activation improvements
-
Ecobee Suite Smart Vents, version 1.8.12
- Fix
getThermostatPrograms()
- Fix
-
Ecobee Suite Thermal Comfort, version 1.8.17
- Fix
getThermostatPrograms()
- Fix
-
Ecobee Suite Working From Home, 1.8.17
- Fix
getThermostatPrograms()
- Fix
These fixes are recommended for all Ecobee Suite installations
3 Likes
I’m getting this. I reinstalled it, and not sure how to fix it. I did everything right (I think) any ideas?
Look at Live Logging for Ecobee Suite Manager and the Ecobee Suite Thermostat, and see if there are any errors/hints in there…
It could be that you just need to re-authenticate with Ecobee, but the logs should tell you that…
FYI, the Open Contacts Smart Helper is still not working with the newest release.
I’m sorry, but it works fine for me, so could you please give me more some more information than that? Log files showing errors, selected configurations, etc. are always helpful…
There is an interesting thing. When I go to logs for Contacts with this helper, there are none.
I just updated on Wednesday.
And yes, I did open and close a window
I have the same issue as dlehmer…empty tile. I wiped it all out, started over.
Will check the log.
I had to force something into the IDE logs by clicking on the bee. Got this, but its not much help to me at least:
2:32:25 PM: error java.lang.NullPointerException: Cannot get property ‘temperature’ on null object @line 2784 (doCall)
Try opening and saving the Helper itself…that will force data to the log…
We need to know what is in Live Logging, as viewed from the IDE, for the Ecobee Suite Manager application. If it hasn’t connected, or isn’t seeing data from the Ecobee Cloud for some reason, you are never going to get any data displayed in the Thermostat Device…other than (maybe) if you scroll to the bottom of the Thermostat Device, you may see a “last poll failed” message - but ES Manager’s live logs will tell us why…
Ok, I went into the Suite Manager and selected the Thermostat and saved. Got back this:
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:53 PM: error java.lang.NullPointerException: Cannot get property ‘temperature’ on null object @line 2784 (doCall)
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:53 PM: info Requesting ( equipmentStatus settings program events audio location alerts runtime extendedRuntime sensors weather ) for thermostat My ecobee (511882763456)
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:53 PM: info Polling 511882763456 (forced)
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:53 PM: trace Checking for updates…
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:49 PM: debug Ecobee Suite Manager, version 1.8.42 on SmartThings - initialization complete
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:48 PM: debug getChildDevices(false), children=2
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:48 PM: trace Spawning the poll scheduled event. (thermostats.size(): 1)
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: debug getChildDevices(true), children=2
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: debug getChildDevices(true), children=2
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: trace ====> getEcobeeThermostats() entered
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: trace ====> getEcobeeSensors() entered. thermostats: [8726757b-e381-43e7-9a99-dbdbcf1026c4.511882763456]
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: info Got valid sunrise/set data: [sunrise:Sun May 17 09:27:00 UTC 2020, sunset:Mon May 18 00:06:00 UTC 2020]
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: info Trying to get sunrise/set using geographic coordinates for ‘Home’
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: info Clearing callQueue…
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:47 PM: trace Ecobee Suite Manager, version 1.8.42 on SmartThings Initializing…
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:26 PM: warn intialize() - Waiting 21 seconds for current poll cycle to complete…
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:26 PM: trace Ecobee Suite Manager, version 1.8.42 on SmartThings Initializing…
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:26 PM: trace Cleaning up states
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:26 PM: trace Updated with settings: [accountType:registered, mobile:Android, speak:false, debugLevel:2, holdType:Until Next Program, smartAuto:false, ecobeesensors:[ecobee_suite-sensor-rs:100-L4T9], arrowPause:4, pollingInterval:3, pushNotify:true, thermostats:[8726757b-e381-43e7-9a99-dbdbcf1026c4.511882763456], tempDecimals:0, showThermsAsSensor:true]
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:18 PM: debug getChildDevices(true), children=2
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:15 PM: trace atomicState.settingsCurrentTherms == thermostats: No changes detected!
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:15 PM: trace thermsPage(): atomicState.settingsCurrentTherms=[8726757b-e381-43e7-9a99-dbdbcf1026c4.511882763456] thermostats=[8726757b-e381-43e7-9a99-dbdbcf1026c4.511882763456]
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:15 PM: trace ====> getEcobeeThermostats() entered
8726757b-e381-43e7-9a99-dbdbcf1026c4 2:40:12 PM: debug getChildDevices(true), children=2
Thanks - that makes it easier to debug…
Based on this, I suspect that you haven’t set your thermostat’s location yet - this is required for Ecobee Suite to function correctly.
To fix it, go into the Ecobee Mobile App, go to Account / Manage Homes, select your home/location, and then click Edit to define/identify your thermostat’s (home’s) geographical location and address…
And bang-zoom…just like that it works.
Thanks very much!!!
Thanks - I need to add that to the documentation.
Hi, love your work on this. I am having trouble with Fan Only State in the Vent Helper, my vents are not opening when the fan only mode turns on. Thanks
I am sorry that you are having problems with the Ecobee Suite. To debug your issue, I will need to see Live Logs for ES Manager, ES Thermostat, and the ES Smart Vents Helper at the time things don’t happen as you expect. PM me those logs and I’ll be happy to help!