May 3, 2011
April 11, 2011
I'm also using ThingSpeak to track home control data and I have not had this problem. Some of my channels have many thousands of points and I can display multiple days. Since I can only retrieve 8,000 points at a time, I am limited to the number of days I can display at one time depending on the data rate but that has not been a problem. You can always use the start= and end= API calls to display a different range.
Here's a chart with two fields from one of my channels displaying the last 5 days:
March 14, 2011
If you log less data, it's easier to display charts on a longer time frame. If you log every 15 seconds, you reach 8000 data points in 1.4 days, but if you log every hour you can return over 300 days worth of data.
We have to put the rate limits in place, otherwise getting a month's worth of data from 15 second intervals is extremely intensive on our systems. For example, this would require a database call for 175,000 points, and then the web server might still have to slice that data into time slices and calculate averages for each of these time slices.
June 6, 2011
"timescale" is a data operation, like average or median. So, a timescale of 10 sets the channel output to even increments of 10 minute slices even if you have a 100 data points in a 10 minute windows, only 1 will be presented.
To get an extended range, use results=200 or specify days=3.
Does this make sense?
Most Users Ever Online: 166
Currently Browsing this Page:
Guest Posters: 1
Newest Members:Advantagetreeexperts, laundrydaddyuk, techhhelp5, ken, tran, huldacormier
Moderators: cstapels: 460
Administrators: Hans: 405, lee: 457