Free tier policy questions | General | Forum

Avatar

Please consider registering
Guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed sp_TopicIcon
Free tier policy questions
No permission to create posts
April 10, 2019
2:32 pm
Avatar
finnbear

Silver
Members
Forum Posts: 5
Member Since:
April 8, 2019
sp_UserOfflineSmall Offline

What exactly does "No. Annual usage is capped." mean? (Taken from the pricing comparison pages)

Also, are graphs (built-in, not matlab) limited in terms of number of datapoints? I set the limit to 7 days but the graph only goes back about 2. (https://thingspeak.com/channels/752396)

April 10, 2019
5:12 pm
Avatar
Vinod

MathWorks
Members
Forum Posts: 306
Member Since:
May 1, 2016
sp_UserOfflineSmall Offline

I believe you are referring to the row "Scalable for larger projects." which shows "No. Annual usage is capped" for the free tier.

This is intended to convey that if you plan to have a number of devices sending data frequently, you will likely want to buy a license. This ensures that your devices don't get their data rejected when the account has reached the annual limit of 3 million messages/year for the free tier of service.

April 10, 2019
9:54 pm
Avatar
finnbear

Silver
Members
Forum Posts: 5
Member Since:
April 8, 2019
sp_UserOfflineSmall Offline

Oh, so "capped" means capped based on the account. Thus, when you pay, its only capped per device?

More importantly, based on my math, I can have one device/channel that updates every 15 seconds and run that on the free tier for the whole year? Correct?

April 11, 2019
6:07 pm
Avatar
cstapels
Moderator
Members


Moderators
Forum Posts: 730
Member Since:
March 7, 2017
sp_UserOfflineSmall Offline

The graphs are limited to 8000 points, or possibly less with averaging on. Be careful not to set the number of points and the number of days simultaneously, points will win. There doesn't seem to be any data in your channel older than April 10, so you wont be able to go back further than that. Also be careful if you update different fields asynchronously, there will be extral null values added to the non updated fields.

You can have one device per account that updates every 15 seconds - that would consume ~2M messages per year. If you added a second device, you would have to slow things down a little to stay under 3M messages. The number of channels you use does not change the number of messages allowed. (3M)

April 12, 2019
12:30 pm
Avatar
finnbear

Silver
Members
Forum Posts: 5
Member Since:
April 8, 2019
sp_UserOfflineSmall Offline

I wish the graphs were limited to 10080 points or higher. That way, a sensor could log every minute (my new interval) for an entire week, on one graph. Anyway, thanks for the insight into why my graph wasn't working perfectly.

April 12, 2019
3:44 pm
Avatar
cstapels
Moderator
Members


Moderators
Forum Posts: 730
Member Since:
March 7, 2017
sp_UserOfflineSmall Offline

We definitely appreciate the feedback - we will record it in our suggestion tracking log.

To get long time periods of averaged data, you might consider using a derived channel. Set up a time control that reads your channel every hour and saved the two minute average to the derived channel. Then you can see the two minute averages (or what ever value you want that is greater than 76 seconds) for the whole week on a plot, while maintaining the raw data.

Forum Timezone: America/New_York

Most Users Ever Online: 166

Currently Online:
25 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

rw950431: 272

Vinod: 240

piajola: 95

turgo: 70

vespapierre: 63

Adarsh_Murthy: 62

Member Stats:

Guest Posters: 1

Members: 8665

Moderators: 1

Admins: 2

Forum Stats:

Groups: 3

Forums: 14

Topics: 1600

Posts: 5760

Newest Members:

ssh47k, aaceitunog01, AlinaCutle, MARTO, simplicity1, jango6954

Moderators: cstapels: 460

Administrators: Hans: 405, lee: 457