[DEPRECATED] Universal Ecobee Suite, version 1.7.**

Ah ha?

10‎:‎33‎:‎34‎ ‎AM: error  java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 1702861844021453 @line -1 (doCall) 
‎10‎:‎33‎:‎04‎ ‎AM: error  java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 1702862180147139 @line -1 (doCall) 

That’s for the thermostat. Nothing else around that time in the logs.

Here’s what ES Manager shows around that time:

10‎:‎33‎:‎59‎ ‎AM: info resumeProgram(Thermostat) [heatingSetpoint:70.0, coolingSetpoint:78.0, currentProgramName:Home, currentProgram:Home, currentProgramId:home] 
10‎:‎33‎:‎58‎ ‎AM: info resumeProgram(Thermostat) [heatingSetpoint:70.0, coolingSetpoint:78.0, currentProgramName:Home, currentProgram:Home, currentProgramId:home] 
10‎:‎33‎:‎49‎ ‎AM: trace Updates sent (42 / 480ms) 
10‎:‎33‎:‎49‎ ‎AM: info Polling thermostat Thermostat (511890317849) completed 
10‎:‎33‎:‎49‎ ‎AM: info No sensor updates... 
10‎:‎33‎:‎49‎ ‎AM: info No thermostat updates... 
10‎:‎33‎:‎49‎ ‎AM: info Requesting ( equipmentStatus runtime sensors ) for thermostat Thermostat (511890317849) 
10‎:‎33‎:‎49‎ ‎AM: info Polling thermostat Thermostat (511890317849)

One more request: could you please set your debug level to 4 (In ES Manager Preferences), and run the test again? I’d like to see the ES Manager log at the EXACT few seconds that the errors occur in ES Thermostat, minus a minute or so, through to 5-10 seconds after the error…

Thanks!

It probably would be best if you PM me the log segments…

You are (again), the bomb! I don’t know why I didn’t see that before. I think I was stopping at ‘smart switch/dimmer/vent’ and just not seeing ‘smart vents & switches’ right below it.

This will allow me to remove the virtual thermostat device handler, which has never worked properly with the new smartthings app.

1 Like

If it doesn’t work exactly like you want, I have a newer version under development that specifically enables switch/dimmer/vent operation independent of the thermostatOperatingState (it still uses the thermostat to track setpoint changes)

So far it seems to be working exactly as hoped. I put it in place yesterday morning, and no WifeGripes© !

1 Like

@storageanarchy, I seem to have caused an issue with my setup last night when I swapped out my ecobee4 ST with a replacement (warranty). I tried to back out the old install and re-add the new tstat. I removed the smart assistants and then removed the Ecobee Suite Manager and it looked like everything was removed. I didn’t uninstall the DTH or apps. When I added the new tstat and smart assistants I now see the following error in the Live Logging and there are two listings at the top for Ecobee Suite Manager and the error is under one of them.

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:34:44 AM: trace No updates…

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:33:45 AM: error java.lang.NullPointerException: Cannot get property ‘deviceChildren’ on null object @line 1807 (doCall)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:33:45 AM: info Polling thermostat My ecobee (521700037704) completed

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:33:45 AM: info 72 updates for 9 sensors (Basement, Bedroom, Family Room, Hallway, Kitchen, Living Room, My ecobee, Office, Upstairs Office)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:33:45 AM: info 9 updates for 1 thermostat (My ecobee)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:33:44 AM: info Requesting ( equipmentStatus settings program events audio location alerts runtime sensors weather ) for thermostat My ecobee (521700037704)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:33:44 AM: info Polling thermostat My ecobee (521700037704) (forced)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:32:49 AM: trace No updates…

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:31:50 AM: error java.lang.NullPointerException: Cannot get property ‘deviceChildren’ on null object @line 1807 (doCall)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:31:50 AM: info Polling thermostat My ecobee (521700037704) completed

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:31:50 AM: info 9 updates for 8 sensors (Bedroom, Family Room, Hallway, Kitchen, Living Room, My ecobee, Office, Upstairs Office)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:31:50 AM: info 5 updates for 1 thermostat (My ecobee)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:31:46 AM: info Requesting ( equipmentStatus runtime extendedRuntime sensors ) for thermostat My ecobee (521700037704)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:31:46 AM: info Polling thermostat My ecobee (521700037704)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:30:53 AM: trace No updates…

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:29:45 AM: error java.lang.NullPointerException: Cannot get property ‘deviceChildren’ on null object @line 1807 (doCall)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:29:45 AM: info Polling thermostat My ecobee (521700037704) completed

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:29:45 AM: info 6 updates for 6 sensors (Family Room, Kitchen, Living Room, My ecobee, Office, Upstairs Office)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:29:45 AM: info 2 updates for 1 thermostat (My ecobee)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:29:44 AM: info Requesting ( equipmentStatus runtime extendedRuntime sensors ) for thermostat My ecobee (521700037704)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:29:44 AM: info Polling thermostat My ecobee (521700037704)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:28:45 AM: error java.lang.NullPointerException: Cannot get property ‘deviceChildren’ on null object @line 1807 (doCall)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:28:45 AM: info Polling thermostat My ecobee (521700037704) completed

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:28:45 AM: info 6 updates for 5 sensors (Kitchen, Living Room, My ecobee, Office, Upstairs Office)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:28:45 AM: info 3 updates for 1 thermostat (My ecobee)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:28:44 AM: info Requesting ( equipmentStatus runtime extendedRuntime sensors ) for thermostat My ecobee (521700037704)

