search

FlyingDiver / Indigo-Ecobee-2

Ecobee thermostat plugin for Indigo Home Automation System
The Unlicense
0 stars 0 forks source link

token expired #11

Closed smuseby closed 3 years ago

smuseby commented 3 years ago

renewed within last 7(?) days - certainly within last 30 days. Yesterday, from event log:

2020-11-15 19:01:13.985 Ecobee 2 Error Token Refresh Error, error = invalid_request 2020-11-15 19:03:14.396 Ecobee 2 Error Ecobee Account (1428206274): Ecobee Account Update failed, response = '{ "status": { "code": 14, "message": "Authentication token has expired. Refresh your tokens. " } }' 2020-11-15 19:06:14.849 Ecobee 2 Error Ecobee Account (1428206274): Authentication lost, please re-authenticate 2020-11-15 19:11:15.308 Ecobee 2 Error Ecobee Account (1428206274): Authentication lost, please re-authenticate 2020-11-15 19:16:15.820 Ecobee 2 Error Ecobee Account (1428206274): Authentication lost, please re-authenticate

FlyingDiver commented 3 years ago

Please confirm plugin version. Should be 2.2.5.

Is the plugin still in the same state? Are you still getting the same message every 5 minutes? If so, turn on debug logging and post the output when it tries again.

smuseby commented 3 years ago

The plug-in is v 2.2.5 I re-authenticated my ecobee account. There was another anomaly just prior to the token expiration - perhaps related? - as follows: I have an Indigo control page that I use to alter the thermostat settings with 2 buttons, +1C, and -1C (using two action groups). (I confirmed the accuracy of the two action groups). The +1 button changed the setting +11C and I couldn't alter that setting with the -1 button,; resetting to 20C at the thermostat, the -1 changed the setting appropriately twice, and then stopped. I was able to reproduce the behavior. Trying again now, the +1 button produced:

   Ecobee 2                        fHall Thermostat: set heat to: 57.2 and leave cool at: 18.3
   Ecobee 2 Error                  Error in plugin execution ExecuteAction:

Traceback (most recent call last):
  File "plugin.py", line 656, in actionControlThermostat
  File "plugin.py", line 787, in handleChangeSetpointAction
  File "/Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/Ecobee 2.indigoPlugin/Contents/Server Plugin/ecobee_devices.py", line 224, in set_hold_temp
  File "/Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/Ecobee 2.indigoPlugin/Contents/Server Plugin/ecobee_account.py", line 229, in make_request
AttributeError: EcobeeAccount instance has no attribute 'access_token'

I confirmed that the plug-in is currently authenticated. Turning on Detailed Debugging, and pressing the +1 button produces:

 Nov 16, 2020 at 3:18:05 PM
   Ecobee 2 Debug                  logLevel = 5
   Ecobee 2 Debug                  updateFrequency = 900.0
   Ecobee 2 Debug                  setting temperature scale to C
   Ecobee 2 Debug                  fHall Thermostat: action.thermostatAction: IncreaseHeatSetpoint
   Ecobee 2                        fHall Thermostat: set heat to: 57.2 and leave cool at: 18.3
   Ecobee 2 Error                  Error in plugin execution ExecuteAction:

Traceback (most recent call last):
  File "plugin.py", line 656, in actionControlThermostat
  File "plugin.py", line 787, in handleChangeSetpointAction
  File "/Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/Ecobee 2.indigoPlugin/Contents/Server Plugin/ecobee_devices.py", line 224, in set_hold_temp
  File "/Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/Ecobee 2.indigoPlugin/Contents/Server Plugin/ecobee_account.py", line 229, in make_request
AttributeError: EcobeeAccount instance has no attribute 'access_token'

I reloaded the plugin, pressed +1, and it changed the thermostat (iOS) to 57.2F; pressed a second time, sent it to 95F, and a minute lated to 22.9 (Having started at 13C, the correct value would be 15C). Pressed the -1C and it went to 95.0F, changing after a minute to 21.9C (so perhaps the 95.0F is some temporary value pending a conversion to C?).

