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

Just a guess. But there are non-free Ecobee integrations for SmartThings.

1 Like

@storageanarchy

Hey there...I can't seem to get the contacts helper to work. Here are screenshots of my configuration. I waited 10 minutes with multiple contacts sensors open and the app did not turn off the Ecobee. Help?



Try with the 1.7.05 version I just posted (forgot to include it in this morning's updates).

If it still doesn't work, look at the Live Logging for the Helper, the Thermostat and the Manager - see if there are any red "error" notices. If so, please forward them to me so I can see what's going on...

I won't be home till late tonight, I will attempt this tomorrow. Thank you for the quick replies and work on this.

No worries - at your convenience!

Ok I updated all of the code accordingly. Here are the errors:

app:29902019-05-30 06:26:15.274 pm errorjava.lang.IllegalArgumentException: Command 'currentValue' is not supported by device. on line 248 (updated)

app:29902019-05-30 06:26:15.119 pm infoEcobee Suite Contacts & Switches Helper,

Quick question, I looked through the thread and the .md file and didn't see anything about how to update on Hubitat. Do you just do the import for the manager and helpers to overwrite the existing code?

Yes, Tom - that's the easiest way. Once you import the files the first time, the newer versions of Hubitat appear to "remember" the source, so all you have to do is Import again...

1 Like

I have what I think is the fix for this issue coming soon - thanks for reporting it...

1 Like

Universal Ecobee Suite updates posted 31 May 2019 at 2:45pm

These updates improve performance and reliability.

These are the key updates:

  • Ecobee Suite Manager (ecobee-suite-manager.groovy) version 1.7.11.
    • Fixes Thermostat state updates on SmartThings mobile (thermostatMode, thermostatOperatingState, etc.)
  • Ecobee Suite Thermostat (`ecobee-suite-thermostat.groovy) version 1.7.10
    • Fixes thermostatOperatingState updates
  • Ecobee Suite Contacts & Switches Helper (ecobee-suite-open-contacts) version 1.7.06
    • Fixes issues experienced when using multiple Contacts and/or Switches
  • Ecobee Suite Thermal Comfort Helper (ecobee-suite-thermal-comfort.groovy) version 1.7.06
    • Cleans up arguments passed to setProgramSetpoints()

Collectively, these fixes should address the reported issues with yesterday';s release. If I have missed an issue, please let me know - publicly or via PM.

Note: There may be a remaining issue with cancelling vacation holds...

These updates are Mandatory for ALL users...

1 Like

I have updated to the releases of last night, I have not seen the error today.

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 08:35:31.189 am [info](http://192.168.7.201/installedapp/configure/3687)Updating API status with [apiConnected:full, lastPoll:Succeeded]

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 08:35:31.098 am [error](http://192.168.7.201/installedapp/configure/3687)refreshAuthToken() - HttpResponseException occurred. Exception info: groovyx.net.http.HttpResponseException: Bad Request StatusCode: 400

Woke up this morning after updating and seeing this in the logs?

Is everything still working?

The bottom message indicates a transient error, since the next message above it says that it succeeded on a re-attempt. You will see this from time to time - given the occasional instability of the Ecobee servers.

No.

I went into the device in HE and set the temperature to 68

v:29512019-06-01 09:17:46.570 am infoUpdated 2 objects (37ms)

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:40.083 am [info](http://192.168.7.201/device/edit/2951)Updated 2 objects (32ms)

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:24.059 am [info](http://192.168.7.201/device/edit/2951)Updated 2 objects (37ms)

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:22.026 am [info](http://192.168.7.201/device/edit/2951)refresh() - calling pollChildren , deviceId = 411985555364

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:16.994 am [error](http://192.168.7.201/device/edit/2951)Error updateThermostatSetpoints()

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:16.839 am [info](http://192.168.7.201/device/edit/2951)Updated 2 objects (45ms)

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:15.432 am [info](http://192.168.7.201/device/edit/2951)Updated 1 object (29ms)

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:15.417 am [debug](http://192.168.7.201/device/edit/2951)Ecobee Suite Manager: setHold() for thermostat EcobeeTherm: Kitchen - h: 63.0(630), c: 68.0(680), indefinite, null

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:15.275 am [info](http://192.168.7.201/device/edit/2951)Updated 2 objects (32ms)

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:13.438 am [info](http://192.168.7.201/device/edit/2951)updateThermostatSetpoints() adjusted setpoints, heat 63.0°, cool 68.0°

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:13.431 am [info](http://192.168.7.201/device/edit/2951)Using holdType indefinite

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:13.382 am [warn](http://192.168.7.201/device/edit/2951)No signature of method: java.util.LinkedHashMap.putAll() is applicable for argument types: (java.lang.Integer) values: [2] Possible solutions: putAll(java.util.Map), putAll(java.util.Map), putAll(java.util.Collection), putAt(java.lang.String, java.lang.Object), putAt(java.lang.Object, java.lang.Object), findAll()

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:13.374 am [info](http://192.168.7.201/device/edit/2951)updateThermostatSetpoints(): heatingSetpoint 69°, coolingSetpoint 68.0°

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:11.327 am [info](http://192.168.7.201/device/edit/2951)setCoolingSetpoint() requesting coolingSetpoint: 68.0°F

[dev:2951](http://192.168.7.201/logs#dev2951)2019-06-01 09:17:11.306 am [info](http://192.168.7.201/device/edit/2951)setCoolingSetpoint() request with setpoint value = 68°F

Please look in the Ecobee Suite Manager log at that time and tell me if you see any errors there...

Just FYI, you requested a cooling setpoint (68) that is lower than the heating setpoint (69), so the software had to adjust your request to heat: 63, cool 68 - the 5 degree difference is bbecause your heatCoolMinDelta is 5 degrees.

From ecobee suite logs when I set downstairs.

app:36872019-06-01 09:54:31.996 aminfoUpdating API status with [apiConnected:full, lastPoll:Succeeded]

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:31.834 am[error](http://192.168.7.201/installedapp/configure/3687)refreshAuthToken() - HttpResponseException occurred. Exception info: groovyx.net.http.HttpResponseException: Bad Request StatusCode: 400

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:16.023 am [trace](http://192.168.7.201/installedapp/configure/3687)No updates...

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:15.955 am[error](http://192.168.7.201/installedapp/configure/3687)Checking: Auth_token refresh failed

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:15.745 am[info](http://192.168.7.201/installedapp/configure/3687)Updating API status with [apiConnected:full, lastPoll:Succeeded]

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:15.624 am[error](http://192.168.7.201/installedapp/configure/3687)refreshAuthToken() - HttpResponseException occurred. Exception info: groovyx.net.http.HttpResponseException: Bad Request StatusCode: 400

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:08.968 am[error](http://192.168.7.201/installedapp/configure/3687)Sending: Auth_token refresh failed

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:08.701 am[info](http://192.168.7.201/installedapp/configure/3687)Updating API status with [apiConnected:full, lastPoll:Succeeded]

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:08.639 am[error](http://192.168.7.201/installedapp/configure/3687)refreshAuthToken() - HttpResponseException occurred. Exception info: groovyx.net.http.HttpResponseException: Bad Request StatusCode: 400

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:08.096 am[info](http://192.168.7.201/installedapp/configure/3687)sendJson() - HttpResponseException occurred: Auth_token has expired

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:08.094 am[trace](http://192.168.7.201/installedapp/configure/3687)sendJson() 500 14

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:07.553 am[trace](http://192.168.7.201/installedapp/configure/3687)setHold() for thermostat EcobeeTherm: Kitchen - h: 68.0(680), c: 73.0(730), indefinite, null

[app:3687](http://192.168.7.201/logs#app3687)2019-06-01 09:54:07.535

OK, looks like something wrong with your communications with the Ecobee servers. If it got timeout errors for more than a couple of hours overnight, this might be what you see - I'd be interested to know how long the 400 errors were occurring, but you would have had to have Live Logging running overnight to see.

At this point, try re-authenticating to the Ecobee Servers - even if Ecobee Suite Manager says you are already connected. If that works, then we need to keep an eye on your logs to see if it happens again. The code will usually recover from Ecobee outages, but if the outage is too long, Ecobee invalidates your token and forces you to log back in...

Keep us posted!

That fixed it. Everything is responding properly. Thank you.

101 Registered Users!

As of this morning, there are 101 users who have at least authenticated Ecobee Suite 1.7.**!!!

We have 73 users on SmartThings and 28 users on Hubitat...

2 Likes

Universal Ecobee Suite updated on 1 June, 2019 at 1:15pm EDT

Added 1 feature and fixed SMS text string for new SamsungConnect app compatibility

  • Ecobee Suite Manager, Contacts & Switches, Mode/Switches/Programs, Smart Mode, Smart Room, Thermal Comfort, and Working From Home Helpers
    • Fixed SMS text entry for the New Samsung Connect app
  • Ecobee Suite Contacts & Switches Helper
    • New Feature If the HVAC is already in Off mode when the first contact sensors opens or the first switch is engaged, then when all the contacts & switches are closed again, it will NOT turn the HVAC back on.

These updates are not manadatory