Client Id for New Authentication Process
In your https://support.tado.com/en/articles/8565472-how-do-i-authenticate-to-access-the-rest-api it mentions a Client Id code. Is this a a fixed code or does it change per user / system? If the latter then how does one find it?
Best Answer
-
It's a fixed code, so just do a post of the following url:
https://login.tado.com/oauth2/device_authorize?client_id=1bb50063-6b0c-4d11-bd99-387f4a91cc46&scope=offline_access
1
Answers
-
Have you had a look at this thread? https://community.tado.com/en-gb/discussion/comment/93785#Comment_93785?utm_source=community-search&utm_medium=organic-search&utm_term=api0
-
-
I have tried to follow this process, using javascript in Node-Red, without success. I obtain an error 404, and invalid client_id as the reason ("error_reason": "invalid_client_id"). Even with the "fixed" client_id=1bb50063-6b0c-4d11-bd99-387f4a91cc46 or my personal Tado client_id.
Any new ideas or suggestions? Any help will be appreciated.
0 -
Try adding quotes on the name client id and it's value0
-
I'm lost.
Only for experts?
Can't we inexperienced old folks do anything?
Where should I post it? I posted it in the address bar and the result was:
This page doesn't work.
If the problem persists, contact the website owner.
HTTP ERROR 4050 -
Sticking it in the post won’t work either.
This is an HTTP POST method0 -
Thank you AndrewFG.
I tried with quotes, escaped quotes and some other variations. If someone have a successful code (javascript), please share the code. I discover that today the "old" method to access Tado API data doesn't work anymore. So I'm trying to update the Node Red, javascript based, module to extract dato from Tado API.
0 -
Thank you so much, "Montaje," for your advice, but after three and a half hours of tinkering, I haven't achieved anything, and at seventy years old, it seems too late to go back to university.
From what I can see, many of us are having trouble controlling Tado from our home automation app (in my case, Home Assistant). I think Tado has set the bar very high for many of us with this new process.0 -
Developers may be interested in my OpenHAB Device Code Grant Flow code for tado integration in the following two Pull Requests:
https://github.com/openhab/openhab-addons/pull/18354
https://github.com/openhab/openhab-core/pull/46320 -
Thanks, "Montaje":
I was able to publish it with Postman. It returned the following sections:
{"device_code":"XXXX"
"expires_in":300
"interval":5
"user_code":"XXXXX"
"verification_uri":https://login.tado.com/..........
"verification_uri_complete":"https://login.tado.com.......................I assume I can now log in from Home Assistant (which asks for a username and password) using some of these details.
Would you mind telling me which ones?
Do I have to use another method to log in?
"Montaje," I thank you again for taking the time and apologize for the inconvenience.
Regards, Kepa0 -
Home Assistant is just awaiting a fix, to match the new authentication method. The code has passed testing and is making its way through the path to production. Hopefully the release will be soon.
Meanwhile, you can head to verification_uri_complete":"https://login.tado.com....................... and complete the next step. Logging in there will allow you to proceed.
0 -
Thanks again.
I don't even know what I did, but I had to run the request again, and after some fiddling, I got a user code. After typing the full URI description in the taskbar and doing I don't remember what, I got a message that says:tado
(green "tick" symbol)
Device connected successfully.Now, do I need to save that user code? Or any of the data received?
Thanks so much for your help: Kepa 🙂0 -
> do I need to save that user code?
Not really. The transaction will have given you two things -- namely an Access Token and a Refresh Token. The former is what you offer in the HTTP Authentication: Bearer header for the immediate API calls. However the Access Token is valid only for probably 60 minutes. After it expires you need to do an OAUTH token refresh using the Refresh Token and offering the about to expire Access Token, and this will give you a new Access Token valid for 60 minutes etc. Rinse and repeat..0
