Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Netatmo : no more stats after a power supply shutdown #2078

Open
ngeissel opened this issue May 14, 2024 · 2 comments
Open

Netatmo : no more stats after a power supply shutdown #2078

ngeissel opened this issue May 14, 2024 · 2 comments

Comments

@ngeissel
Copy link
Contributor

First, are you sure that you found a Gladys bug?

=> NOT AT ALL (i did not take time to reproduce it, but still : after reboot it is a fact : it is down)

Describe the bug
After a thunderstorm, power supply shut down => it should have reboot the gladys and the netatmo station => no more stat => have to go to "integration=>netatmo=>reset login / password configuration ...)

To Reproduce
Steps to reproduce the behavior:

  1. Simulate a thunderstorm by Power down gladysassistant server or Netatmo
  2. Go to Netatmo device stats
  3. See the lack of info (until you reset your access ...)

Expected behavior
A reboot of all the stuff should be crystal clear for the user with no human action ...

Screenshots
Too bad I re set my access ... and now all is working

Your Gladys installation (please complete the following information):

  • Raspberry Pi 3 installation
  • Manual installation: docker-compose

Desktop (please complete the following information):

  • OS: raspbian 11
  • Browser : chrome
  • Version XXX

Additional context
N/A

@Pierre-Gilles
Copy link
Contributor

@Terdious I don't know if you saw this one :)

@Terdious
Copy link
Contributor

Hi @ngeissel
I read your message (thanks @Pierre-Gilles ), I hope it doesn't have a significant impact on your use for the moment.

I started looking, I already had a similar problem (well, not really the same one). I haven't found it yet but I guess it's related to the refresh token. I am continuing the investigation. And above all I try to reproduce (because I did not succeed intentionally).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants