BUG: Change SetPoint in Auto Mode

[ukie]

When my smart thermostat is operating in AUTO mode and I adjust the cool temp down, I get the following in the event log:

Code: Select all

Ecobee 2                        Ecobee Upstairs: set cool to: 77.0 and leave heat at: 67.0
Ecobee 2                       Ecobee Upstairs: set heat to: 66.0 and leave cool at: 78.0

Where the initial temp was set to 78 and 67.
So it ends up changing only the heat set point and the cool point remains as is.

[FlyingDiver]

Can you do that again with debug logging on?

I assume if you're in Cool or Heat mode and you adjust the setpoint it does it correctly?

[ukie]

Code: Select all

Ecobee 2                        Ecobee Upstairs: set cool to: 77.0 and leave heat at: 68.0
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>
   Ecobee 2 Debug                  Ecobee Upstairs: action.thermostatAction: DecreaseHeatSetpoint
   Ecobee 2                        Ecobee Upstairs: set heat to: 67.0 and leave cool at: 78.0
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>

This is happening only through the Indigo App HVAC interface. Adjusting it directly from the Indigo Mac Client works properly since it has two arrows for both cool setpoint and heat setpoint.

[FlyingDiver]

This is happening only through the Indigo App HVAC interface. Adjusting it directly from the Indigo Mac Client works properly since it has two arrows for both cool setpoint and heat setpoint.

I'm sorry, I don't know what you mean. You mean the Indigo Touch iOS app? I've never tried using that for this plugin.

[ukie]

Yes, the Indigo iOS app has an HVAC interface.
https://photos.app.goo.gl/nsqqjDpeYr5Pt2yv9

[FlyingDiver]

Ok, I'm going to test with that. I wonder if it's actually a bug in that HVAC UI?

[FlyingDiver]

OK, so what's the expected behavior with that single set of buttons in the touch UI? Change both setpoints each press?

[jay (support)]

Yes - the server issues separate setpoint change messages.

[FlyingDiver]

For now, ignore the log messages and let me know if the actual UI (Mac client, touch client, and Ecobee app) are showing the correct values after a change from the touch UI.

[ukie]

Ecobee app indeed reflects the Indigo log behavior, only the heat set point changes.

[FlyingDiver]

Ok, I'm getting the same thing. The Indigo touch UI shows both changes, but Ecobee is showing only one change, the last one sent by the server.

[FlyingDiver]

My initial analysis is that there seems to be a race condition between the plugin and the Indigo server, such that the device snapshot (which includes the current setpoints) sent with the commands does not include the change made from the first change command. Looking into a fix now.

[FlyingDiver]

Now tracking this issue in GitHub: https://github.com/FlyingDiver/Indigo-E ... /issues/20

[FlyingDiver]

Try https://github.com/FlyingDiver/Indigo-E ... /tag/2.3.3

[ukie]

This fixed it. Thank you!