Ok, I've added a re-auth option and published v1.5 - I think it works, but if you could test it out, it would be appreciated.
v1.5 - Added a manual reauthorize option
1 Like
I think it doesn't take you back to the app correctly. When I click it, it works as expected and finds my account and then when you click ok it takes you to.
https://cloud.hubitat.com/api/"my hub ID"/apps/8941/oauth/callback?"other tokens"
Is that correct? Or should it take back to the local IP?
This is the page for above
It doesn’t take you back to Hubitat when you first authenticate either. If you manually go back to the Hubitat app page, and then go into the Netatmo Connect app, it should work when you select next to view your devices and change the unit types.
That’s one thing I was never able to fix.
1 Like
This has quit working for me in that it no longer shows any of my devices. If I check the application state, everything looks fine in that deviceDetails, deviceState, and response fields are all populated with apparently valid data. However, nothing appears in the list of devices in the app itself. Thoughts?
Are you running the latest release? It has a re-auth option.
I've recently required a Netatmo station and mine is working fine.
1 Like
Sorry, I did leave out a few details. Yes, I'm using the latest version. I've reauthorized multiple times. I've uninstalled and reinstalled the app itself. I've even created a new app on the Netatmo side with a new client ID/secret. Nothing was showing.
Emphasis on ”was.” I just went back to get a screenshot and suddenly everything is showing up. I did nothing different whatsoever, and I jumped through a bunch of hoops repeatedly before posting. Just one of those things, I guess. Sorry for the false(?) alarm. 
Hmmm, I wonder if Netamo had some sort of outage that caused your issue?
An outage is possible. I monitor my Netatmo's for a temp change. If there hasn't been a change in 3 or 4 hours, I restart the unit. It restarted yesterday and alerted me about it
There's a better option - monitor the "last update" field on the main unit:
My rule is on Github if you want to use it - if the Netamo goes offline, it power cycles it via a smart outlet (ignore the name, I need to change it).
1 Like
I've had this running smoothly for a few years until a few days ago when my Netamo devices stopped updating (Saturday at 7:55P CT).
When I go into the App and hit "Connect to netatmo" to "reauthorize", I am taken to the correct "dev.netatmo.com" page. However, when I click "Yes, I accept" I'm taken to a 'cloud.hubitat.com' page which appears to be linked to my hub and my Netatmo app, but I get a 400 error.
Has anyone encountered this or have a workaround?
I've tried reinstalling the app, and initially get to a successful connection page on 'cloud.hubitat.com' but then the Netatmo devices are not created. When I go back into the app and click "Connect to netatmo" I go into the same loop described above resulting in a 400 error at cloud.hubitat.com.
App installed:
Netatmo connect page, where I hit "Yes, I accept"
cloud.hubitat.com page which loads after "Yes, I accept" from the prior "Netatmo" page, resulting in a 400 error.
Hopefully one of y'all have some ideas I can try. Thanks!
EDIT: updating to note that I have upgraded my C8 to build 2.3.9.197 (this was also happening on 2.3.9.196) and have rebooted the hub
I'm experiencing the same thing - reauth flow, 400 from cloud.hubitat.com on the oauth callback. Seeing some cloudfront headers..... Wondering if something changed on the hubitat infrastructure end?
1 Like
@gopher.ny @mike.maxwell ^ hi folks, sorry to bother you. Are you aware of any changes on the Hubitat infrastructure side that would be causing the 400 errors we're seeing on cloud.hubitat.com for oauth callbacks?
My post above with screenshots earlier today outlines what we're seeing. Thanks!
Just go to the apps page manually, and it should be fine after that. The re-auth always does this.
1 Like
The only way I could solve was to delete the Netatmo app from my hub, create a new set of API keys and app at dev.netatmo.com and basically start over from scratch. That was painful due to 5 netatmo devices across dozens of rules and dashboards. The netatmo devices weren't available in the Swaps App Devices in settings to make the process any easier.
Hopefully whatever killed my authentication/connection doesn't happen again. 
... which apps page? The hubitat one? The netatmo one? A third, unspecified and mysterious, one?
I've tried the first two and no joy. Really not into the idea of re-creating the full oauth app/flow as craigspree suggested.
Yes. Just go into the the app, click the re-Auth button, complete the process, and when you get a page with an error, just manually navigate back to your hub’s app page.
Nope, doesn't seem to work for me - still don't see any devices when I click past the re-auth page after doing the re-auth flow like you suggest
The only thing I can suggest is making new credentials.
My exact process for fixing:
- I did all of this in Chrome due to familiarity with clearing the page cache which was required in these steps.
- Make note of all of current devices and rules as all Netatmo devices will be deleted from hubitat (and recreated with new IDs) in this process
- Delete the Netatmo app on the hubitat apps page, which will also delete all the child devices on the hubitat
- Go to your hubitat devices page to visually confirm all Netatmo devices are deleted
- Go back to the hubitat apps page and add a user created app - select Netatmo
- On your hubitat, open the new Netatmo app you just installed - there will be two blank text fields for your api keys from Netatmo.
- In a new browser tab, go to dev.netatmo.com and create a new app, which will generate a new set of api keys
- Copy the appropriate keys from dev.Netatmo.com into the app you just installed on your hubitat - do not hit next yet.
- In your other browser tab at dev.netatmo.com, open the old app and disable the old app (there’s a toggle near the bottom left of the page)
- Go back to your hubitat tab and click on authorize/next
- You’ll be automatically sent back to dev.netatmo.com with a confirmation to enable hubitat to communicate with Netamo. Confirm this connection. There will then be a message that you can close that page, don’t close that page/tab yet.
- Open a 3rd browser tab. Navigate to the hubitat page and your Netatmo app on your hub. Click ‘next’. If you don’t see all of your devices in the drop down then right-click anywhere in the white part of the page and select ‘inspect’ then right-click the reload button in the browser address bar and select ‘empty cache and hard reload’. Now your devices should display in the drop down.
- Select all your devices. Set all your measurements and hit done.
- All your devices should be back and you can now recreate all your rules.
- For my rule 5.0 and above, I could easily fix the broken rules by editing them. For my rule 4.0 or lower rules, I couldn’t edit them and had to recreate them as rule 5.1 rules.
Good luck!
1 Like
Me too. Is the call to cloud.hubitat.com coming from Netatmo or the this Netatmo (Connect) app?
