Dashboard
Cake Red
LoRaWAN
Guides
Historical Data
Use the graphical database viewer to visualize your measured values.
Datacake has a database viewer that allows you to view and compare sensor data from your sensor. We also call this viewer the history of a device.
Quick Start
To open the history view, navigate to the history tab using the tab bar on the device view.
You will see the following view.
When the history view is opened for the first time, no fields are selected yet to be visualized.
To be able to select fields, please scroll further down. There you will find a list with all fields of the database.
Now select the respective fields that you want to display on the history and simply click on the checkbox next to the respective field.
If you now scroll up again, you will see that the visualization in the form of a chart for the respective fields is now displayed.
Reference
Time Range
Using a drop-down, predefined time ranges can be selected for the display of the data.
Alternatively, individual time ranges can be defined. To do this, simply click on the text box that displays the current time range. A window opens for the graphical selection of a time range.
Skipping Time-Ranges
You can use both the previous and next buttons next to the time range input field in order to jump to the next or previous time range.
This works great if you for example have selected a time range preset like day, week or month and if you want to jump between days, weeks or month.
If you have selected a custom time range these buttons will skip to the amount of time (and date) defined in the time range selector.
Resolution
The resolution defines the time intervals with which the data is queried by the API over the specified time range.
The settings are defined as follows.
Auto-Resolution
This works in a way that the Chart requests at least as much datapoints from the backend as pixels are available on the screen.
Manual Resolution
You can override the automatic resolution setting by specifying your own resolution. However, there is a maximum number of data points that can be retrieved from the backend to protect our API limits.
Background
So, if you selected the period of one year as an example, and set a resolution of 1 minute, the number of data points would lead to several million per selected field.
Even if our servers were able to provide this number of data points, it does not make sense to request such a large amount, as the graphical representation will not have enough pixels on the screen to display it properly. So data points would be thrown away anyway.
Interpolation
If you select a resolution that is lower than the transmission frequency of your sensors, then all data points that lie within the resolution are combined and an average is formed.
As an example think of a sensor that sends every
5 Minutes and a Resolution set to 1 hour, this makes:- 12 Messages per Hour
- Average our 12 Messages = 1 Value for Resolution of
1 hour.
Effects of Resolution
In the following screenshots, you can see the effects of the resolution.
The first screenshot shows you a setting for Auto-Resolution. There are more pixels on the screen available than data points for the selected fields so the backend fills all pixels with repetition of data points.
- The time range is set to
one weekand the Sensor sends about every one to two hours generally with shorter intervals on steeper value changes. - You can clearly see the quantization effects.
- No averaging is applied here as there is more space than data points.
Resolution Auto = More pixels than data points available
Now in the following screenshot, you see the same time range as above but with a resolution set to a manual value of 1 hour.
Resolution 1 Hour = More Smoothing
As most of the time, the sensor sends every one or two hours, there is still no averaging applied (no interpolation) but you can see that the quantization does look different. There are now less datapoints than pixels still but there is no fill happening.
Gap Filling
The filling of gaps works in conjunction with the resolution. To explain how it works we select the following settings:
- Time range
1 week - Resolution set to
30 Minutes
Gap Filling enabled
As long as the filling of gaps is enabled you see a full line chart.
Gap Filling disabled
Now, if we deactivate the gap-filling option (which is enabled by default) we can see a change happening.
You can see that the chart is no longer fully displayed and only a few areas show a chart. What does this mean?
Remember that we have set the resolution to 30 minutes. If you uncheck the "Fill Gaps" option, all areas where there are data points with a time span greater than 30 minutes will be hidden.
This means that the chart above shows only the area where there are data points whose time span is less than or equal to 30 minutes.
Field Statistics
Above the table for selecting the fields to be displayed on the history, there are additional column headers, which show you statistics for the respective fields.
The following statistical information is available for each field.
- Current Value
- Average
- Minimum
- Maximum
Time Range for Statistics
The time range for each statistic (average, maximum, minimum) is defined by the time range of the history.
Time for Maximum, Minimum
If you hover over a Maximum or Minimum Value you can see the time this event has occurred.
No-Data
If you see a "No Data" tag or "null" sign on the list of fields this means that the field has not yet received any data or the decoder has not yet stored any information on that field.
​
Last modified 3mo ago
Export as PDF
Copy link