Attempting to change the setting in Indigo>Device by pressing the down button produces a similar result:

Nov 16, 2020 at 3:26:03 PM
   Ecobee 2 Debug                  fHall Thermostat: action.thermostatAction: DecreaseHeatSetpoint
   Ecobee 2                        fHall Thermostat: set heat to: 71.42 and leave cool at: 18.3
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>
   Trigger                         fHallStatSetPt2var
   Ecobee 2 Debug                  fHall Thermostat: action.thermostatAction: DecreaseHeatSetpoint
   Ecobee 2                        fHall Thermostat: set heat to: 95 and leave cool at: 18.3
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>
   Trigger                         fHallStatSetPt2var
   Ecobee 2 Debug                  fHall Thermostat: action.thermostatAction: DecreaseHeatSetpoint
   Ecobee 2                        fHall Thermostat: set heat to: 95 and leave cool at: 18.3
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>
   Ecobee 2 Debug                  fHall Thermostat: action.thermostatAction: DecreaseHeatSetpoint
   Ecobee 2                        fHall Thermostat: set heat to: 95 and leave cool at: 18.3
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>
   Ecobee 2 Debug                  fHall Thermostat: action.thermostatAction: DecreaseHeatSetpoint
   Ecobee 2                        fHall Thermostat: set heat to: 95 and leave cool at: 18.3
   Ecobee 2 Debug                  API 'set hold temp' request completed, result = <Response [200]>

I think this rules out an Action Group issue. Enough???

FlyingDiver commented 3 years ago

I can't replicate the access_token error. You appear to still be loosing it, even with the changes I made in 2.2.5. I have no idea why. No one else has reported anything like this.

On the other hand, there's definitely something weird going on with the temperature scale. I didn't write that code, it came over from the original Ecobee plugin more or less intact. And it's definitely broken. It assumes Fahrenheit unless overridden and I don't think the over-ride is applied properly.

FlyingDiver commented 3 years ago

Since I can't replicate this on demand, I need you to try out some things. First, when you're not having an authentication issue, do your setpoint actions work properly? Up and Down? Is there some sequence that always causes the issue?

If you CAN replicate the set point errors, please set the temperature scale to F and repeat the tests. You might want to change your actions to 2 degrees. Or not.

FlyingDiver commented 3 years ago

Moving all the temperature scaling issues to new issue #12.

smuseby commented 3 years ago

All the temperature issues documented today occurred after I re-authenticated yesterday. I'll set it to F tomorrow and see if that makes a difference.

smuseby commented 3 years ago

Sorry about your father. It’s never good to be ill, but it’s a particularly bad time now. No rush - I can manage the heater at the thermostat or with the internet interface. Be safe.

On Mon, Nov 16, 2020 at 15:31 Joe Keenan notifications@github.com wrote:

Yeah, that should be enough to track it down. Not sure when I'll get to it, my Father is in the hospital and I'm going to visit him tomorrow. That's going to take me all day.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-728405092, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3DTORKSWD774EPPRTTSQGY4XANCNFSM4TXQQORQ .

-- Robert Smith h: 510.524.0080 m: 510.529.1995

FlyingDiver commented 3 years ago

So what's the actual status of this issue? Is it repeatable? You posted in the other issue that you restarted after a power failure without any authentication issues.

smuseby commented 3 years ago

Sorry - I've been distracted. Once again - last night - I lost the ability to control the thermostat with Indigo - as follows: To work around the scaling issue, Last night, I created buttons on an indigo control page to activate ecobee comfort settings(?) - e.g., 20C. I tested them, and they worked. Later, I noticed that the thermostat was still calling for heat when the schedule for 15C should have reset the thermostat. My control page buttons were now not working, and the event log revealed that the authentication had expired. Just now, I made the screenshot below of both event log and device settings

On Thu, Nov 19, 2020 at 12:43 PM Joe Keenan notifications@github.com wrote:

