- What version of Ecobee Suite are you running?
- What programming language are you using to call resumeProgram()?
- How are you calling resumeProgram() (code snippet, please)
- What is the problem you are seeing?
1 Like
Barry,
I just installed for the first time. Used the Github repos for the 2 devices and the 12 smartapps. I logged my Ecobee credentials in the Classic app and hit Save (on Android). Going to hit save again (to close out and restart) and I get a red error message stating āDevice still in use. Remove from any SmartApps or Dashboards, then try again.ā I still have Ecobee (Connect) installed but the readme file from Github states this is OK? Do you know best next step for installation. Thanks!!
Hi Barry,
Thanks for the quick reply
-
v1.7 of the Ecobee Suite
-
webCore
-
Snippets (VentControl is the errant piston. I included NightVents just so you can see the whole idea.
-
Flipping the virtual switch VentsUp to ON properly returns push msg āHold: VentsUp until tommorow at 8 amā and the thermostat itself also appropriately changes. Flipping the switch to OFF, does not resume the regular program which is either Sleep or Home, but rather repeats the same msg as above. If I change the parameters for ON to āindefiniteā, the msg upon on or off reads āHold: VentsUp foreverā
Ideally, I would also include the below piston, but for testing I have this paused.
Best,
Howard
Brian -
If you check your Devices list, you will probably find two ātestā devices - one thermostat and one sensor. Simply remove those by hand, then go back to Ecobee Suite Manager and it should proceedā¦
1 Like
Howard -
Does the āResumeā button on the Thermostat Device work after your app has set the Program to VentsUp?
Itās not a big deal, but I suggest that you use the attribute ācurrentProgramā instead of āscheduleā. The latter is updated more ālazilyā, and itās value is based off of currentProgram.
Iāll look to see if there is a resumeSchedule bug somewhereā¦
Thanks Barry,
The pistons now look like below with āscheduleā changed to ācurrentProgramā. All run, but flipping the virtual switch to OFF does not resume. Nor does the Resume switch on the Ecobee Suite thermostat; ex. if I push the Away button using the suite thermostat, program changes to Away as it should. Pressing Resume button does not resume.
Best,
OK, somethings definitely wrong if the button doesnāt work.
Unfortunately, I cannot recreate the issue you are seeing, so Iāll need some more info from you, if you donāt mind:
!. Open Ecobee Suite Manager on your mobile and note the version shown at the top.
2. Open Preferences (the gear) for Ecobee Thermostat and note the version displayed there.
3. Turn on Live Logging in the IDE, then set the thermostat to āAwayā,
4. Then, click the resume button and check the Live Log for any errors - could be in the Thermostat device, or it could be in Ecobee Suite Manager - please check both for the time that you clicked Resume.
In #4, I need to know what the FIRST error you see in the logs isā¦
Worry not, we will get this figured outā¦
Let me know those version numbers and Iāll work from thereā¦
1 Like
I updated everything yesterday and now none of my automations seem to work. I am on version 1.7.09 of Ecobee Suite Manager and the only helper app I use is the Mode/Routine/Switches/Program Helper which is on version 1.7.06. I have the helper app set to change the Ecobee Program when the Location Mode changes, but it does nothing. This has been working flawless for months (maybe years?). Any idea what happened?
First Iāve heard, but nothing should have been broken, but Iām human. I really need to fix this - can you get me answers below, please?
Are you seeing errors in Live Logging for the Helper, the Thermostat or the Manager?
Have you tried opening and saving the settings for the Helper? If so, did it solve your problem?
Opening the app and helper and resaving them was the first thing I tried. I do see errors in the Live Logging for the helper:
12:28:00 PM: error groovy.lang.MissingPropertyException: No such property: ncCp for class: script_app_4074c745f21e2ac2621aed6873f3ea69c06ca536d8f6596272af60db92b2b2b8 @line 607 (doCall)
Version 1.7.07 just posted to Github - should fix the problemā¦
Itās been a bit since Iāve had time to mess with changing anything on my ST set up. Does this work with the new app yet? I donāt use it, but eventually Iād like to play around with it again. I havenāt since the 1st version came out of the new ST app.
1 Like
CORRECTION (June 1, 2019): It appears that the latest drop of the New app does in fact support Ecobee Suite. The thermostat device is limited in its UI, but you can control the setpoints and modes (etc.). More importantly, Ecobee Suite Manager appears under Automations, and seems to work pretty well (after I fix a bug in handling SMS notifications).
There may be hope for SmartThings after all 
Please note that this thread is deprecated - the new version is hereā¦
Updated and things seem to be working again, thanks!
In something not really related - I had a paused webcore piston that was parked because this was broke for a little at some other time and I would use that piston in the meantime when the helper would break. I re-enabled that webcore piston while you looked at things and that was hit or miss on whether or not it would set the thermostats correctly. The webcore piston just changes the heatingSetPoint and coolingSetPoint of the thermostats based on location mode, thatās it. I could see that the piston would send commands to the thermostat under the āRecentlyā section in the smartthings app, but the setpoints were definitely not changing. Might be something to look into.
P.S. I also saw your new 1.7 thread so Iāll hop over there with and future comments/issues after this discussion is over, sorry about that!
@storageanarchy My door open sensors to turn off the AC seems to have broken since the last release, it turns the system off with no issue but now when the door is shut it does not turn the AC back on. The notification states all sensors are closed and all switches are off, returning true, thermostat already in off, so its not turning it back on correctly anymore.
- Double check that you are running the latest version of the Contacts & Switches Helper - this sounds like the last fix I posted a couple of days ago.
- Also, double-check the settings for that Helper - somewhere along the line I broke the thermostat selection, you may have to reset the thermostat being controlled within the Helper.
1 Like
Hi Barry,
I am on 1.7.08 for the contact helper.
I noticed the thermostat was missing, I had removed the helper app and set it up from the beginning but i am still having the issue.
It seems that its looking to see if it was already off, even though it was not and it thinks it was so it keeps it off. Since the part of if the contact or switch was already off it will keep it off even if it closes, but its keeping it off no matter what.
A few questions to help me understand what might be different between your setup and mine (which works).
How many contacts/switches are you using, and are you using both, or just one (which one).
Also, when you configured the Helper, was everything closed/off such that the HVAC was supposed to be on, and was the HVAC in fact on at the time?
Does it work correctly for you if you use only a single contact or switch?
Ezra -
Try this test version of Open Contacts & Switches (you will have to load the source into your IDE by hand). It has better logging, so it should tell us what it did instead of turning the HVAC onā¦
Let me know what you seeā¦
1 Like
Barry,
i have one virtual switch and 3 contact sensors.
I was previously using all 4 of those successfully.
During testing i have tried with just a single sensor and with just the switch on their own, to narrow down possible causes.
Usually the AC would be on, with all sensors closed and off, south floridaā¦, but during testing its possible that the AC was off so using the new app you provided i made sure to set it up while everything was closed/off and the AC was on and running.
It turns off correctly but does not turn on, all regardless if i use one or multiple sensors.
Below is the sensor log, notice it thinks the AC is already on, after a while i manually turned it back on.
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:54:32 PM: debug cancel 311071964635, modeOff
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:54:24 PM: debug cancel 311071964635, modeOff
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:54:24 PM: debug cancel 311071964635, modeOff
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:22:01 PM: trace turnonHVAC() entered
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:22:01 PM: info All sensors & switches are reset, and HVAC is already on
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:22:01 PM: info Returning true
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:22:01 PM: info All switches are off
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:22:01 PM: trace sensorClosed() entered with event AC Off Switch switch: off
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:20:04 PM: trace turnoffHVAC() enteredā¦
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:20:04 PM: trace sensorOpened() entered with event AC Off Switch switch: on
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace initialize() exiting
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace switchOffState = false
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace contactOffState = false
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: info Ecobee Suite Contacts & Switches Helper,
version 1.7.09b on SmartThings
Initializingā¦
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: debug updated() entered
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace initialize() exiting
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace turnonHVAC() entered
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace switchOffState = false
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: trace contactOffState = false
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: info Ecobee Suite Contacts & Switches Helper,
version 1.7.09b on SmartThings
Initializingā¦
2e40ca0b-988c-40a1-b510-2a13d83dd084 6:19:40 PM: debug installed() entered