Fortunately, you can have Time drive both ST Routines and Ecobee Programs - then you just need to decide which one drives the other…
I pulled the update 1.4.17 and most things are working except I cannot change the temp setpoint from the arrows on the tile. I’m in Celsius. Changing the setpoint using actiontiles or using the slider in the command centre works, but touching the main upper-left tile itself doesn’t do anything. Any ideas?
UPDATE NOTIFICATION
As of 9:45am EDT on Friday on April 6, 2018 Ecobee Suite Manager has been updated to v1.4.19 and Ecobee Suite Thermostat has been updated to v1.4.10
Changes in this release:
-
Setpoint buttons on the thermostat main tile are working again! Operation is not as smooth as I would like, but the buttons do work. Generally, wait for the setpoint to update between button presses…
-
When a request is made to change the setpoints to the currently scheduled program’s values, and if that request is temporary (nextTransition), the scheduled program will be resumed and no hold will be set. This allows you to resume the current program using the setpoint adjustments (and also via the API).
-
The Ecobee thermostat device name is now displayed for most Live Logging entries (instead of or in addition to the device ID)
This is a recommended update for all Ecobee Suite users.
3 Likes
Hi Barry, I tried using your Helper as well to turn the Ecobee to Away Mode when the routine changes, but once again, no result is happening on the thermostat.
Helper, CoRE, WebCoRE are not working.
Any other ideas?
I have a good handle on how to use these apps…
Derek -
Please provide the version numbers of Ecobee Suite Manager, Thermostat and Smart Routine/Mode/Program.
Also, in Live Logging, do you see any errors for those 3 when you try to make the change?
One more thing: Can you change the program using the buttons on the Thermostat DTH?
My version for Ecobee Suite Manager is 1.4.19.
My version for Ecobee Suite Routines is 1.4.01.
My version for Ecobee Suite Thermostat is 1.4.07.
My Ecobee 3 Thermostat has a Firmware version of 3.7.0.969.
There were no errors when I changed routines in Live Logging.
Screenshot below.
When I select “away” in the EcobeeTherm: Ecobee device under “My Home”, nothing happens.
I increased the temperature in the app as well, that didn’t work.
I circulated the fan, that worked in the app. When I selected to turn the fan off, that didn’t work.
The app sometimes seems to freeze - I have to assume the issues I am having are from the app itself.
I hope this helps to be able to diagnose my issues.
Let me know if you need me to try anything else - I’m home all day.
Derek -
First thing to try is to update your Thermostat device handler to the latest (1.4.10).
It appears that the proper commands are being sent to the Thermostat, but if the Thermostat device buttons still don’t work, you should probably just uninstall and start over.
My apologies in advance - today is Orthodox Easter, and I will be celebrating with family most of the day. I’ll try to check in late in the afternoon, once things have settled down…
Also - that screenshot is of the device history - it will not show errors. You need to go to Live Logging in the IDE, then try changing the program. THEN, go to the Live Logging and click on the Manager, Routine and Thermostat and look for Error or Warn (red / orange respectively) around the time you tried to change programs.
Hi Barry,
I updated the Thermostat Device Handler to 1.4.10.
Ran the “away mode” routine that uses the Ecobee Suite Helper, then received the following error in Live Logging:
I selected “Away” in the app, and received the following error in Live Logging:
It appears to be the same error…any advice on where to go from here?
No worries in getting back to me - do it when you can.
Happy Easter.
Derek
It appears that either Ecobee Suite Manager or Ecobee Thermostat did not initialize properly when installed. It could be as a result of the version of the thermostat you were running.
Now, this issue SHOULD have cleared itself within an hour of you installing the updated version, so you might find that it is working now. If not, you can try the “double refresh” trick to see if it clears up the issue - hit the refresh button on the thermostat device in SmartThings, wait for the Bee to re-appear, then hit it again. give it a few seconds (until the next scheduled refresh) then try changing programs again.
If that doesn’t work, there could be another error preventing Ecobee Suite Manager from sending the Programs List down to the thermostat. if you run Live Logging during the double refresh, you should look at the logs for both the Thermostat Device and the Suite Manager to see if any other errors are being reported. If so, send me the log snippets and I’ll see what I can do.
If there aren’t any errors being logged on the full (forced) refresh, I’m afraid you will indeed need to uninstall and re-install again. Here’s hoping that the problem has already cleared itself up 
I’m guessing the issue cleared itself within the hour, because I did nothing, ran it again and it works 
7:45:43 PM - Away, Set Ecobee Away Mode Using holdType indefinite
Thank you for all of your assistance.
Lets hope there are no more issues…
Derek
1 Like
@storageanarchy is it possible to set a “quiet time” for the humidifier? I was a nest user and it had a feature where I could set a time period that would not allow the fan and humidifier to kick on. I used this a lot because I have a central return right near where we watch tv at night and it so loud it makes the tv hard to hear. I didn’t see anything in the helper app that I thought would do this. Do you know of a way that this could be accomplished? Maybe webcore piston or something, I just can think of what it would need to call to stop it from running…
TIA!
Interesting idea. Which helper are you using/referring to - Smart Circulation?
@jbrown - Here’s a proposed approach, tell me what you think:
Instead of a “quiet time”, I could add support for disabling Smart Circulation (setting fanMinInTime = 0) any time an (optional) specific switch (real or virtual) was (on/off), and re-enabling it when said switch was reversed. It would be optional, so that it wasn’t used in every Smart Circulation instance (for example, add it only to your Home circulation Helper, but not to your Away or Night Helpers).
This switch could be a switch or a hue lamp or a Harmony activity or anything else you have turned on (or off) while watching TV.
It could also be a virtual switch, that you turn on using some other automation - you could have a Routine that turns the switch on/off based on almost any SmartThing event (motion, presence, time, sunrise/sunset). Or you could add it to an existing routine (perhaps to ensure the switch is turned off when changing to Night mode). Or, you could use Smart Lighting to control the switch, based on other switches or events.
The elegance is that it is a simple addition to Smart Circulation, but you get an almost endless means for actually controlling the “quiet period”…
Note, of course, that setting fanMinOnTime to 0 does not prohibit the HVAC system from running in response to a demand call for heat/cool. I doubt that you want to actually turn the HVAC off, just stop it from circulating…
Thoughts? (Everyone is encouraged to comment)…
1 Like
300+ posts so I just skipped to the bottom lol. Is it ok to install this alongside the existing older version so I can swap out the device names in webcore before removing the old app?
@eibyer -
Respectfully, your question is answered in the first post in this thread:
These changes mean two Very Important things:
Installing this version WILL NOT update your existing version.
If you want to switch to this version:
- You will be required to create all new SmartThings devices
- You will have to re-create any Helper SmartApps you may be currently using
- You will have to change any SmartThings SmartApps and/or Routines to use the new devices created by this Suite
You can now run this version along with:
- the stock SmartThings Ecobee support
- @StrykerSKS’ Ecobee support (from which I had forked my own implementation)
- prior versions of my Ecobee support
- and of course, alongside any other Ecobee support that uses different names and namespace
1 Like
I just installed (for the first time) the latest version, and when operating in Fan Only, the top pane does not display a green background, but instead is completely blank. Running on android.
Odd…that shouldn’t happen.
A couple of questions:
- Does the Icon and Text “Fan Only” display in the top left Tile under the main tile?
- Did you try the “double Refresh” trick?
We need to look at Live Logging for the Thermostat Device to see if any errors are being logged. Could you please enable Live Logging, then do the double Refresh (hit refresh, wait for the Bee to reappear, then hit refresh again). Look in Live Logging for any red “error” entries - if any, please PM the surrounding segment of Live Logging (screen shot or text grab) to me…
Here’s a screenshot of device when running fan only. There are no errors in live logging for the device or smart app
Sorry, but I am travelling and without my Android device, so I pretty much can only ask questions in the quest to figure out what’s wrong.
- What are the revision numbers for both the Suite Manager and the Thermostat Device?
- What is the version of your Mobile SmartThings app?
- Is this running on SmartThings Classic mobile app, or the new one?
- Do you get the other colors (purple when idle, orange when heating, etc.), or is it only green?
- Did you try double-refresh?
- How about if you pull down on the whole page, does the display refresh?
You might try re-installing the Ecobee Thermostat Device in your IDE - something may have gotten messed up in the initial copy.
Since both the fan-on icon (above “Hold: Home”) and the main tile use the exact same variable’s state to define their content, I’m at a loss to explain why one works and the other doesn’t.