API_RATE_LIMIT
Netatmo
Cloud API Rate Limiting
Third‑party integrations (Home Assistant, HomeKit, etc.) report API rate limit or too many requests; thermostat may appear offline in integrations while working in Netatmo app.
Advertisements
Possible Causes
Too frequent polling by third‑party system, Misconfigured automation loop, Multiple integrations querying the same account, Temporary Netatmo cloud protection
How to Fix / Troubleshooting
Note: This is a cloud/integration issue, not a hardware fault.
- Reduce polling frequency: In your third‑party system, increase the interval between API calls (e.g., poll every 5–10 minutes instead of every few seconds).
- Disable duplicate integrations: Ensure you do not have multiple instances of the same Netatmo integration running.
- Use official integrations: Prefer official Netatmo integrations where possible, as they respect rate limits.
- Wait for cooldown: Rate limits usually reset after a short period; avoid repeated manual refreshes during this time.
If rate limiting persists even with low polling, consult Netatmo developer documentation or support.
Advertisements
Repair Difficulty
Very Easy
1/5
Advertisements