Yes, unfortunately, you cannot configure Contact & Switches while any of the sensors are in the state that the thermostat should be set to Mode = Off. You have to have everything in the state that the Mode should NOT be Off, then configure the Helper, and everything should work…
@storageanarchy I thought I updated all the code, but for some reason the DHT code wasn’t being updated even though I updated the main app. Thanks for pointing me in the right direction. All is well now!
Loving the Ecobee Suite so far, but I’ve run into an issue with Holds. I’ve got my Thermostat setting set to “Until the next scheduled activity”. I’ve also got the Ecobee Suite global setting for Select Hold Type set to “Until Next Program”. However whenever I change modes in ST, for example from Away to Home, it seems to set an indefinite hold. I check the Ecobee app and it’s showing “Home and Holding”. Is that expected? I would have assumed it would say “Home until 8PM” or whatever the next scheduled change is. It seems like Ecobee is setting all holds to indefinite no matter what.
Nobody has reported an issue with holds before.
You sure that the Ecobee App just says “holding.” What does it show on the Ecobee Suite thermostat device display in SmartThings? What about on the thermostat itself? And the Ecobee web app?
Within a few minutes of the hold being set, all four should reflect the same hold end time. If not, we need to check what hold is being requested by ES: get into LIve Logging before the event change should happen, and the afterwards look at the log for the timeframe for:
- the Helper app that should be making the request
- the ES thermostat device
- ES manager
You should be able to find the log entries when the request was made showing the type of hold requested and the returned response.
Let me know what you see in the logs; hopefully this will give us a clue as to what is happening.
My apologies! I dug a bit deeper and now that you mention it, I think it’s an issue with the UI in the Ecobee iOS app.
As you can see in this screenshot, it’s showing an indefinite hold. However, here’s the web app and the ST app.
So nevermind! Thanks!
OMG, I had been looking for some way to turn my a/c off when the sliding door was open since I always forget. So after a google search led me to this post then reading and following your instructions I installed Ecobee Suite with contacts helper and boom just want I needed. if the door is open more than a min the mode changes from auto to off.
Thank you so much for this!!
also will whatever I set it to on the device (off/auto) override the helper request? If i have set it off the helper will not change it to auto?
Sorry for the delayed response - was pretty much off-the-grid for the last week…
That error pops up occaisionally on SmartThings, generally with no apparent cause. Is it ALWAYS throwing that error for you, or did it happen only once or twice?
I’ve seemed to hit a similar issue to what millsjq hit back in Jun. I get to step 10 in the “Finalizing Installation on SmartThings Mobile” of the readme, but re-opening the suite doesn’t continue the process. I have tried deleting the test devices as instructed, but the installation does not continue. Once the devices are deleted, the Ecobee Suite Manager no longer shows in the Automation tab.
Ecobee Suite updates posted on 22 August 2019 at 7:05am EDT
Ecobee Suite Open Contacts, version 1.7.30
- Fixed typo in tmpThermSave(d)State
This fix is highly recommended for all users of ES Open Contacts
I"m not sure what’s going on with your installation - deleting the test devices shouldn’t also delete the ES Manager SmartApp.
As I haven’t heard any other such reports lately, you might want to start over from scratch, deleting ALL the ES SmartApps and DTHs and then re-installing.
I can remove the devices which also deletes the ES Manager SmartApp, however from there the installation doesn’t continue. Am I missing something? it doesnt seem to find the ecobee
Like I said, removing the temporary devices should not delete ES Manager - I can only guess that something isn’t installed correctly…
Some things to check:
- Be sure that you are using the SmartThings Classic mobile app - you can’t do the installation with the “new” mobile app
- Be sure that you have installed all 14 files: 2 device handlers (thermostat & sensor), plus the 12 SmartApps - you need them all installed, even if you aren’t going to use them all
- The first time you run Ecobee Suite Manager should be from the Marketplace/SmartApps/MyApps
- After completing the initial login to Ecobee, exit from ES Manager. Then go to the Applications tab in the (old, classic) mobile app, and find the installed instance of Ecobee Suite Manager. Run that, and it should now allow you to select thermostats and sensors you want to use…
It might help to run Live Logging from the IDE while you attempt the installation - that way you can look for errors that may have been logged in the process…
Managed to finally get it working. Had to go through the steps really fast after removing the temp devices.
I can’t seem to create a new setpoint helper. What would be the cause of this:
d92cf2ef-a77e-4c2d-9486-5289e6caac97 1:38:25 PM: error java.lang.NullPointerException
d92cf2ef-a77e-4c2d-9486-5289e6caac97 1:38:25 PM: info Ecobee Suite Smart Mode, Programs & Setpoints Helper, version 1.7.17 on SmartThings Initializing…
d92cf2ef-a77e-4c2d-9486-5289e6caac97 1:38:25 PM: trace Installed with settings [notify:false, humidistat:Mesa Weather, belowSchedule:Very Hot, betweenSetpoints:false, aboveCool:false, tempDisable:false, aboveTemp:110, aboveSchedule:Extreme Heat, betweenSchedule:Very Hot, thermostats:[Ecobee Thermostat], holdType:Ecobee Manager Setting, insideAuto:false, belowMode:cool, thermometer:Mesa Weather, belowSetpoints:false, belowTemp:105, aboveSetpoints:false, theModes:[Home], tempSource:sensors]
d92cf2ef-a77e-4c2d-9486-5289e6caac97 1:37:41 PM: error java.lang.NullPointerException @line 1389 (updateMyLabel)
Hi, just installed this. First of all, the installation was very straightforward and easy. Kudos.
I’m running into an error with the Smart Mode, Programs and Setpoints, however. (Rest appear to be working fine.) Logged error below. Did I miss a step somewhere?
java.lang.IllegalArgumentException: Command ‘currentValue’ is not supported by device c46dda5e-190a-4b3c-b7fe-937e62be8c6f of type ‘Ecobee Suite Thermostat’. Supported commands: [refresh, setHeatingSetpoint, setCoolingSetpoint, off, heat, emergencyHeat, cool, setThermostatMode, fanOn, fanAuto, fanCirculate, setThermostatFanMode, auto, setSchedule, ping, auxHeatOnly, generateEvent, raiseSetpoint, lowerSetpoint, resumeProgram, setHeatingSetpointDelay, setCoolingSetpointDelay, setThermostatProgram, setFanMinOnTime, setFanMinOnTimeDelay, setVacationFanMinOnTime, deleteVacation, cancelVacation, home, present, asleep, night, away, wakeup, awake, emergency, fanOff, noOp, doRefresh, cancelDemandResponse, cancelReservation, forceRefresh, makeReservation, setDehumidifierMode, setDehumiditySetpoint, setEcobeeSetting, setHumidifierMode, setHumiditySetpoint, setProgramSetpoints] @line 616 (insideChangeHandler)
I just posted about the same Smart Helper App so, it has a couple issues with it
currentValue() is a built-in and is supported for ALL devices, so this error is a red herring. Possibly something else is wrong, but I can’t reproduce it. Perhaps you can try simply opening this Helper instance, verifying all the selections, and then saving it again…
Fix will be posted momentarily…