Netatmo Cloud becomes unavailable

[Fatalmose]

The problem

This will be the third time I'f installed Netatmo. It works fine for several days before becoming unavailable.

What version of Home Assistant Core has the issue?

2024.9.1

What was the last working version of Home Assistant Core?

2024.9.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Netatmo

Link to integration documentation on our website

No response

Diagnostics information

Not available.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Échec de la configuration, nouvel essai: 500, message='Internal Server Error', url='https://account-link.nabucasa.com/refresh_token/netatmo'

Additional information

No response

[gvigroux]

Same for me

[Fatalmose]

Hello.

Have the impression that HA loses the Netatmo access token when updating to newer Core or Operating System. When having a HA problem where you decide to reinstall a saved previous HA version it also loses the Netatmo access token. I’f noticed that because every time you delete and reinstall the Netatmo integration it works again.

Regards.

JS.

Le mar. 10 sept. 2024 à 18:30, gvigroux @.***> a écrit :

Same for me

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/125615#issuecomment-2341432251, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FSZW3SWI7JZSL4GCSDZV4NCHAVCNFSM6AAAAABN464PWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGQZTEMRVGE . You are receiving this because you authored the thread.Message ID: @.***>

[home-assistant[bot]]

Hey there @cgtobi, mind taking a look at this issue as it has been labeled with an integration (netatmo) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of netatmo can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign netatmo Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

netatmo documentation netatmo source _{^{(message by IssueLinks)}}

[AnthonyBe]

Log details in English for broader searchability.

Logger: homeassistant.components.netatmo
Source: components/netatmo/__init__.py:90
integration: Netatmo (documentation, issues)
First occurred: 12:26:46 (123 occurrences)
Last logged: 15:05:05

API error: 500 (Internal Server Error)

2024-09-11 15:03:43.326 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error)

[Just2Confuse]

Same problem. "Einrichtung fehlgeschlagen, wird erneut versucht: 500, message='Internal Server Error', url='https://account-link.nabucasa.com/refresh_token/netatmo'"

[CorentinMic]

Same problem here

[sven-debug]

Dear @cgtobi ,

is there something we can provide to help you solving this issue? Any additional logs, protocols...

BR Sven

[Sohnkarlsruhes]

if I delete the integration and setup again, it works for a few weeks. same problem every few weeks

[HansWegman]

Same here

[Just2Confuse]

if I delete the integration and setup again, it works for a few weeks. same problem every few weeks

Thats it. Delete it, and set it up again. You will not lost any data

[mfiordi]

deleting and re-setting up works but you lose the relationships of the devices (for example the room they are in, within Hassio)

[janchlebek]

It does not seem to be related to core update, happened to me while still on 2024.8

[WueBumbum]

I have the same issue since today

[AnthonyBe]

It does not seem to be related to core update, happened to me while still on 2024.8

That's interesting. I never encountered the issue until I updated from 2024.8.3 to 2024.9.1

[Ralphy140]

Yep same problem, Never had it drop out before updating to 2024.9 and then it stopped working so will try removing and re-adding

[Ralphy140]

As a word or warning, When i re-added I lost all my sensor history, Not a huge issue but i had ~4 years of hystoical data thats now lost in Home assistant, I still have it in the netatmo platform so more annoying than anything else

[janchlebek]

As a word or warning, When i re-added I lost all my sensor history, Not a huge issue but i had ~4 years of hystoical data thats now lost in Home assistant, I still have it in the netatmo platform so more annoying than anything else

Sometimes the entity_id changes when you remove and add the integration. You need to make sure your entity names are the same as before (update them to old values after re-adding the integration). Then all history will stay.

[WueBumbum]

Sometimes the entity_id changes when you remove and add the integration. You need to make sure your entity names are the same as before (update them to old values after re-adding the integration). Then all history will stay.

You are right, that is great.

[Haifi58]

Same for me - can do an integration with Netatmo, but can't see all my home netatmo sensors . . . tried to restore a backup, but no improvement . . .

[janchlebek]

Same for me - can do an integration with Netatmo, but can't see all my home netatmo sensors . . . tried to restore a backup, but no improvement . . .

After you add the integration it might take a minute for all the devices and entities to appear.

[Haifi58]

Same for me - can do an integration with Netatmo, but can't see all my home netatmo sensors . . . tried to restore a backup, but no improvement . . .

After you add the integration it might take a minute for all the devices and entities to appear.

Agreed, thats how IT worked the last 12 month, but no success since two days, see only kind of public Sensors with no values behind

[Foguet]

It does not seem to be related to core update, happened to me while still on 2024.8

That's interesting. I never encountered the issue until I updated from 2024.8.3 to 2024.9.1

The same thing happens to me since yesterday and I am still on version 2024.7.4; Supervisor 2024.09.1; Frontend 20240710.0;

[2Joda2]

is there a solution without re-adding ?

[janchlebek]

is there a solution without re-adding ?

I'm afraid not at the moment - the developer of the integration or someone capable would need to implement it.

But there is nothing to worry about, just remove and add again, adjust entities in case they were customized.

[SupercowsNL]

Same issues here.

[luissimoes]

Same issues - annoying when this is used to trigger decisions…

[flashouillette]

same issue

[doctorlunch]

Heating back on ready for winter...same issue

[nickgr6]

I have the same error. HA Version 2024.8.2

[spanzetta]

Same issue here.. for the 1st time after long time .. without updating anything (I am still using Core 2024.6.4 and OS 12.2) Just started to give this error now without any apparent reason