So what's the actual status of this issue? Is it repeatable? You posted in the other issue that you restarted after a power failure without any authentication issues.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-730625884, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3GCFWZE7LKOUCGMDWTSQV7NXANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

Looks like the screen shot did not get included in the issue. Please add it on the website (not email).

FlyingDiver commented 3 years ago

Also, please upload screen shots of your action groups or control page controls. Apparently, whatever you're doing to set modes or temperatures is breaking the authentication (I have no idea how), so I want to see exactly what actions you're using.

And as always, I need the debug level logs from when this happens. Paste the log text into the issue. Please don't use screen shots of the event log.

smuseby commented 3 years ago
Screen Shot 2020-11-21 at 11 34 18 2 Screen Shot 2020-11-21 at 11 34 18 2

Screen Shot 2020-11-21 at 13 34 46

Notice that the authentication codes for both houses are being updated. Front Hall and North Office are local; Stairs is remote.

2020-11-20 19:00:57.926 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for 'Front Hall', 521703550260
2020-11-20 19:00:57.926 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for remote sensor 'North Office', C5SW
2020-11-20 19:00:57.926 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for 'Stairs', 521781046633
2020-11-20 19:00:57.926 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 19:00:57.929 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 19:00:57.929 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:00:57.929 Trigger fHallTemp2var
2020-11-20 19:01:05.147 Ecobee 2 Error  Token Refresh Error, error = invalid_request
2020-11-20 19:01:43.908 Schedule    pOFFflONautoOFF (delayed action)
2020-11-20 19:01:50.911 Schedule    _delayed_action_31
2020-11-20 19:01:51.180 Sent INSTEON    "bHallStrsPwayLOAD" off
2020-11-20 19:06:05.169 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:06:05.628 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:11:05.640 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:11:06.086 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:16:06.108 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 19:16:06.108 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 19:16:06.110 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 19:16:06.111 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:16:06.541 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:21:06.569 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:21:06.999 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:26:07.027 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:26:07.452 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:31:07.532 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 19:31:07.532 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 19:31:07.534 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 19:31:07.534 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:31:07.966 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:36:07.982 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:36:08.408 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:41:08.425 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:41:08.888 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:46:08.899 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 19:46:08.899 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 19:46:08.901 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 19:46:08.902 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:46:09.332 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:51:09.415 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:51:09.862 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:56:09.878 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 19:56:10.309 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 19:56:22.458 Trigger track fYrd temp to variable
2020-11-20 20:01:10.330 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 20:01:10.330 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 20:01:10.332 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 20:01:10.333 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:01:10.978 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:06:11.032 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:06:11.577 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:11:11.602 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:11:12.330 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:16:12.375 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 20:16:12.375 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 20:16:12.377 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 20:16:12.377 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:16:12.805 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:21:12.840 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:21:13.264 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:26:13.284 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:26:13.714 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:31:13.719 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 20:31:13.720 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 20:31:13.722 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 20:31:13.723 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:31:15.387 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:36:15.399 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:36:15.928 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:41:15.952 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:41:16.384 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:46:16.400 Ecobee 2 Debug  Ecobee account 1428206274 not authenticated, skipping update
2020-11-20 20:46:16.400 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 20:46:16.403 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 20:46:16.403 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:46:16.814 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:51:16.837 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:51:17.258 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
2020-11-20 20:56:17.281 Ecobee 2 Debug  Token Request with refresh_token = SlVwuSzWioKHGdGlaxqQoRzI8VmduZIZ
2020-11-20 20:56:17.706 Ecobee 2 Error  Ecobee Account (1428206274): Authentication lost, please re-authenticate
smuseby commented 3 years ago

Could you please hide all the account data I just uploaded - publicly? I assume you don't have a lot of traffic here, but I'd prefer that it not be available. Thanks. Hope your father is getting better. Bob

On Sat, Nov 21, 2020 at 12:30 PM Joe Keenan notifications@github.com wrote:

