Forum Replies Created
-
Glad to hear that, and if this is the case, marketing wise, you would be better off limiting the minute data when that plan is actually available.
People are more likely to subscribe when they feel the pain. By removing the ability now when there is no alternative, they will be forced to get use to doing without the data, and are less likely to subscribe when an alternative actually becomes available 🙂
If not, please consider restricting to 8 days until the subscription is available (instead of 3), so we can do a weekly download. Every two days is just not practical.
Again, if people cannot get the data in a practical way for a long time, they will have to get use to not using it and many will be less likely to subscribe…
My 2 cents
I forgot to add that last post and not last thread (if this is what is being shown) is really what is useful.
Ideally, if you could have a What’s new page showing all the new post since the last visit, that would be ideal for people who want to quickly check the forum for new discussion or answers.
This help engage people more, as they can quickly see what is going on and be tempted to participate.
If one has to go drill down into every sub forum to see if there are new elements, they are likely to skip.I created the same difference table with the Feb 5th seconds data.
I calculated the minute data from the seconds data, and made the difference with the downloaded minute data. The blips illustrated in the first post appear across all CTs that have a non zero reading.
To detect all discrepancies between the hourly report and the minute report, I recalculated all the hourly data from the minute data in excel and made a difference table between the recalculated hourly data and the downloaded hourly data, and the error in the downloaded hourly data appear clearly, always over two consecutive numbers, with equal deviation up and down.
This is the same phenomenon that was initially detected and reported in this thread, between the seconds data and the minute data.
So I assume all starts with the seconds data that is correct, then when minutes data is calculated that error occurs occasionally, and then when the Hourly data is calculated, the same happens (I have not check daily data yet)
FYI,
It seems the same issue is happening between Hours interval reporting and Minute interval reporting.
Sometimes the hour data will deviate from the minute data in the same way as described above. One value will be higher than it should the next below what it should, then back to normal.
One more suggestion to the above:
Unless I missed a functionality, it can be very hard to inspect a past event using the app graph page. Problem being there is no way to directly go to a specific date and time except by scrolling, which can take forever depending how far back you are trying to goo in any specific time view.
I have already suggested to give us a calendar tool to select a specific day to go to (and auto scale the view to that day). I also suggested to allow us to scale axis with pinch to zoom.
In addition to the above, the functionality below would go a long way to make that process easier.When switching between time Views (sec, min, hour day…), maintain the time the cursor is currently on to prevent having to scroll forever.
For example, let us say you want to check the minute graph of a load 5 days before the current day/time. Right now you have to scroll the whole 5 days in the minute view to do that.
Instead we could use the day view to scroll to that day, then switch to minute view and still be on that day.Same if you wish to check the second view of a load a long time before current time, you could approach it using the hour view, then switch back to the second view when you are on the hour in question.
Thank you for listening 🙂
I was told by Emporia, that although the Vue Gen 2 can only store 5 to 15mn data, if it looses connection for more than that, it still keeps track of the overall consumption and will fill in the missing data with the average between the moment it lost connection and the moment it reconnects (showing a flat consumption level).
This means that although you would not see the actual consumption fluctuations for the period connection was lost, the overall consumption number should be correct.
