API rate limit

[chriscatuk]

Lately it has become unreliable to use home assistant to control all my netatmo devices

Heating doesn't stop, windows don't close or open.

Always with this message saying we hit the api limit

Error: ("429 - - Maximum api usage reached (26) when accessing 'https://api.netatmo.com/api/setstate'",)

Would it be because the app used in home assistant is reaching its limit and we should each create our own app in the developer website?

[davidl77]

I have the same error daily…

[chriscatuk]

it gets in the way of using Home Assistant for all Netatmo IoT. My ensuite heating doesn't start when I push the associated button. doesn't stop after the scheduled x minutes. my 8 windows shutters won't open or close randomly when I leave the house and get back.

it became unusable.

[chriscatuk]

on this issue home-assistant/core#152449 someone shared a solution they worked on: https://tiimjcb.notion.site/HA-Netatmo-Integration-guide-to-apply-fix-2bcfa0ba79a5800a8355c4a42924933c

explaining:

🤔 What does this fix do?

This fix does multiple things :

• First of all, it uses a custom version of the Pyatmo library, which is the library the integration relies on to make the API calls.
  This custom version fixes a bug, and is on a [pull request](feat: enhance weather attribute normalization to support wind gust data across all API endpoints jabesq-org/pyatmo#546). This first PR needs to pass first to submit a PR on the Home Assistant repo.
• This fix uses the /homestatus endpoint instead of the /getstationdata endpoint. It provides more frequent updates.
• And finally, it reduces the “penalty factor” when a request failed. To make it short, on the original version, when a request failed, a 10x cooldown was applied to the next request. Meaning that you had to wait 10+ minutes, or even 30+ minutes in some case to make the next API call.
  We reduced that factor to 2x, meaning that, if you apply this fix with a dev account, you’ll wait only ~80s when a call fails.
  • That point hasn’t been verified yet by the code owner, so it might be removed on a future update.