Hello @raman325 , thanks for your climacell integration contribution - this is really great, and I was so happy to have a new solution to replace dark sky. I noted that the rate limit was set to 100 lately. According to tomorrow.io, the free rate limit is 500 and I still have 1000 as you have. It seems, that multiple situations need to be covered. My requests/idea:
Rate limit adjustable in configuration flow or at least in the configuration files
To support different rate limit plans, this would be great. I would like to be able to set this permanently in my docker environment, stored in the /config folder.
Frequency only allows updates every 5/10/15/30 minutes (or similar) - I would like to allow lower update rates due to item 1
Sample case: I do have 3 locations, I am supervising with climacell. 2 of them are of low importance and I just need an update every 3 hours.
Can you add also 1h, 2h,3h, 6h, 12h, 24h (or similar) to the config flow?
Frequency updates to be different during time of the day
To optimize the free API call usage, I would like to specify a generic update frequency per day. But for specific time windows, I would like to have an increased or slowed down rate (depending on implementation).
E.g. I am interested in latest updates in the morning, before leaving the house. During the rest of the day, I am fine with hourly updates. During night I might even want to reduce the update rate to every 3 hours or none at all.
The r-renato custom component (https://github.com/r-renato/ha-climacell-weather) allowed “exclude” intervals. This would also be sufficient for my case.
Item 3 would actually combine item 1 and 2. I consider it the most complex one (specifically with UI in the config flow - if UI is required, probably this is something we can also define without UI to make it simpler?).
For now, I changed the const.py in my climacell integration, but this is unfortunately not permanent throughout updates in docker…