Hello,
since a few days the API for the weather station has changed.
At first glance, I only get the data from my station every 30 minutes. In the last few years, I received new data every 10 minutes. The 30 minutes are really stupid if I want to ventilate from/up to a certain CO2 value, for example. In the Netatmo app, the data continues to arrive every 10 minutes.
I have the same problem too. In an efficient environment, the Server must be sized to support one request every minute from an APP. Other wether station allows to query easily (without 2Auth factor) directly the own Base Station to avoid to clog the Cloud.
If Netatmo does not change policy, I am thinking to change solution at the root.
0
Tawi
I have reduced the polling cycle from every minute (60x/h) to every 2 minutes (30x/h). Actually, there weren't many queries - measured against the limit, but since then it has been working again.
Comments
4 comments
I have the same problem too.
In an efficient environment, the Server must be sized to support one request every minute from an APP.
Other wether station allows to query easily (without 2Auth factor) directly the own Base Station to avoid to clog the Cloud.
If Netatmo does not change policy, I am thinking to change solution at the root.
I have reduced the polling cycle from every minute (60x/h) to every 2 minutes (30x/h). Actually, there weren't many queries - measured against the limit, but since then it has been working again.
https://dev.netatmo.com/guideline
200 requests every 10 seconds
2000 requests every hour
Does the token also count as a request or is it only about the actual data retrieval?
How many requests do you have now?
For me its constantely telling me I am above my usage limits after 3 hours... and I am way below the limits in the guideline
Can I see the number somewhere in the dev portal? I currently do not save any information other than the data and tokens when retrieving.
Please sign in to leave a comment.