[DEPRECATED] Free Ecobee Suite, version 1.6.**

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 :slight_smile:

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.

  1. 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.
  2. 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…

https://raw.githubusercontent.com/SANdood/Ecobee-Suite/universal-dev/smartapps/sandood/ecobee-suite-open-contacts.src/ecobee-suite-open-contacts.groovy

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

Moved reply to pm

I am in a relatively unique situation, but someone may have already solved. I have two separate zones in my home each with separate ecobee. I have a peak power program with my electric company I am billed by the highest usage (in 15 min window) of electricity at a lower rate during 7pm to 11:59 AM, and a much higher rate (again for highest usage in 15 min window) during the Noon- 6:59PM. What I am think of trying is to build a Webcore piston that does not allow one zone to run, until the other zone is not running. I can use a variable to track when one system is running and work from there. I am sure Ecobee or others could build an more elegant process for slow starts and sharing time. Has anyone tried this?

Just to verify - you have 2 zones, but only 1 condenser and air handler, correct?

If true, you should do some experimentation to see how long the HVAC takes to cool both floors at the same time vs. 2nd Floor then 1st Floor. You may find that the time is actually shorter if both zone cool at the same time…

If it’s 2 separate condensers and air handlers, then running them sequentially will reduce the peak demand, I should think.

Hi Barry,

I think you sent the email below. accidentally to me.

I have been using the Ecobee suite for a while now and switched over to this version when it was in beta. It has worked flawlessly in conjunction with my webcore logic to set away hold and resume. However, one time on each of the last three days my resume command looks to be ignored. In fact on one occasion resume was sent twice over a 30 minute span and hold still was in place. This occurred for both of my thermostats. See screenshot below.

@ssilence -

My apologies, I probably broke something. But I’m going to need more information before I can help…

  • Do you see any errors in the Live Logging for the Thermostat or the Manager?

  • What are the version numbers for ES Manager and ES Thermostat?

Moved discussion to correct thread.