Also, please upload screen shots of your action groups or control page controls. Apparently, whatever you're doing to set modes or temperatures is breaking the authentication (I have no idea how), so I want to see exactly what actions you're using.

And as always, I need the debug level logs from when this happens.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731632654, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3FQZOQEANA5H3KMITDSRAPOTANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

What account information? Your login and password aren't logged, and the tokens are random strings that only work with your account.

FlyingDiver commented 3 years ago

Ok, going through the log I see an update from the Ecobee servers at 2020-11-20 19:00:57.926, so the authentication was good at that point.

Then there's this line: 2020-11-20 19:00:57.929 Trigger fHallTemp2var

What is that? I need to see what activated the trigger, and what actions the trigger attempted.

The next thing I see is the failed token refresh at 2020-11-20 19:01:05.147.

Notice that the authentication codes for both houses are being updated. Front Hall and North Office are local; Stairs is remote.

But it's all on the same Ecobee account, right? So there's only one authentication token, for the account. Each device checks to see if the account is currently authenticated.

Turn off detailed debugging, I don't think I need that data. I've deleted it from the post above. But what I don't see if the previous successful authentication attempt. Or anything else that happened in between.

smuseby commented 3 years ago

I previously authenticated the account several days ago. I just authenticated it again, and the device screen before and after screenshots are below. Below are screenshots from the trigger you requested. Then I attempted to change the temperature with an action group/comfort setting - event log screenshot attached. View screenshots from bottom up. Screen Shot 2020-11-21 at 11.34.18.pdf

Screen Shot 2020-11-21 at 19 11 33 Screen Shot 2020-11-21 at 18 58 15 Screen Shot 2020-11-21 at 18 56 26 Screen Shot 2020-11-21 at 18 53 42 Screen Shot 2020-11-21 at 18 52 55
FlyingDiver commented 3 years ago

Sorry to be pedantic about this, but you're really making this much harder for me than it needs to be.

  1. I don't need screenshots of the Ecobee Account config dialog. That's not changing.
  2. I want TEXT from the event log, not a screen shot. And I want all the stuff before and after the error message.

I need to check the code, but I thought it would (debug) log any commands to change set points. But I've never seen any of those commands logged in the stuff you've sent me.

And just for my curiosity - why are you copying the state into a variable? What are you using the variable for that you can't use the state? Obviously, you should be able to do this, so it shouldn't be causing this issue.

FlyingDiver commented 3 years ago

Yeah, I just looked. Anytime you send an actual command to the thermostat, there should be a line in the debug log with the text " action.thermostatAction:" in it (following the device name). Are you seeing those?

FlyingDiver commented 3 years ago

And, again, I need to see the actual action groups you're using to send the commands. Screenshots are fine.

smuseby commented 3 years ago

I thought I sent you the AGroups. I have a new theory: in our main home, indigo>device, the ecobee account is '274; at tahoe, it's '757. In Indigo/iOS, the Tahoe account has a green dot, our home has a red dot - it seems if I can get it authenticated, it's is temporary, whereas the Tahoe one persists. I'm wondering if in the process of setting up the thermostats, I did something wrong and have two account numbers, when I should only have one. That may explain why no one else has experienced my authentication issue. We're leaving tomorrow morning for Tahoe for a week, so I won't be able to be as responsive as I'd like until we return. Bob

FlyingDiver commented 3 years ago

You have two installs of Indigo? Or did you create two Ecobee account devices with the same login information? Or do you actually have two different Ecobee accounts?

smuseby commented 3 years ago

Is this what you want? Debugging turned off, and I can get something different it that would be helpful.

