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.
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.
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...
Added 1 feature and fixed SMS text string for new SamsungConnect app compatibility
These updates are not manadatory
Found more errors with contacts and sensors:
app:29902019-06-03 09:18:34.397 am errorgroovy.lang.MissingMethodException: No signature of method: user_app_sandood_ecobee_Suite_Open_Contacts_1387.numOn() is applicable for argument types: () values: [] Possible solutions: run(), run(), dump(), run(java.io.File, [Ljava.lang.String;), main([Ljava.lang.String;), use([Ljava.lang.Object;) on line 402 (sensorOpened)
app:29902019-06-03 09:18:34.224 am tracesensorOpened() entered with event Door Sensor - Patio Door contact: open
app:29902019-06-03 09:01:14.192 am traceNo action to perform yet...
app:29902019-06-03 09:01:14.166 am infoReturning false
app:29902019-06-03 09:01:14.029 am tracesensorClosed() entered with event Door Sensor - Patio Door contact: closed
app:29902019-06-03 09:00:57.876 am errorgroovy.lang.MissingMethodException: No signature of method: user_app_sandood_ecobee_Suite_Open_Contacts_1387.numOn() is applicable for argument types: () values: [] Possible solutions: run(), run(), dump(), run(java.io.File, [Ljava.lang.String;), main([Ljava.lang.String;), use([Ljava.lang.Object;) on line 402 (sensorOpened)
app:29902019-06-03 09:00:57.801 am tracesensorOpened() entered with event Door Sensor - Patio Door contact: open
app:29902019-06-03 08:59:35.542 am errorgroovy.lang.MissingMethodException: No signature of method: user_app_sandood_ecobee_Suite_Open_Contacts_1387.numOn() is applicable for argument types: () values: [] Possible solutions: run(), run(), dump(), run(java.io.File, [Ljava.lang.String;), main([Ljava.lang.String;), use([Ljava.lang.Object;) on line 402 (sensorOpened)
app:29902019-06-03 08:59:35.311 am tracesensorOpened() entered with event Door Sensor - Front Door contact: open
So I noticed a whole bunch of errors everywhere with the mode helper app and the smart circulation app. I decided to remove the ecobee suite and reinstall. So far I am not seeing any issues in the logs. I will keep you posted. The above post may still be relevant though.
So after the reinstall I do not see any of the errors anymore. I see the helper app for contacts/sensors is detecting when open/close. BUT It isn't doing anything. Meaning if the doors are all closed it does not set the Ecobee on for the mode that is currently set.
Thoughts?
Do you see any errors in Live Logging for the Helper, the Thermostat or the Manager when it doesn't do what it is supposed to do?
Try configuring with only 1 door, does that work?
OK so I think I have a configuration issue maybe? Even with one door it isn't working.
Contact/Sensor Logs:
app:29982019-06-04 11:07:52.660 am infoNotifications sent
app:29982019-06-04 11:07:52.238 am traceNotification Message: All contact sensors are closed, running HVAC On actions for EcobeeTherm: Ecobee - Home.
app:29982019-06-04 11:07:52.209 am infoEcobeeTherm: Ecobee - Home is already in Off
app:29982019-06-04 11:07:52.162 am traceturnonHVAC() entered
app:29982019-06-04 11:07:52.137 am infoThe on delay is 0
app:29982019-06-04 11:07:52.106 am traceAll Contact Sensors & Switches are reset, initiating actions.
app:29982019-06-04 11:07:52.070 am infoReturning true
app:29982019-06-04 11:07:52.038 am infoAll contact sensors are closed
app:29982019-06-04 11:07:51.949 am tracesensorClosed() entered with event Door Sensor - Front Door contact: closed
app:29982019-06-04 11:05:33.590 am traceinitialize() exiting
app:29982019-06-04 11:05:33.553 am warnInitialized while should be 'Off' - can't update states
app:29982019-06-04 11:05:33.524 am traceswitchOffState = false
app:29982019-06-04 11:05:33.475 am tracecontactOffState = true
app:29982019-06-04 11:05:33.405 am infoEcobee Suite Contacts & Switches Helper, version 1.7.08 on Hubitat Initializing...
app:29982019-06-04 11:05:33.337 am debugupdated() entered
Ecobee Suite Manager Logs:
app:29972019-06-04 11:08:32.497 am traceUpdates sent (271 / 2673ms)
app:29972019-06-04 11:08:32.200 am tracePrep complete (1948ms)
app:29972019-06-04 11:08:31.822 am infoupdateThermostatData() - 8 updates for 1 thermostat (Ecobee - Home)
app:29972019-06-04 11:08:30.958 am infoupdateThermostatData() - Updating event data for thermostat Ecobee - Home (311020479333)
app:29972019-06-04 11:08:30.742 am infoParsing complete
app:29972019-06-04 11:08:30.403 am infoParsing data for thermostat Ecobee - Home (311020479333)
app:29972019-06-04 11:08:29.914 am infoRequesting ( equipmentStatus runtime sensors weather ) for thermostat Ecobee - Home (311020479333)
app:29972019-06-04 11:08:29.782 am infoPolling thermostat Ecobee - Home (311020479333)
app:29972019-06-04 11:07:52.687 am infoContact & Switches Notifications sent
app:29972019-06-04 11:07:52.263 am traceContact & Switches Notification Message: All contact sensors are closed, running HVAC On actions for EcobeeTherm: Ecobee - Home.
app:29972019-06-04 11:07:52.233 am infoContact & Switches EcobeeTherm: Ecobee - Home is already in Off
app:29972019-06-04 11:07:52.101 am infoContact & Switches Returning true
app:29972019-06-04 11:07:52.065 am infoContact & Switches All contact sensors are closed
app:29972019-06-04 11:07:52.027 am traceContact & Switches sensorClosed() entered with event Door Sensor - Front Door contact: closed
app:29972019-06-04 11:05:33.618 am traceContact & Switches initialize() exiting
app:29972019-06-04 11:05:33.582 am warnContact & Switches Initialized while should be 'Off' - can't update states
app:29972019-06-04 11:05:33.548 am traceContact & Switches switchOffState = false
app:29972019-06-04 11:05:33.514 am traceContact & Switches contactOffState = true
app:29972019-06-04 11:05:33.453 am infoContact & Switches Ecobee Suite Contacts & Switches Helper, version 1.7.08 on Hubitat Initializing...
Screenshots of Contacts/Sensors:
Screenshots of Ecobee Suite Manager:
Feature enhancement: can the pushover notifications in each helper not be a required field? I really don't want notifications after I get this up and running correctly.
You should have gotten a warning during setup that the door was open and it couldn't save the proper state.
app:29972019-06-04 11:05:33.582 am warnContact & Switches Initialized while should be 'Off' - can't update states
Try closing the door, turning the HVAC to the mode you want it to be when all the doors are closed, and try configuring the Helper again...
Simple, change your answer to this question in setup:
Select which actions to take [Default=Notify Only]
to: HVAC Actions Only
That did it! Thx!!
So, the Helper is working now? Have you tried with multiple doors also?