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

@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.

What’s the recommended way to turn off quiet time? I have a button that turns on quiet time, and then when I press it again it “resumes program”. Strangely, the thermostat fan resumes and the mode gets set back to heat/cool (vs off), but the set points are often still remaining at 10C to 30C. That is, “resume program” isn’t always undoing the Quiet Time set points. Aside from that, if my wife has manually changed the set points, I’d rather go back to what she had, instead of resuming the program.

What’s the best way to undo quiet time, including undoing the set points from quiet time back to either the program or what they were before?

When you turn ON the switch, it should save the state of everything and then make the changes you specified during setup.

And when you turn OFF the switch, it should restore the state of everything that it saved prior.

If you don’t think it is doing that properly you can try setting the debug level to 3 or 4 (in ES Manager), and then turn on Live Logging. Turn Quiet Time on, wait a few minutes (at least as long as 2* your cycle time), and then turn Quiet Time back off. Capture the Live Log for the Quiet Time Helper, the ES Thermostat device and ES Manager, starting a few seconds before you turn off the Quiet Time switch, and PM them to me.

It would also be helpful if you could PM me a screen capture(s) of your settings, so that I can see what is expected…

Thanks!
Barry

1 Like

One more thing - please be sure that you are running the latest version of Ecobee Suite - we’re in the 1.7.** version number ranges now -

I sent you the logs and screenshots. The set points don’t resume when Quiet Time turns off.

Why do I have to reconnect this to my ecobee account every few months? It just stops working. Shows connected in the app but cant do anything.

It could be because you aren’t running the latest code. This is the (deprecated) thread for version 1.6.**.

The current version of Ecobee Suite is 1.8.** - see here:

[RELEASE] Universal Ecobee Suite, Version 1.8.01

Well I got rid of all my Nests and have moved to 3 Ecobees and am utilizing this program for them and so far so good. What I am finding is that the cooling comes on more often then the Nest. Seems like if I have a set point let’s say 75 and my temp drops to 74 the AC comes on. I know the Nest had like a 3 degree buffer about. Also I am using webcore for my scheduler. I don’t want to use any of the ecobee scheduler. Is there any to totally delete all the schedules. I know on the nest you could do that.