2020-11-20 00:01:32.768 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for 'Front Hall', 521703550260
2020-11-20 00:01:32.768 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for remote sensor 'North Office', C5SW
2020-11-20 00:01:32.768 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for 'Stairs', 521781046633
2020-11-20 00:01:32.769 Ecobee 2 Debug  fHall Thermostat: Updating device
2020-11-20 00:01:32.771 Ecobee 2 Debug  Ecobee Front Hall Remote - North Office: Updating device
2020-11-20 00:01:32.777 Trigger fHallTemp2var
2020-11-20 00:16:33.300 Ecobee 2 Debug  Ecobee Account (1428206274): Ecobee Account Update OK, got info on 2 thermostats
2020-11-20 00:16:33.304 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for 'Front Hall', 521703550260
2020-11-20 00:16:33.304 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for remote sensor 'North Office', C5SW
2020-11-20 00:16:33.304 Ecobee 2 Debug  Ecobee Account (1428206274): getting data for 'Stairs', 521781046633
smuseby commented 3 years ago

I'm sorry - but I've lost track of which action group I need to send you. As for your question about the trigger - I had to think a bit: it's left over from a previous thermostat (Proliphix) and it was a work-around as I believe the issue was that there was no way to access the device temperature value. I'll fix it.

On Sat, Nov 21, 2020 at 7:23 PM Joe Keenan notifications@github.com wrote:

Sorry to be pedantic about this, but you're really making this much harder for me than it needs to be.

  1. I don't need screenshots of the Ecobee Account config dialog. That's not changing.
  2. I want TEXT from the event log, not a screen shot. And I want all the stuff before and after the error message.

I need to check the code, but I thought it would (debug) log any commands to change set points. But I've never seen any of those commands logged in the stuff you've sent me.

And just for my curiosity - why are you copying the state into a variable? What are you using the variable for that you can't use the state? Obviously, you should be able to do this, so it shouldn't be causing this issue.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731691219, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3CPU6ZLQDGCLN3D3E3SRB73HANCNFSM4TXQQORQ .

smuseby commented 3 years ago

I checked every day from 11/17 through 11/21: seaching for action.thermostatAction, I found 6 instances on 11/17, and one on 11/20/20.

On Sat, Nov 21, 2020 at 7:26 PM Joe Keenan notifications@github.com wrote:

Yeah, I just looked. Anytime you send an actual command to the thermostat, there should be a line in the debug log with the text " action.thermostatAction:" in it (following the device name). Are you seeing those?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731691892, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3EQPCA2ZA4PEG3YGXLSRCAFXANCNFSM4TXQQORQ .

smuseby commented 3 years ago

I think you want ecobee action groups. I'll post screenshots of one.

On Sat, Nov 21, 2020 at 7:27 PM Joe Keenan notifications@github.com wrote:

And, again, I need to see the actual action groups you're using to send the commands. Screenshots are fine.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731692153, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3GEYV3PLYMTYNVN273SRCAJLANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

Please give me the specifics of: (1) How many Ecobee accounts you have (for the website/app, not Indigo related) (2) How many Indigo installations (servers) you have (3) How many Ecobee devices you have created on each Indigo server, and what types they are.

Please turn OFF detailed debugging. It's very verbose and I don't need that level of data. Set the logging to the simple debugging level.

If there's an instance of "action.thermostatAction" around the time of loosing authentication, I need to see the logs between (and including) those two events. This will help me determine if it's the action somehow causing the loss of authentication. And I need to see the action that's sending that command.

FlyingDiver commented 3 years ago

FYI, from the data I'm seeing (that you posted). I see two thermostats: "Front Hall" (which has a remote sensor "North Office), and "Stairs" (no remote sensor). Which house is this (or is it both)?

smuseby commented 3 years ago

2 houses, 2 indigos Same ecobee login info for 2 stats, one in each house. I don't know if the account is specific for me, or for the devices as I have been unable to find an account number on the internet interface. When setting up, Ecobee tech support showed me how to create a second house for the second thermostat. Note the 'change home' at the top left. [image: Screen Shot 2020-11-22 at 12.55.57.png]

On Sat, Nov 21, 2020 at 8:10 PM Joe Keenan notifications@github.com wrote:

