My apologies for the delay in my updates. While we continue checking your case, I’ve proceeded to change the data span for all your widgets to minutes, so that, from midnight UTC, you can see a few of your data instead of none whatsoever.
Best,
–Sergio.
Thanks. That will help.
I don’t understand how your system works but it seems that the dots out - both normal and synthetic - are carried over from the previous day and not reset to zero at 0000Z. Is it possible to manually clear those values? If they are generated new everyday that would not help.
Larry
Sergio,
I am guessing that you are thinking that something in one of my widgets is causing a huge dots download when I try to access the data after 0000Z when the counters have been reset to zero…
I can easily rebuild the widgets. I am going to take your change even further. I am going to delete all of my widgets and see what happens at 0000Z when the dots in and out counters are reset.
If that works, I will rebuild the widgets one at a time to see what was the problem.
Larry
Sergio,
I think I have the problem which is simple arithmetic.
Suppose you are capturing data the generates 2,000 dots in per day and you want to display 10 days of data. Each pull down of data generates 20,000 dots out. Suppose you are working to improve the look of a widget display and edit it just twice, Each edit plus the original pulls 20,000 dots out for a total of 60,000 dots which could take just a few seconds. All of a sudden you are locked out.
40,000 dots out may seem like a large number but it makes no sense at all. Please let me know quickly if you plan to continue this restriction.
Larry
Hi,
I think i’m having the same issues. I’m capturing dots in my widgets for the last 30 days. Since Friday I’ve started a new monitoring session and hence I’ve changed the start date in the widget from May 8 to June 6. This resulted in the widgets telling me ’ Error loading your data’ . Apparently I’ve surpassed the number of dots in a day. I have 2 devices sending data ( 10 parameters ) every 15 minutes.
Greetings,
C.
I must say 8 have enjoyed stem and find it ver6 useful, but the 50,000 limit which is new is blocking me a lot. It feels too low. Could you count the likely dots on a change of view or refresh, and warn me that I am about to lock myself out for a day?
Alternatively, I dont use the views wvwe5 day so could you accumulate my unused view dots within the month so that I can use the quota when I want?
I think Tony has a very good idea. Could you change the dots out limit from daily to monthly? It could still be the same total. That way when I make changes, reload pages, or other events that cause use spikes, I would not go over the limit.
Hi @tonyg,
Thanks for sharing your insights with the community.
Let me check with the team about the refresh of the dots out consumed upon a change of view and get back with a more solid answer. In the meantime, I confirm that when you’re close to run out of dots, we display an advertisement at the bottom of the web interface warning about that.
Now, the daily quota is not accumulative, so you can’t accumulate “unused” dots out in the next day.
Best,
–Sergio.
Thanks for sharing that idea, unfortunately, that cannot be implemented and I’m going to explain why with an example.
Let’s suppose instead of a daily quota, you have a monthly quota so let’s say it’s 1MM dots out per month, however on the 12th day of the month you needed to check a longer period and so you did several times in the day, suddenly you ran out of dots out, in such a scenario you would have to wait until the end of the month to be able to see data again, while with the current quota you have to wait until the next day.
I’ll, however, bring your proposal to the team for further analysis.
Best,
–Sergio.
Thanks Sergio. On the location of the warning, my use case is to change the timeframe in the dashboard, so I am looking at the top of the page, not the bottom. In fact, my dashboard requires a bit of scrolling to see the bottom. So the top would be better. Also would be useful to see used daily quotas and/or remaining dots from a link at the top so that I can see the effect of ingestion and export at each refresh’s or as time passes.
Ok thank you, look forward to updates.
I would just like to add my two cents on the STEM data extraction limits. Given the way the pages refresh dashboards and extract dots, either the limit should be raised or better control over refreshes should be provided. In editing dashboards and widgets, I hit the limit very quickly and it really is impacting my ability to learn what Uitdots capabilities are. After realizing the amount of dot extractions my dashboard showing seven days of data was generating, I attempted to clone the dashboard, remove a few widgets from the clone and set the time range for the dashboard to the past two days. Because of the refreshes, I hit the extraction limit within the first couple of operation and now have to wait until tomorrow to complete the task. Also, given the impact of bringing up the wrong dashboard could have on the extraction count, it would be nice to have the ability to select or confirm the dashboard before displaying - both in editing and in the main menus, since the main menu dashboard selection choice seems to select the last active dashboard, and I may want to bring up a different dashboard with fewer variables/widgets or a shorter default time range.
As a semi-retired technology executive with more than 50 years in the industry, I fully understand and respect that Ubidots is a business with cost control, revenue, and profit objectives. I think looking at competitors can be enlightening.
Mathworks offers a Thingspeak service similar to Ubidots that includes a free entry level version. Not only does that version provide extensive access to the MatLAB modeling and visualization tools, it has no data out limits and the data in limits are much higher than Ubidots. Mathworks then offers a step up version with even greater data in limits and still no data out restrictions plus a few more features for $90 per year.
What I am suggesting is that Ubidots could address their business objective by providing a new product version between STEM and their $50 per month product that would primarily address the dots in and out restrictions. I hope Ubidots will address the core problem rather than adding band-aids.
Larry
Hey @W6LVP @amestes @tonyg @hoehebeur23,
Thank all of you again for your valuable feedback, it is quite valuable as it is something that has happened to other users, and we certainly don’t want to be a bump in the road for their IoT initiatives. We’ve added a “+1” to this STEM feature request, and we’ll be updating this topic once a definitive decision is made. In the meantime, I’ve been authorized to extend your dots out capacity to 400,000 per day, to avoid you hit any limits during your IoT application’s development. To apply this limit, can each of you kindly confirm the username?
Best,
–Sergio.
My username is Domino.
Larry
hoehebeur23 confirmed.
C.
Dretful is me
In the military, there is an interesting concept when considering a strategy. “Don’t forget, the enemy gets a vote.” The same it true for business strategy but with an additional complication - customers. I would paraphrase the military expression for business this way. “Don’t forget, competitor and customers get a vote.”
Hi @tonyg @W6LVP @hoehebeur23,
Thanks for confirming your username. I already went ahead and increased the dots out limit to 400,000 in your accounts, hoping this new limit allows you to continue developing your applications.
I’ll stay tuned in case any of you face further issues.
Best,
–Sergio.
