Don’t be so sure… there are still people in their forum complaining very recently about the performance of their API…
did you perform any troubleshooting yourself so far?
I mean the maintenance yesterday cannot be the cause, because I habe the posted problem earlier!
I reboot yesterday evening my server after this reboot it worked again, but over the last night, the same problem. This morning no refreshing (updating) any more.
Now I creat a new API App at netatmo, and change the ClientID and Secret in Openhab. but this don’t solve the issue.
At the moment I cannot take a look into Openhab.log but I will post the log as soon as possible!
1 Like
by the way, the first report on their forum is from 3 days ago: SERIOUS ISSUE with /api/getstationsdata - Netatmo Forum. The maintenance yesterday was a reaction of NetAtmo to the problems.
It will help to see the logs. I can try to help even though I don’t use this binding
This issue I can confirm on Thuesday I had also no data in the app. May this both issues goes hand in hand! Approx. since this time my binging makes no refresh…
Nevertheless, I will post the log today evening
1 Like
Hello,
Same problem here.
Using openhab official docker image 2.4.0.M6-amd64-debian
Since ~ one week, the netatmo binding seems to stop functionning after a few hours.
- Items receive no more update
- see lots of "
2018-11-22 21:49:37.404 [ERROR] [nternal.handler.NetatmoBridgeHandler] - Unable to connect Netatmo API : 502 Bad Gateway" in the logs.
Just restarting the container give the exact same results
Deleting the container and re-creating it solve the problem (for a few hours)
Thanks for pointing to this information Angelo, yet I think tonight’s problem on Netatmo infrastructure is a coincidence and doesn’t account for all the problems discussed in this thread. Here’s a Grafana screenshot showing disconnection of the NEtamo. Each time, I had to recreate the openhab container to have it work again.
It could be a binding problem also… I didn’t exclude this possibility (but no-one is uploading logs… so no-one can really say what is going on).
I just added the info from the NetAtmo forum.
By the way: NetAtmo confirms only 2 incidents [1] [2] but their users have been reporting constantly API issues since early Tue 20/Nov (see here)
similar issues with other integrations since early Nov/18: Status code502 · Issue #10 · thexperiments/pimatic-netatmo · GitHub
and a comment by the developer of the binding: https://github.com/openhab/openhab2-addons/issues/2586#issuecomment-324680817
check also: https://github.com/openhab/openhab2-addons/pull/2682
Ok, you’re right, there is clearly a running problem on Netatmo’s side since a few days.
Then, it look like for some reason I cannot understand, our binding seems unable to reconnect to the API after is is repaired on netatmo’s side until we restart openhab.
this is an area of improvement that was addressed by the binding author sometime ago (he completely re-wrote the way he handles comms to the NetAtmo API) but it seems that maybe further improvements should be investigated (maybe to perform re-connect attempts after the API has timed-out) 
can you open up a github issue around this?
I have openend an issue on github.
1 Like
Yesterday evening, I didn’t had to restart the binding or openhab, the binding was able to reconnect ( openHAB 2.4.0 Build #1424 on a openhabian raspberry pi). Perhaps it is a docker-specific problem?
1 Like
Hi,
I’m facing the same problems:
- 404 Not Found
- 500 Internal Server Error
- 502 Bad Gateway
My items are not updated even the thing „Netatmo API“ is ONLINE - it’s annoying. For the moment it seems sufficient to just restart the Binding via bundle:start (not the whole OH process again and again), then it’s working again for a while… but not stable. I hope, this will not be the new default when they are sailing under Legrand flag…
Cheers,
Marianne
1 Like
Intranet of Things people 
too much cloud = stormy systems 
Your’e absolutely right! My Healthy Home Coach is the ONLY cloud basted hardware I bought – and now I know again why I hate this cloud approach so much!
1 Like
Lucky us for using “just” the weather and/or security products. Imagine you have the thermostat or relays for controlling your heating via Netatmo cloud. You would have been freezing for hours by now …
1 Like
That is the reason, why the thermostat of my Heaters are “cloudless”, connected local with my Fritzbox and controlled with openhab rules - also my Window sensors. 
Netatmo is less important for me, I use it in openhab only for the heater rules. all other features I use with native netatmo app
The binding doesn’t seem to request a refreshed token either.
From the last Week and till yesterday (Thursday), It is stop working again. Sinces Thursday is not refreshing any more
Crazy!