Netatmo integration stopped working.
Re-integration does not work, get a DNS error when calling api.netatmo.com.
Can anyone confirm?
Yes, most likely due to an Azure outage that affects many other services, such as NS, Officce365,… According to an outage site, also AWS had problems, both from a couple of hours ago. Reported problems graphs:
The App is not working as well for quite a while now…
Would really love Netatmo local API, their service is too unreliable.
Any ideas where to start? First thought would be a proxy to get the update traffic
Netatmo will post any (acknowledged) outages here if you ever need to check…
https://helpcenter.netatmo.com/hc/en-us/sections/10390237686930-Service-notifications
this time as Edwin states above this is a wider than just a Netatmo issue…that said Netatmo has been back online for me a few hours at this stage
Recent catch-cry: It’s always DNS!!!
Stepping back and lookimg at the greater picture.
Sadly, a graceful fallback would be nice, developers always assuming that all the stars align, ALWAYS, for their code to work. Robust error correction and allowing for unusual conditions is the mark of a mature product.
Just wondering why DNS needs fo be updated so often, and checked and validated? How often does a domain IP address change in the real world once it is allocated? Is fetching from cache when it is down a valid option, with appropriate warning status codes? Could we save on lots of DNS traffic if the underlying assumptions were redesigned?
Maybe we’re all doing this the wrong way?
The internetz is broken.
/rant mode off