d1c9e843-c1b3-4e4b-9473-21c5826c88cf 8:28:44 AM: info Polling thermostat My ecobee (521700037704)

The other instance has the following:
cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:34:23 AM: trace Updates sent (1109 / 2123ms)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:34:22 AM: info Polling thermostat My ecobee (521700037704) completed

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:34:22 AM: info 73 updates for 9 sensors (Basement, Bedroom, Family Room, Hallway, Kitchen, Living Room, My ecobee, Office, Upstairs Office)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:34:21 AM: info 12 updates for 1 thermostat (My ecobee)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:34:21 AM: info Requesting ( equipmentStatus settings program events audio location alerts runtime sensors weather ) for thermostat My ecobee (521700037704)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:34:21 AM: info Polling thermostat My ecobee (521700037704) (forced)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:29:22 AM: trace Updates sent (516 / 1337ms)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:29:22 AM: info Polling thermostat My ecobee (521700037704) completed

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:29:22 AM: info 8 updates for 7 sensors (Basement, Family Room, Kitchen, Living Room, My ecobee, Office, Upstairs Office)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:29:21 AM: info 3 updates for 1 thermostat (My ecobee)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:29:21 AM: info Requesting ( equipmentStatus runtime extendedRuntime sensors ) for thermostat My ecobee (521700037704)

cadd1b1b-6944-4105-a04a-b2b8e2b4d94e 8:29:21 AM: info Polling thermostat My ecobee (521700037704)

At this point you need to do a complete uninstall, starting by removing all the app and Helpers you are using, then the sensor devices, then the thermostat devices and finally ES Manager itself. Any other order, and you likely will get stuck, requiring SmartThings support to remove one or more app and/or devices.

In the future, I advise the following when replacing a thermostat controlled by ES Manager:

  1. In ES Manager, disable the thermostat being replaced (remove it from the selected list).
    • You may be required to remove this thermostat from any/all Helpers that was using it.
  2. Verify that the Device Driver for the disabled thermostat has been removed. If not, manually remove it.
  3. Physically remove the old thermostat from the mounting
  4. Using the on-line Web access to your account, remove the old thermostat from your account
  5. Install the new thermostat, following the standard instructions. Be sure to name the device, and to add your location to it (latter is done via the Web interface, I believe).
  6. Once you know you have access to the new thermostat using the Ecobee Web interface, go back into ES Manager and discover/select the new thermostat (and any dependent sensors).

I hope this helps!!!

I’m having some oddities regarding the usage of the ES Manger.

Automatons are working well and from what I can tell my thermostat is actually communicating with STs however when I look in the app it is reporting my thermostat and my secondary sensor is unavailable.

I know that I could turn off the device health in the old app and it would keep humming along reporting everything happening and I wouldn’t know any different but it is a little odd to me since as I said everything is working just fine it just is showing as unavailable in the app.

Again, it is

Do you have any ideas about what could be causing this and what can be done to fix it?

Thanks for the help.

Turn off device health…that’s the only solution that I am aware of.

Thanks Barry. That worked and all is good again.

MAJOR Update posted on 12 January 2020 at 9:15am EST