You have two installs of Indigo? Or did you create two Ecobee account devices with the same login information? Or do you actually have two different Ecobee accounts?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731695526, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3BIEIFNO5ZJ7YTQCSDSRCFJPANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

You can't include a screen shot via email. Only on the web site.

The account is for you. It's based on your email address. You can have multiple locations (houses), and each location can have multiple devices (thermostats).

So now I'm wondering if their API doesn't allow multiple instances of the same "app" (which is the plugin). So when the second Indigo instance authenticates, it drops the first one.

smuseby commented 3 years ago

(1) How many Ecobee accounts you have (for the website/app, not Indigo related) Not clear - see previous message. (2) How many Indigo installations (servers) you have 2 servers (3) How many Ecobee devices you have created on each Indigo server, and what types they are. At Tahoe, one thermostat At home, one thermostat, and one remote sensor. Detailed debugging is off Looking for instances of 'action.thermostataction' is going to take a bit of time. I'll get back to you. Heater Action Group screen shots:

[image: Screen Shot 2020-11-22 at 13.07.06.png]

[image: Screen Shot 2020-11-22 at 13.07.58.png]

[image: Screen Shot 2020-11-22 at 13.08.33.png]

[image: Screen Shot 2020-11-22 at 13.09.14.png]

[image: Screen Shot 2020-11-22 at 13.10.25.png]

On Sun, Nov 22, 2020 at 10:14 AM Joe Keenan notifications@github.com wrote:

Please give me the specifics of: (1) How many Ecobee accounts you have (for the website/app, not Indigo related) (2) How many Indigo installations (servers) you have (3) How many Ecobee devices you have created on each Indigo server, and what types they are.

Please turn OFF detailed debugging. It's very verbose and I don't need that level of data. Set the logging to the simple debugging level.

If there's an instance of "action.thermostatAction" around the time of loosing authentication, I need to see the logs between (and including) those two events. This will help me determine if it's the action somehow causing the loss of authentication. And I need to see the action that's sending that command.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731801432, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3DKXVL543C4GIWFXQDSRFIIJANCNFSM4TXQQORQ .

smuseby commented 3 years ago

That's both houses: Front Hall is main house Stairs is Tahoe house

On Sun, Nov 22, 2020 at 10:18 AM Joe Keenan notifications@github.com wrote:

FYI, from the data I'm seeing (that you posted). I see two thermostats: "Front Hall" (which has a remote sensor "North Office), and "Stairs" (no remote sensor). Which house is this (or is it both)?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731803385, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3GKBNDLPA3MW3WECODSRFIYBANCNFSM4TXQQORQ .

smuseby commented 3 years ago

What I've noticed has been a little inconsistent: I've never had a problem at Tahoe since you modified the plug-in with the last version. At the main house, until recently, the authentication expired quickly (days); as of yesterday, I am unable to authenticate at all. I just emailed a bunch of screen shots. - they seemed me specific. I'll repost them to the website.

On Sun, Nov 22, 2020 at 1:04 PM Joe Keenan notifications@github.com wrote:

You can't include a screen shot via email. Only on the web site.

The account is for you. It's based on your email address. You can have multiple locations (houses), and each location can have multiple devices (thermostats).

So now I'm wondering if their API doesn't allow multiple instances of the same "app" (which is the plugin). So when the second Indigo instance authenticates, it drops the first one.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731846904, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3HZU5E2RMAJNXP72R3SRF4GPANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

Are you posting those screenshots here on GitHub?

FlyingDiver commented 3 years ago

Since you have one login to the Ecobee website, and you use that to manage both locations and both thermostats, you have ONE Ecobee account.

The only thing at all unusual about your situation is that you have two Indigo servers running the same plugin with the same Ecobee account. I don't know of anyone else doing that full-time. On the other hand, I occasionally run two Indigo instances when I'm working on the plugin and have it running on both my house (production) system and my development system. But I don't leave it that way for hours at a time. I shut the development system down when I'm done for the day.

