switch to new tado authentication server

[elmi82]

tado is discontinuing the old OAuth2 endpoints at my.tado.com. Starting March 2019, authentication will require retrieving access and refresh tokens from auth.tado.com. The client public-api-preview can be used as is (with the same client secret) on the new endpoint.

The new authentication will also be a standard OAuth2 system, but will use JWT as a format for refresh tokens. So be aware that this will increase the size of the refresh tokens.

Additionally, the new endpoints implement refresh token rotation. A new refresh token is issued with every access token refresh response. The previous refresh token is invalidated.

[ekeih]

@elmi82 Thanks for sharing this! :+1:

[wmalgadey]

this is fixed in my fork now and uploaded to pyPi (python-tado 0.2.8)

[wmalgadey]

I made a mistake to 0.2.8 and hat to replace it with 0.2.9

[wmalgadey]

can be closed now, it is working!

[michaelarnauts]

@chrism0dwk is this repository still maintained, or should the fork from @wmalgadey be used?

Home Assistant uses the one from @wmalgadey, since this repo was inactive at the time.