Ecobee Suite Hotifxes posted on 14 April 2020 at 10:15am EDT
Fixes issue with hubless SmartThings installations (ES Thermostat and Sensor)
Ecobee Suite Hotfix posted on 14 April 2020 at 12:30pm EDT
Fixes fatal error in setHold() (ES Manager)
Contacts & Sensors won’t do anything at all.
It sees the sensor open but never does anything. I set it to one minute, 2 and 5. Notify or not, it doesn’t do a single thing, not even in the log.
Dag nabbit!!!
There is a 1-bit fix: line #673
change:
if (openCount > 0) return // Belt & Suspendersto:
if (openCount > 1) return // Belt & SuspendersFumble fingers, I am. Hotifx momentarily
ES Open Contacts Hotfix 1.8.16 posted 14 April 2020 at 4:25pm EDT
Fixes typo that was causing no actions when a contact opened.
The fix that you posted fixed it! Thanks for looking at it!
Ok, if I have windows open, it still turns on…
I will give you a log in a few.
Just updated from repo to 1.8.03. I had to reconnect to API, after signing in and clicking authorize, I get an error.
{“error”:true,“type”:“java.lang.reflect.UndeclaredThrowableException”,“message”:“An unexpected error occured.”}
Edit:
Not sure why I didn’t do live logging initially
12:47:21 PM: error groovyx.net.http.HttpResponseException: Unauthorized @line 907 (callback)
Sorry about that - Try the 1.8.30 version of Ecobee Suite Manager
Thanks for the quick update. All good.
This hotfix is still at 0 not 1 like you gave me the instructions above.
80afcbba-1a68-44b1-a856-d20b0f686f97 12:22:46 PM: info numOpen(): 1
80afcbba-1a68-44b1-a856-d20b0f686f97 12:22:46 PM: info sensorOpened() - Bedroom Window Contact contact open
Nothing else. It just won’t do anything, no matter what I set the timeout at.
Before the hotfix, when you told me to change it, that was fine.
Fixed (again - my bad) - Open Contact version 1.8.17
Ecobe Suite Updates posted 18 April 2020 at 2:40pm EDT
This release is primarily cosmetic, and every file has been updated.
Fixes/enhancements include:
- All of the hotfixes that were previously released
- New “Do Not Disturb” setting for Notifications (in those Helpers that support Notifications).
IMPORTANT NOTE: You will have to re-enable Notifications in your installed Helpers - Fix to stop some attributes from not being updated, and others from being updated even when they don’t change
- MUCH faster processing of sensor updates
Version numbers:
- Ecobee Suite Thermostat, version 1.8.13
- Ecobee Suite Sensor, version 1.8.07
-
Ecobee Suite Manager, version
1.8.33HOTFIX 1.8.34 * -
Ecobee Suite Open Contacts, version
1.8.18HOTFIX 1.8.19 * - Ecobee Suite Quiet Time, version 1.8.06
- Ecobee Suite Routines, version 1.8.12
- Ecobee Suite Smart Circulation, version 1.8.08
- Ecobee Suite Smart Humidity, version 1.8.07
- Ecobee Suite Smart Mode, version 1.8.16
- Ecobee Suite Smart Room, version 1.8.12
- Ecobee Suite Smart Switches, version 1.8.06
- Ecobee Suite Smart Vents, version 1.8.09
- Ecobee Suite Zones, version 1.8.08
- Ecobee Suite Thermal Comfort, version 1.8.11
- Ecobee Suite Working From Home, version 1.8.12
* HOTFIX Log:
19-04-2020: ES Manager, 1.8.34: fixes typo causing extraneous attribute updates
21-04-2020: ES Open Contacts, 1.8.19: Notifications were not being sent
These updates are recommended for all Ecobee Suite users, on both SmartThings & Hubitat
1 Like
Thank you very much Barry.
I upgraded from 1.7 to 1.8 yesterday, and I’m no longer able to add or remove sensors from comfort settings. I have a webcore piston that looks like:
The Ecobee Suite App and the device logs report that it succeeded:
The Ecobee Suite ST app shows that it’s been deleted:
But the Ecobee app disagrees:
Any ideas?
Lots of possible issues:
- You can’t delete this sensor from Sleep
- If you call two deletesSensor* back-to-back, one or both will fail. 1.8.** introduced
updateSensorPrograms(activeList, inactiveList), plusaddSensorToPrograms(List)anddeleteSensorFromPrograms(List)so that you can make multiple changes in a single call to the Ecobee Cloud
Not sure what will happen, though, if you do deleteSensorFromPrograms(["Home", "Sleep"]), since you can’t remove it from Sleep.
Perhaps try adding another Sensor to Sleep by hand and then see if your WebCoRE piston works that way…
PS - ES will show completed before hearing back from the API. The Ecobee mobile apps and the physical thermostat won’t reflect the change until they are told about it by the Ecobee Cloud servers. But the Ecobee Mobile app doesn’t auto-refresh, so you may need to reload it.
Thanks for the response!
Sorry, I realize that my post was confusing. In my piston, I added another sensor to Sleep first, but that was failing, so the Ecobee app, as you noted, said I can’t remove the sensor from Sleep since it was the only one.
However, I found if I add a 5 second delay between each add/delete, it works. Not very elegant, but I can live with it.
Unfortunately, I don’t see commands for any of the functions you mention in Webcore:
Please let me know if there’s a better solution that the 5sec delay.
Thanks for your help!
You need to have WebCoRE reload the command interfaces for the sensor device…the new commands are there to solve exactly that problem…
Oh, an knowing the code, I would suggest a 7-second delay instead of 5 will be more reliable.
@storageanarchy, many thanks for all of your wonderful work. I am a new user of Smartthings in general and have enjoyed using your Ecobee Suite Manager app for the last month.
Although temperatures near Chicago haven’t risen to the point that I can see if it is working, I’m using your “Smart Mode, Programs & Setpoins” helper app for the specific purpose of turning off heat/AC and alerting me to open the windows whenever the temperature is in the “between” threshold. I’m using “SmartThings/TWC Weather for Home” to gather my outside temperature and dew point, and I have the temperature check frequency set for 5 minutes.
Initially, I was getting a text message every 5 minutes telling me that the outside temperature was “below” and it adjusted things accordingly. After about 70 of these text messages every 5 minutes, I stopped receiving them, so I thought perhaps it was a fluke. However, last night without any known changes by me, I started receiving text message notifications again every 5 minutes to my suprise. That lasted for about 7 hours and has now stopped. I attempted to turn on the “minimize settings text” option, but I’m not sure if that is related to my problem or not. What exactly does that toggle do?
I do want the outside temperature monitored every 5 minutes, but I don’t want to be texted about it unless the temperature crosses in or out of the “between” threshold so that I know to open or close the windows. What settings would permit that? I’m worried if I turn off all texting, then I won’t be alerted to open/close my windows which defeats my intended purpose.
Thanks again!