smuseby commented 3 years ago

Sample Ecobee thermostat action group (screenshots):

Screen Shot 2020-11-22 at 13 57 57 Screen Shot 2020-11-22 at 13 58 39 Screen Shot 2020-11-22 at 13 59 00 Screen Shot 2020-11-22 at 13 59 41
FlyingDiver commented 3 years ago

Those all look as I would expect. I'm running an experiment here, going to leave both systems running with the Ecobee plugin enabled and see what happens.

smuseby commented 3 years ago

Back online. Looking forward to hearing from you.

On Sun, Nov 22, 2020 at 14:05 Joe Keenan notifications@github.com wrote:

FlyingDiver commented 3 years ago

Ran all night, no errors.

FlyingDiver commented 3 years ago

Still no errors. I'm thinking it's just not likely that it's an API issue.

Are your two Indigo systems totally independent? There's no shared file system or anything like that? Were files (like plugin preferences or the Indigo database) ever copied from one system to the other?

smuseby commented 3 years ago

Totally independent. Over the last year, as I was trying to figure out and implement python scripts, I copied stuff, but I do not recall having done so for the thermostats. But to be honest, I can't be 100% certain. Since I am no longer able to even authenticate the thermostat at our home, maybe I have to delete the device and start over? Or maybe call Ecobee tech support? I'm at Tahoe now, and there are no issues.

On Mon, Nov 23, 2020 at 12:13 PM Joe Keenan notifications@github.com wrote:

Still no errors. I'm thinking it's just not likely that it's an API issue.

Are your two Indigo systems totally independent? There's no shared file system or anything like that? Were files (like plugin preferences or the Indigo database) ever copied from one system to the other?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-732400207, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3CH7LZT5L2AIF6VQX3SRK65LANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

You mean when you attempt to go through the authentication process in the Account device's configuration dialog, it fails? At what point, and is there anything in the log when it happens?

smuseby commented 3 years ago

it was in the verbose event log I sent earlier. I'll see if I can find it.

On Mon, Nov 23, 2020 at 12:32 PM Joe Keenan notifications@github.com wrote:

You mean when you attempt to go through the authentication process in the Account device's configuration dialog, it fails? At what point, and is there anything in the log when it happens?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-732409708, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3EER4T5EUBP2RPH4QTSRLBEFANCNFSM4TXQQORQ .

smuseby commented 3 years ago

I logged onto my home Indigo, and was able to authenticate my account - nothing appeared in my event log however. I reloaded the plug-in, and activated the action group to change the setting to 13C, and confirmed it at the device. All seems to be working. I'll keep watching it.

Event log: `Nov 23, 2020 at 4:40:05 PM Reloading plugin "Ecobee 2 2.2.5" Stopping plugin "Ecobee 2 2.2.5" (pid 45346) Ecobee 2 Ecobee Account ('274): Stopping EcobeeAccount Device '274 Ecobee 2 Ecobee Front Hall Occupancy: Stopping OccupancySensor Device 379356500 Ecobee 2 Ecobee Front Hall Remote - North Office: Stopping RemoteSensor Device 1917353578 Ecobee 2 fHall Thermostat: Stopping EcobeeThermostat Device 1716992129 Ecobee 2 Stopping Ecobee Stopped plugin "Ecobee 2 2.2.5" Starting plugin "Ecobee 2 2.2.5" (pid 51220) Started plugin "Ecobee 2 2.2.5" Ecobee 2 Starting Ecobee Ecobee 2 Ecobee Account ('274): Starting EcobeeAccount Device xxx274 Ecobee 2 Ecobee Front Hall Occupancy: Starting OccupancySensor Device 379356500 Ecobee 2 Ecobee Front Hall Remote - North Office: Starting RemoteSensor Device 1917353578 Ecobee 2 fHall Thermostat: Starting EcobeeThermostat Device 1716992129

Nov 23, 2020 at 4:40:28 PM Action Group htr ON 13C

`

