is it possible to change the default-interval for the Netatmo-Binding from 10 min. to 5 min.? In the readme I read that the default interval is defined by Netatmo API and therefore can’t be changed but the default interval is 5 minutes as can be seen here:
Yeah of course, but still you would have to wait 10 minutes and read the last two measurements since the next one would not be available already after 5 minutes.
(And you would have to update the corresponding item with a specific timestamp for the second last measurement and not the current time. I don’t know if this is possible.)
For the record:
I have monitored the my.netatmo dashboard now.
It didn’t update for 10 minutes and had 2 new values afterwards.
Has to be checked for the api separately of course, bit is a first indicator.
Well the usecase behind my question is that I have integrated a lawn mower which will be sent back to his station when it starts raining as we have some water patches around and I don’t want him to get stuck there. In our region it starts raining quickly and strong - so within 10 minutes the whole yard can be soaked. Of course, best would be a rain gauge which triggers an event immediately but as far as I understood, this is not possible with Netatmo.
But reducing the poll-time from 10 to 5 minutes would be better than nothing.
@Confectrician you mentioned to poll the api directly in a higher frequency. Is there any other chance to do this within Openhab without the binding? (Sorry for the question but I’m a bloody rookie)
Sorry for the late reply. I raised a ticket with Netatmo about which information is right. The answer from Netatmo was:
„The upload interval from the weather station to the cloud is currently 5 minutes. We will adjust the API-documentation accordingly.“
I also installed home-assistant to check out the netatmo module there (with 5 minutes interval). It works great. According to the developer, the module works like this:
On the first api call the module is looking at the server-timestamp which is included in every response. Using this timestamp, adding 5 minutes and 10 seconds and you will have the time when to poll the API next time.
Would it be possible to implement this in the Openhab Netatmo Binding too?
Oh that‘s the best idea to make it configurable! Maybe a note next to the parameter to inform users about the default value of Netatmo? In this case we would be able to adjust settings immediately if Netatmo is changing the setting again…
Long story short: The data available via the Netatmo API only changes every 10mins as of today, but the netatmo binding sometimes skips refreshes and when it does refresh, it effectively adds up to 9min delay because it queries the API at the wrong time intervals (shortly before the refresh happens).