This release delivers a completely revamped Smart Vents helper, bug fixes for manual fan controls, and miscellaneous performance enhancements.

  • Ecobee Suite Thermostat, version 1.7.35
    • setThermostatFanMode() now retains current fanMinOnTime for ON & CIRCULATE; resets to 0 for OFF & AUTO
    • resumeProgram() now works to clear fan holds
    • Fan Holds now mimics exactly fan holds set at the physical thermostat
    • provides new attributes for Smart Vents Helper (nextCoolingSetpoint, nextHeatingSetpoint and nextProgramName); these are only valid when thermostat is in (Smart Recovery)
  • Ecobee Suite Manager, version 1.7.44
    • Fixed fan holds (setting & recovery) - now properly recognizes fan holds set outside of ES Suite
    • Revamped Smart Recovery, so that the Smart Vents Helper knows what the Recovery target is|
      • added nextCoolingSetpoint, nextHeatingSetpoint and nextProgramName attributes (only valid in (Smart Recovery))
    • Optimized myConvertTemperatureIfNeeded() code
  • Ecobee Suite Smart Vents Helper, version 1.7.23 MAJOR NEW FUNCTIONALITY!
    • New (Smart Recovery) handling - now “knows” the Smart Recovery target temperatures, and optimizes the vents to that target
    • Added Fan Only percentage setting option
    • Added optional Ecobee Programs selection to restrict vent changes to certain Programs/Climates/Schedules
      • Optionally will auto-enroll (and un-enroll) Ecobee Sensors into enabled Programs on the ES Thermostat, so that the ES Sensors’ temperature is included in the setpoints
      • Properly recognizes and handles (Smart Recovery) during a disabled Program/Climate, so allows preHeating/Cooling when the next Program is enabled.
    • Now shows open percentage and logical state (open/closed) in device label
    • New recommended min/max values (1/98) for near-silent vent operation (using 0/100 results in the “slap!” sound on Keen vents)
    • Added support for HubConnected EcoNet Vents and Keen Home Smart Vents
      • ES-optimized drivers can be found here. These drivers will show ‘open/closed’ logical state based upon the configured min/max values
      • Also works with stock EcoNet Vent and Keen Home Smart Vent drivers/DTHs (without open/closed state)
    • Optimized Vent handling - fewer position changes to maximize battery life
    • Operational Note
      • It is strongly recommended that you include at least 1 non-Ecobee temperature sensor (ZigBee, Z-Wave or WiFi) in the configuration of ES Smart Vents, because Ecobee Sensors can be slow to report changes. If possible, tune the non-Ecobee sensors to match the reported value of the Ecobee Sensor, and then adjust the Smart Vent target setpoints to align with the rooms “real” temperature (this because you cannot adjust the Ecobee Sensors’ temperature values).

This update is recommended for all Ecobee Suite installations

Hotfix update for Smart Vents released 12 January 2020 at 1:15pm

  • Ecobee Suite Smart Vents, version 1.7.24
    • Remove extraneous debug logging
    • Add ‘percentage’ option for vent state when Helper is Paused
    • Updated app.label updates to correctly reflect open/close + percentage states.

As above, recommended for all Ecobee Suite installations

Hi,

I installed Ecobee Suite several weeks ago, as I wanted to be able to change the mode of my thermostat (Home, Away) based on the mode of Smartthings. It seemed to work OK until we had a power failure in the house a couple of weeks ago. Since that time, the thermostat is showing as “Unavailable”. I tried re-authenticating at Ecobee, to no avail.

I then decided that I’d start over by removing Ecobee Suite completely. But I’m unable to do that, as I’m getting “An Unexpected Error Occurred” when trying to remove the instance of Ecobee Suite. I then saw reference here to removing helper apps and the thermostat from EC Suite, which I did. I still get the unexpected error, but also an error “Device still in use. Remove from any SmartApps or Dashboards, then try again.”

I thought I had removed everything, but realized I still had the thermostat on a dashboard. Just removed that, and still get the Unexpected Error when trying to remove Ecobee Suite manager.

In the Smartthings API website the thermostat device shows with a status of “HUB_DISCONNECTED” while every other device is Online or Active.

At this point, I just want it gone. What can I do?

Bob

Hi,

Never mind. I just tried lots of random “deletes” and “removes” of the Suite and the phantom “Connect” that also gets installed. Removed connections to devices, and ultimately, using both the ST app on my phone and the API I managed to get everything removed.

1 Like

Hi Barry, is there a way in your current helpers to turn on the schedule earlier than the ecobee schedule? I currently have a time based virtusl switch in smartthings to do it, but have to modify both the switch and the ecobee setting anytime I want to change. I am hoping you can address the whole 30 minute increments limitation for the Ecobee schedule which I have seen others gripe about as well. I.E. want my schedule to start at 645am. So in a prefect world I would like to have the ability to take the Ecobee schedule time minus 5,10,15,20,25 minutes in your helper someway to start my schedule when I want to and not be limited to the 30 minute increments. That way my wife can just changed the ecobee and your suite will work as well.

Hey, so this is an awesome suggestion!

None of the current Helpers can do this, and it’s going to be a bit of work to get the necessary data about the daily climate schedule into the ES Thermostat device so that I can write a new Helper, but it is doable. I’ll see what I can no - no promises, but I do like the idea…

1 Like

is it possible to add access to adjust if the ecobee is in home/away mode as a switch?

Already supported. Just create a virtual switch (or 4), then configure an instance of the ES Mode/Routine/Switches/Program helper to change the Program based on that virtual switch being turned on or off.

oh wow, thanks… i didn’t even need the virtual switch I can just set the ecobee mode based on the mode of smarthings.

Thanks for the help pointing out the “helpers”, those are great.