That might be an inconsistency. I’ll have to investigate.
I’ve problem with 0.105 and Netamo…
Since the update, my old configuration for the thermostat fail…
Then I try with integration/netamo and the acceptation page open, I accept but then nothing change a all?
No new popup in this webpage nor in the HA.
Anyone could help?
Other way than integration / netatmo?
My old configuration was:
netatmo:
api_key: !secret api_net
secret_key: !secret secret_net
username: !secret user_net
password: !secret pass_net
But that config give me:
Invalid config for [netatmo]: [api_key] is an invalid option for [netatmo]. Check: netatmo->netatmo->api_key. (See /config/configuration.yaml, line 22)
You have to update your config. Rename api_key and secret_key and remove user and password. After that you simply run the config flow with configuration.yaml option and everything should be fine.
I’ve change my config:
netatmo:
client_id: !secret user_net
client_secret: !secret pass_net
But now when I try to add integration the external website give that:
Missing code or state parameter in http://192.168.1.53:8123/auth/external/callback?error=invalid_client&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmbG93X2lkIjoiMGNjNTI5NmQ2ZDBmNDBjZGE4NWU5YWI1NTNkY2MzZjUifQ.HpcWbYYpDbOOG3qctJQb6fY5sIHWvAKw5sBqrmJf6VA
You have to edit the base_url option in configuration.yaml to the external URL of your HA instance. In my case I set this:
http:
base_url: https://hass.xxxxxxxxx.duckdns.org/
You may also have to specify the port number (default 8123) if you’re not using a reverse proxy like in my case. The it would look similar to this:
http:
base_url: https://xxxxxxx.duckdns.org:8123
I hope you get it up again!
Best
Magnus
1 Like
I’ve not yet ssl configurated on my HA…
I don’t know yet how to configure it with my OVH domain 
You don’t have any access from the outside world?
Of course but via VPN
I am no expert on this particular matter, but I suspect that external access is required to verify the authentication… :-/
External access is not required.
I just verified this on my dev instance, which has neither ssl nor external access. If after you accepted the account link at the netatmo page and get an empty page just go to your HA tab and it should be authenticated.
2 Likes
I don’t see anymore the netatmo page but only this code:
Missing code or state parameter in http://192.168.1.53:8123/auth/external/callback?error=invalid_client&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmbG93X2lkIjoiMGNjNTI5NmQ2ZDBmNDBjZGE4NWU5YWI1NTNkY2MzZjUifQ.HpcWbYYpDbOOG3qctJQb6fY5sIHWvAKw5sBqrmJf6VA
In that case, the fix I proposed should get you across the finish line! 
Problem solved!
Value for
client_id: must be API from netatmo and not username
and
client_secret: must be code delivered by netatmo and not the password from the app
Thx for your help!!!
This is exactly what I did - got blank page and then returned to HA and all was goo din the hood.
1 Like
Upgraded and now it’s not working, I renamed client_id and client_secret but still nothing
This caused my some serious issues, of course it’s not directly related, but as I mentioned above I want to restore to my backup.
So I flashed my sd card with the latest hassio image (done this process before several times and usually it works fine), installed samba to get my backup on the pi and restored (wipe & restore). I waited for over an hour but my ha doesn’t show up again.
SSH connection refused. It’s online because I can ping it but nothing else. Tried that twice.
I noticed that my database is pretty big (4GB). I’m running a pi4. Do I have to give it even more time? Any suggestions. I might have to open another topic for that. Maybe you can split that here @cgtobi ? Topic name could be: HA 0.105 restoring to 0.104.3 fails.
EDIT: Just now I tried ssh again and it is online again, I might give it more time. I will definitely switch to a nuc soon.
Ok, i got mine sorted, here’s how in case anyone is stuck. I commented out my entry in my configuration.yaml, restarted HA, added the integration and selected using configuration.yaml and it suceeded. then uncommented my configuration.yaml which worked on a restart
Have you removed the username and password from the configuration and have you tried to add it in integrations in the GUI?