Does anyone having a working experience with Smart Circulation? It seems to work initially for me for a couple of hours, and then stop working.
OK, I get it. But note that those are all INDOOR measurements, as far as I can tell. What goes on outdoors has almost no predictable effect on the indoor conditions
So anyway, now can you please describe the conditions you want monitored, the thresholds you want to cause changes, and the changes you want to have happen as a result.
And remember:
- An AC will always dehumidify to some extent when it is cooling, with or without a separate dehumidifier - you really cannot turn that off;
- While you can have a separate humidifier and dehumidifier, Iām pretty sure that the Ecobee 3/4ās wonāt allow you to humidify while cooling (only while heating and fan only)
- To dehumidify while heating, you will require a separate dehumidifier
Again, I really donāt see any realistic effect of shutting off the AC when it is cool and the dew point is low - the AC wonāt run inside the house unless a) the house is warmer than the desired temperature, or b) the humidity is higher than the desired dehumidification level. Turning on the stove/oven/dryer or taking a hot shower could raise the inside temps/humidity even though it is cooler/drier outside - do you really want your AC to NOT RUN when conditions inside climb above your chosen settings?
I must be really missing the point hereā¦other than I get that you donāt want to turn the AC off if the outside dew point is uncomfortable. IMHO, I donāt get why you want to turn it off EVER - unless, of course, you open some doors/windowsā¦
I only tried to explain what I think @richardpeng wants. My system works good the way I have it.
Indeed. What that shows (and Iāve knew it for like 25 years) is a comfort zone where it would be optimal to be. Simple temperature adjustment with a fixed number for humidity is not enough. to be comfortable. You can close though.
Thatās correct. And I wold not even look at outside conditions for inside control of my comfort.
Thatās true. But some people believe that turning it off if youāre not home will save money, without realizing that to make up the AC has to work for longer.
Again, I really donāt see any realistic effect of shutting off the AC when it is cool and the dew point is low - the AC wonāt run inside the house unless a) the house is warmer than the desired temperature, or b) the humidity is higher than the desired dehumidification level. Turning on the stove/oven/dryer or taking a hot shower could raise the inside temps/humidity even though it is cooler/drier outside - do you really want your AC to NOT RUN when conditions inside climb above your chosen settings?
I must be really missing the point hereā¦other than I get that you donāt want to turn the AC off if the outside dew point is uncomfortable. IMHO, I donāt get why you want to turn it off EVER - unless, of course, you open some doors/windowsā¦
My apartment tends to get warm with all the windows closed because of appliances, electronics, and the fact that Iām in an upstairs unit. When itās hot outside, I have no choice but to run the AC. However, when itās cool enough outside and the dew point low enough, Iād rather open the windows than run the AC to cool my apartment. I want to automatically turn off the AC rather than remember to check the weather and figure out when I should open the windows. I donāt care as much about staying in the ideal zone (thanks for the graph though @NomadTech) but to save money by using the outside cooler air to cool my apartment. I also donāt actively manage my humidity using my AC. I just want to avoid turning off the AC when itās too muggy out to open windows, which is what has been happening in the past couple of days.
Therefore, Iād like to be able to āturn the AC off if the outside temperature is below 76 degrees AND the dew point is below 65ā. If the dew point is 65+ OR the outside temperature is 76+, then donāt apply this rule (use the between rule or do nothing).
Seems like you could do this pretty easily with webCoRE.
Since you are running a modified version that does what you want, let me know how it works for you over the coming week or soā¦IMHO you really want your AC on all the time, unless the windows are open. YMMVā¦
Very dumb question probably, but mine turned blue in the IDE but when I try to commit changes it gives me a 404 Error, not found. Itās probably user error since I have the same issue with Webcore in IDE. But how can I fix this?
No such thing as a dumb question, my dad always said - only dumb answers.
Sorry, but thatās all I have: dumb answers. I honestly donāt know why you would get a 404 error within the IDE for either my Ecobee Suite or for WebCoRE. If some things work, but these two donāt would be even more confusing; your best bet might be to send an email to support@smartthings.com
I guess nobody else is having this issue? Anyway, I checked to make sure that I had the latest version of Ecobee Suite and all helper apps from the repo and I do. I checked that the issue is still occurring and it is. I do have a log message this time when it happens:
5:37:41 AM: error java.lang.NullPointerException: Cannot invoke method capitalize() on null object @line 75 (doCall)
And this is all I see in the SmartThings UI (Android):
Again, Iām just trying to set quiet time on one of my thermostats when a window or door is opened. My workaround has just been turning it off for now.
On another note, I donāt think quiet time is even working. Lately when I turn the switch off the hvac stays on. But Iām still experimenting with that one.
This post was supposed to be deleted.
You will need to get the latest Ecobee Suite Open Contacts helper code, version 1.5.03 to solve your original problem. Not sure that it will solve your latest one thoughā¦
Thanks for that. Just tested quiet time again. I have it setup so that the button turning off will start quiet time. So basically while the button is on, the HVAC is on.
I just tried setting quiet time now and captured the log from the helper app when it failed.
11:46:44 AM: error groovy.lang.MissingPropertyException: No such property: statState for class: script_app_1080fbaaafddaef2f4ca0e989c50533bdf82cf38ff0eadd7c9bf93c9cc773424
Possible solutions: theState @line 201 (turnOnQuietTime)Please see my updated message aboveā¦somehow the Community Platform lost my editsā¦
Ecobee Suite Quiet Time v1.5.02 fixes your second problem.
Sorry about these - somehow edits were not carried over to the repo when I updated to v1.5.*
And yes, that probably means nobody else is using these two at the momentā¦
Thanks! Sorry Iāve been away most of the day but Iāll update now and report back after Iāve had a chance to test.
I have to re-sign in / authorize the Ecobee Suite smart app a few times a week. Is that normal?
I do this when I get into smartthings and it says all of my thermostat/sensor data is unavailable. As soon as I re-sign in all the data works again. For a day or two (or three).
No, this is not normal, but you are only the 2nd person to have reported this to me. I have taken many steps to ensure this is not an issue, but something strange appears to be going onā¦
To help me debug, can you please provide me with (via PM, preferrably):
-
The vesion number of Ecobee Suite Manager and Ecobee Suite Thermostat that you are running.
-
Live Logging for Ecobee Suite Manager that shows the first āerrorā - to do this youāll have to run Live Logging continuously, and (hopefully) capture the initial error report. Ideally, set your debug level in Ecobee Manager Preferences to 5.
-
Your physical location (City, state. country)
-
Your Preferences settings (debug level, refresh frequency, decimal precision, etc.)
-
Your device, and the version number of the SmartThings app that you are using
-
Any other pertinent details (are you having intermittent internet access; do your Ecobee thermostats remain accessible via the Ecobee mobile app, etc.)
Finally, have you tried totally uninstalling and re-installing the entire Ecobee Suite?
Thanks - Iāll get to the bottom of this for youā¦it most definitely should not be happeningā¦
Barry,
Defiantly something is up with Ecobee again. Three of folks I support in the Vera space also lost connectivity. Where the other 5 didnāt. I wonder if itās account based?
I suspect that it is something to do with the Ecobee service - account or servers. Debugging so far seems to point to the userās login authentication key being revoked by Ecobee, without notice or apparent reason. This is why the recovery code doesnāt work; the user has apparently been ālogged outā of the Ecobee servers.
Thatās my working theory for now - hence the questions about location aboveā¦it might be related to which server oneās Ecobee API is being hosted uponā¦
Iāve been out of town, but it happened again this morning at 4:49am. Iāll try to figure out how to get the live logging for next time.
- The version number of Ecobee Suite Manager and Ecobee Suite Thermostat that you are running.
- The latest on GitHub, updated/checked Sunday. 1.5.00 on both Manager smartapp and thermostat handler.
- Live Logging for Ecobee Suite Manager that shows the first āerrorā - to do this youāll have to run Live Logging continuously, and (hopefully) capture the initial error report. Ideally, set your debug level in Ecobee Manager Preferences to 5.
- Iāll try to figure out how to get this for next time. Seems to happen every few days, so shouldnāt be long.
- Your physical location (City, state. country)
- Boerne, TX, USA
- Your Preferences settings (debug level, refresh frequency, decimal precision, etc.)
- Debug logging=2 [update: I changed this to 5 per your comment on live logging], polling interval=5 min, Decimal places=1
- Your device, and the version number of the SmartThings app that you are using
- I have four Ecobee thermostats - Three ā3ā and one ā3 Liteā. 11 sensors total (including the four thermostats).
- Any other pertinent details (are you having intermittent internet access; do your Ecobee thermostats remain accessible via the Ecobee mobile app, etc.)
- Thermostats seem to be available via the Ecobee app every time I have tried it.
Another observation - when all of my thermostats/sensors show unavailable in the Things list. I can go into one and Refresh, and the āunavailableā goes away for a while, but it doesnāt actually update the value.
The only thing I have found that updates the value is to re-do the Ecobee API authorization.