Netatmo guest weather station's entities show up as not available anymore

[sibbl]

Next to my own Netatmo weather station, I've added my parent's Netatmo station as a guest station to my Netatmo account.

By adding the Netatmo integration to Home Assistant with my account, both stations were shown and updated properly.
Since around 2021-01-15 midnight (UTC) this is not longer the case and the device's entities show up as "not available".

• No errors show up in the HA logs, even after multiple restarts.
• This happened on two different HA instances (both mine and my parent's) which both ran on version 2021.1.0. The same issue happens with 2021.1.2.
• On both HA instances, I was logged in through my same Netatmo account.
• In terms of API credentials: I've created two different Netatmo apps in my Netatmo account to avoid per-app rate limiting.
• I'm using Cloud authentication on my device, while configuration.yaml authentication is used on the second instance. So this does not seem to make a difference, too.
• When removing and readding the integration, the guest station's devices are detected again. However, they're immediately shown as "not available".

To get Netatmo back running on my parent's HA instance, I've logged in there using their Netatmo account instead of mine. The primary station shows up properly again.

[eddiman]

I've been churning my head trying to figure why the hell nothing works, turns out Netatmo have had problems for some hours now: https://helpcenter.netatmo.com/en-us, system status says red and that services are down, even though the last update on my devices in-app was 08:23 CET.

Have also been reading on reddit of people reporting that last data read on station was around 2am CET, which translate to around 1am UTC, I guess its different for everyone.
Best is to wait until their server status says green and see what happens.

[enjikaka]

My netatmo data in home assistant is also missing. Shown as "unavailable" but I have recent data in Netatmo app. Hopefully this is due to that outage and will self-resolve soon :)

[sibbl]

It was indeed fixed on Netatmo's side.