david

1. Community
2. [EN] API, automation and external services
3. Netatmo token refresh fails

The error message in the OP shows that the 500 response is coming from account-link.nabucasa.com, not netatmo.com. I would investigate the nabucasa.com server for the problem.

• Kommentar anzeigen
• 14. Juni 2024 18:42
• 0 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

OK, we owe Netatmo an apology, but in our defense, this was not easy to find. Without going into too much detail, the problem was that Microsoft seems to have removed some obsolete roles on Azure t...

• Kommentar anzeigen
• 6. Juni 2024 20:38
• 2 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

I've just spent several hours debugging this, and I have new data. Fundamentally, the invalid_grant response seems to occur when the token has expired. If I navigate to the app setup page (https://...

• Kommentar anzeigen
• 6. Juni 2024 03:03
• 0 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

I always interpreted the docs to mean that the API will tell you that the token has expired, and then you go and get a new one. The API behaved that way until this week, so we had no reason to thin...

• Kommentar anzeigen
• 5. Juni 2024 20:30
• 0 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

@alexander: That's because until Monday the documentation said to handle token expiration by refreshing the token. The code posted above worked without interruption for half a year until noon CEST ...

• Kommentar anzeigen
• 5. Juni 2024 20:08
• 1 Stimme

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

@Leslie: dommage, mais non. After removing the auth header from the refresh call, the grant still expired promptly at 3 hours, 20 minutes after the last refresh. Is there any reason not to refresh ...

• Kommentar anzeigen
• 5. Juni 2024 13:54
• 0 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

Removing the authorization header from the renewal method per @alexander didn't change the behavior. We're going to try refreshing the token before it expires going forward.

• Kommentar anzeigen
• 5. Juni 2024 13:07
• 0 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

So, is the fix to pre-emptively refresh the grant after n seconds? The documentation seems clear that you should only refresh expired tokens.

• Kommentar anzeigen
• 4. Juni 2024 19:53
• 0 Stimmen

1. Community
2. [EN] API, automation and external services
3. API invalid grant at random intervals

The wrench in that machine is that we're receiving invalid_grant, not access_denied or anything indicating the token itself is the problem. Also, when refreshing the token manually, I have been ask...

• Kommentar anzeigen
• 4. Juni 2024 19:34
• 0 Stimmen