Currently, get_historical collects some number of weeks of data relative to "today". There could be special events which would motivate collecting data from specific sensors on/around specific dates. The following would support this use case:
Channel.get_historical should support either a relative time frame, or a custom start and end period.
The behavior on the custom periods should mimic any behaviors needed to respect API limits on thingspeak. One approach might be to partition the date range into week long chunks.
Thank you for all your work on this wrapper, it has saved a lot of time.
Motivation
Currently,
get_historical
collects some number of weeks of data relative to "today". There could be special events which would motivate collecting data from specific sensors on/around specific dates. The following would support this use case:Channel.get_historical
should support either a relative time frame, or a custom start and end period.Thank you for all your work on this wrapper, it has saved a lot of time.