invalid access token
I try to create an app that can at least read the weather data from my netatmo. I managed to create the login flow and I get back an access_token and a refresh_token.
However each endpoint I call returns a 403 / invalid access token, even if i provide the newest token.
Even refreshing tokens gives me the same error, what can I do?
Comments
7 comments
I tried with a token I generated through the website to no avail. Then I created a new application, created a token and it seems to work. Solved my problem for now but I am a bit worried about the stability of Netatmo auth.
BTW, is there a way to delete an obsolete application?
Same problem; same question
Hello,
Seems like some applications are buggy recently. They correctly generate the first access/refresh_token pair, but these values are invalid
As you said, the solution is to create a new developer application. I'll report the problem to Netatmo devs
You can't totally delete an unused app from your interface. I advise you to deactivate it with the slider in the app's details
Have a good day,
Leslie - Community Manager
Hello,
I'm bumping this thread because I still seem to have the exact same problem. All of the authentification process works fine but the newly generated token doesn't work and the API returns the invalid access token error.
Edit: removing some scopes fixed my issue but I can't add too many different scopes
Hi Marc,
Thanks for the feedback. Could you please send me the exact scope list you tried ? I'll see on my side if I can reproduce the problem
Have a good day,
Leslie - Community Manager
I am having this exact problem, the only scope I am using is read_station. It was returning invalid access token for me but for other users the app was working fine, resetting the client ID and secret did not work but creating a new application did.
Hi there,
I have a similar problem, I do get a credential token, when I use my Access_Token / Refresh_Token created, but get a 403/Forbidden when requesting GetStationData() or GetHomesData().
If I then create a new Token for the App with read_station and read_homecoach scopes, I then receive new Access and Refresh tokens, which will work for a while (appx. 2-4 hours) then we are back to the 403 / forbidden again.
I can see the expiration time of the credential token is appx. 20 seconds, is that correct?
/NielsK
Please sign in to leave a comment.