Sorry, I can really decipher your question here?
The driver allows for two polling frequencies. One for 'daytime' (sunrise to sunset) and one for 'nighttime' (sunset to sunrise). Many users wanted more frequency during the day as they use the driver's LUX (illuminance) attribute, but don't need/want that frequency when it is dark out. The driver uses OWM's OneCall API for all of it's data and that API allows for 1,000 polls per day for free. So if there were 16 hours of daylight (summer) and 8 hours of nighttime, you could poll as frequently as every two minutes during the day and every five minutes at night and remain under the limit ( 30 Polls/hour * 16 hours) + (12 polls/hour * 8 hours) = 576 polls per day. You would remain well under the 1,000 per day limitation on their API. You should also verify that your location actually updates the underlying data at that frequency. Just because you can poll the API that often does mean the data has changed. If your location's underlying data that the API feeds is only updated every 15 minutes it does not help to poll more often than that.
In general API polls take hub resources and creates a larger database. You should consider your requirement for fresh data frequency and balance that with the hub resources required to provide that frequency.
Hope that helps.
