Yep, I did that to the other version of the app and reused the client ID and client secret for this version.
I’d suggest there’s been a copy paste error then, I haven’t changed any code around the authentication process.
I’d recommend going into the Netatmo dev portal and copying the keys into a text only document (eg notepad on windows or textedit on Mac), then copying them into the app.
If falls, you might need to go into the “apps code” section on Hubitat, open the app and hit the oauth button. Then save and exit the apps code.
1 Like
Ok, I’ll give reentering my credentials a try. 
Pressing the ouath-button in app code and then save did’nt help.
Otherwise I’ll try create a new client id and a new client secret in Netatmo dev.
1 Like
Cheers. Sometimes copying directly from HTML pages causes issues - I always paste into a plain text file first to remove any rubbish.
1 Like
Thanks for the help! 
I’ll post the result here when I’ve tried..
1 Like
I’m assuming others are receiving this email as well, but looks like we’ll need to update the way the app authenticates:
Netatmo API Security Update
Dear Netatmo developer,
To improve the security of our products, we inform you that the Client Credentials grant type method will be completely removed. It will no longer be possible to authenticate with the username and password of the user.
The effective date of this update is October 2022.
How can you authenticate with Netatmo API ?
From this date, the OAuth2 authorization code flow must be followed for authentication.
You can find details on this method on our website:
Netatmo Connect Authentication
For tests, you can also get an Access Token from our developper portal.
Netatmo Developer Portal
- Log in
- Go on your account
- Select the application for your test
- Click on "Generate a Token"
You can now use this Access Token for 3 hours.
Sincerely,
Legrand - Netatmo - Bticino
I don’t believe so, I think it’s saying that user ID and password option will no longer be valid ways to access the API.
It will no longer be possible to authenticate with the username and password of the user.
This app already uses Oauth via an API key etc.
Ok. I just noticed some language about refresh tokens, which I don’t think the app uses. The Tesla Connect app that I use needed to be updated to periodically generate refresh tokens, so I was thinking that was the case here as well. If not, then great!
I hope that the case, I guess we’ll see. 
I’m not seeing a problem, only deleted posts.
Sorry! It was supposed to be an answer to one of the deleted posts. I got an email with the content of the deleted posts so thats why I answered.
1 Like
Sorry for any confusion. I realised I had just made a silly mistake myself and it was quickly corrected. In my case it was just I forgot to enable OAuth in the App editing screen itself, and thought I was gonna do it in the App at runtime
2 Likes
Hehe, been there, done that!
G'day all, I added a link to the first post to a brief guide to hooking up your Netatmo to Weather Underground.
2 Likes
I just want to thank you for posting this. You saved my life as my Netatmo app broke in smartthings, and Netatmo app in smartthings will go away in coming few weeks or months. Thank you for putting out in HE!!
2 Likes
No worries
I believe these are Netatmo Server side errors - I see them occasionally too.
I'll have a look at the code to see why the debug logging setting is being ignored.
I commented these out in def refreshToken() to remove from my logs. I think you need an if statement to respect the debug logging setting, for example if (debug) log.debug “In refreshToken”
1 Like