smuseby commented 3 years ago

Is there a state label for the ecobee thermostat that I can access for the current setpoint? I've tried the following, with no luck:

%%d:1508415945:setpoint%% - New setpoint %%d:1508415945:heatSetpoint%% - New setpoint %%d:1508415945:temperature%% - New setpoint %%d:1508415945:Heat Setpoint%% - New setpoint

Bob

On Mon, Nov 23, 2020 at 5:54 AM Joe Keenan notifications@github.com wrote:

Ran all night, no errors.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-732176230, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3FP5AZUGV46I7PCZDLSRJSS3ANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

It's not a custom state. According to the wiki: https://wiki.indigodomo.com/doku.php?id=indigo_7.3_documentation:device_class&s[]=setpoint#thermostatdevice

It's setpointCool and setpointHeat

smuseby commented 3 years ago

That worked. Did not know about that documentation - hope I can find it again. Thanks.

On Thu, Dec 3, 2020 at 12:59 PM Joe Keenan notifications@github.com wrote:

It's not a custom state. According to the wiki: https://wiki.indigodomo.com/doku.php?id=indigo_7.3_documentation:device_class&s[]=setpoint#thermostatdevice

It's setpointCool and setpointHeat

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-738303221, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3EOBE4H5QZ2SVPNZGDSS732TANCNFSM4TXQQORQ .

smuseby commented 3 years ago

Can't say why, but there have been no ecobee failures requiring an account reset since we last emailed. Works for me. Have you made any progress with the issue of changing the set point incrementally from Indigo? To remind you, when I press the up arrow from say 20C, the resulting value is 95F. I'm trying to report the temperature at the thermostat in a Better Email message. The only states I can find on the Indigo website are temperature, Temperature and temperatures. None work. Hope all is well with you. Happy New Year, Bob

On Sun, Nov 22, 2020 at 1:35 PM Joe Keenan notifications@github.com wrote:

Since you have one login to the Ecobee website, and you use that to manage both locations and both thermostats, you have ONE Ecobee account.

The only thing at all unusual about your situation is that you have two Indigo servers running the same plugin with the same Ecobee account. I don't know of anyone else doing that full-time. On the other hand, I occasionally run two Indigo instances when I'm working on the plugin and have it running on both my house (production) system and my development system. But I don't leave it that way for hours at a time. I shut the development system down when I'm done for the day.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731850821, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3HSS5C3B2M2JMBVF63SRF7YNANCNFSM4TXQQORQ .

FlyingDiver commented 3 years ago

I have not worked on the temperature scaling issue lately. Holidays and gaming season. It's tracked in https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/12.

smuseby commented 3 years ago

Enjoy yourself.

On Tue, Dec 29, 2020 at 20:23 Joe Keenan notifications@github.com wrote:

I have not worked on the temperature scaling issue lately. Holidays and gaming season. It's tracked in #12 https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/12.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-752322743, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3CGJQOON65TRVZQV5DSXKTNLANCNFSM4TXQQORQ .

-- Robert Smith h: 510.524.0080 m: 510.529.1995

smuseby commented 3 years ago

I spoke too soon. Last night, I discovered that I could not manage my vacation home thermostat. The event log had a new (to me) message: 2020-12-30 21:57:58.265 Ecobee 2 Warning API 'set climate hold' request failed, result = { "status": { "code": 3, "message": "Processing error. selection.selectionMatch is required." } } Reestablishing the account with Ecobee did not solve the issue; I had to delete the device and reinstall it. I have no information as to the cause. If you can make a suggestion, I'll search the event log.

On Sun, Nov 22, 2020 at 2:05 PM Joe Keenan notifications@github.com wrote:

Those all look as I would expect. I'm running an experiment here, going to leave both systems running with the Ecobee plugin enabled and see what happens.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-Ecobee-2/issues/11#issuecomment-731854615, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3EUQROGAK4V6NYJU63SRGDLVANCNFSM4TXQQORQ .