Upcoming API Changes Effective December 1, 2020

[FlyingDiver]

The following changes will go into effect on December 1, 2020. If you are unsure whether these changes will have an impact on your solution today, we encourage you to discuss it with your technology team, program manager, other stakeholders and ecobee partners.

Access/Refresh Token Format Changes
Starting from December 1, 2020, ecobee access tokens will no longer be returned as opaque 32-character strings. Access tokens will now be JWTs, which are considerably longer and uses a wider character set. Our JWTs follow the RFC7575 standard for JSON Web Signature tokens.
To ensure your application will continue to work, you will need to ensure that your application supports the following changes:
Access tokens will be up to 7KB in length, and includes upper/lower case alphanumeric characters, hyphens, underscores, and periods.Refresh tokens can be of varying lengths and can contain non-alphanumeric characters.

Authorization Code Changes
The Redirect URI associated with your registered application should be a semi-colon separated list of absolute URLs that start with https://. We do not accept http:// protocol links.

PIN Authorization Changes
PINs will become 10 character alphanumeric strings.This flow is only recommended in situations where a user is interacting with a device that cannot easily use a web-based login form; we recommend migrating to the Authorization Code strategy for a better user experience.
 

[FlyingDiver]

https://www.ecobee.com/home/developer/api/documentation/v1/auth/developer-migration-summary.shtml

[FlyingDiver]

Did a quick code review. No obvious issues with the token format changes or the PIN length.

[FlyingDiver]

Possibly related topic: https://forums.indigodomo.com/viewtopic.php?f=295&t=24686

[Cajun1956]

I removed the plugin app from my Ecobee account & added it back in, the process appeared to be successful . I then issued a set point change from my mobile device. The following is the logger text that pertains to “Ecobee 2”, I stripped out all other lines such as Z-Wave & general stuff like Indigo triggers, Action Groups, Schedule, etc.
Indigo Log 2020-12-09.docx

[FlyingDiver]

That is so strange. Nothing I do recreates the error. I want you to try an experiment. Go through the authentication process again, until you get the line that starts with:

Ecobee 2 Debug Token Request OK, access_token =

Then do NOTHING for an hour. You should see a group of lines that start with this every 15 minutes:

Ecobee 2 Debug Ecobee Account: Ecobee Account Update OK, got info on X thermostats

Then about 45 minutes after the first authentication message, you should get:

   Ecobee 2 Debug                  Token Request with refresh_token = YDVUFnpwrEjpK7oX2JpOCXh5ky51oP6b
   Ecobee 2 Debug                  Token Refresh OK, new access_token = P6cwk6FWh5a6vDthIVPNfZxYblRM5TzB, new refresh_token = zU90mRtAozZ1z9njTWrdQ06wfhfrSPoW, expires_in = 3599

I need to make sure that the scheduled updates work before I can concentrate on the commands failing. After you get the stuff above, then go ahead and try sending a command.

Send the log. Please don't use Word or Pages or anything else that adds formatting. Best would be a plain text document using TextWrangler or BBEdit, but TextEdit will do. Just don't save it as RTF or anything with formatting. Just a .txt extension.

[FlyingDiver]

Never mind getting more logs. I was finally able to reproduce this and capture my own. Somehow the wrong refresh token is getting saved when there's a specific sequence of events around authentication. Turning off the account device, then turning it back on seemed to fix it.

[Cajun1956]

I was just finishing up the txt file when I noticed your update. I have attached it anyhow. I am not sure what you mean by "turning off the account device", but each time I have re-authenticated I have deleted the app in Ecobee & re-added using the new PIN generated by the plugin in Indigo.
IndigoLog 20201209-2.txt

[FlyingDiver]

You turn off the device in Indigo by unchecking the "Comm Enabled" box.

[Cajun1956]

Well that did change something and it seems like it should be working, but data is NOT updating in Indigo. There are errors in log for the remote sensors and I would expect that those values would remain stale, however NONE of the data is updating (not even the thermostat). Log attached.
IndigoLog 20201209-3.txt

[FlyingDiver]

Turn off Detailed Debugging. I'm not going to wade through all that. Then restart the plugin, and if you're still getting errors, post them. I've got a possible fix I'm testing now.

[FlyingDiver]

Try pre-release https://github.com/FlyingDiver/Indigo-Ecobee-2/releases/tag/2.2.6

You will probably need to re-authorize at least one more time.

[FlyingDiver]

Fixed in current releases.