When vitals are submitted to the cloud, for diagnostic purposes it should be possible to determine the time they have been submitted.
Observed behavior
When the submitted vitals are viewed in the "VITALS" tab in the console in any time frame other than "Last hour", the data appears to be averaged somehow and a incorrect time stamp is shown.
Steps to reproduce
Submit a vital (reconnect to network, refresh last vital...)
Go to "VITALS" tab in the console
Change time frame to anything other than "Last hour"
Hover witch the mouse over the data point
Observe mismatch between time stamp of data point and effective time of vital submission
Additionaly:
Wait more than one minute
Refresh the page
Observe how time stamp of data point has changed but still mismatches
Feature Requests
I use submission of hourly vitals to track the health of devices in a commercial context. In case the data stream misses data points or stops altogether, the vitals provide an easy and simple way to preliminary diagnose the cause for the loss of data (be it loss of cellular connection due to weak signal, discharged battery due to loss of power or, if everything looks fine maybe a bug in software). Sometimes drop outs are discovered only days in hindsight and the low resolution of the vitals history makes it hard to identify the time when vitals have been transmitted or not.
Expected behavior
When vitals are submitted to the cloud, for diagnostic purposes it should be possible to determine the time they have been submitted.
Observed behavior
When the submitted vitals are viewed in the "VITALS" tab in the console in any time frame other than "Last hour", the data appears to be averaged somehow and a incorrect time stamp is shown.
Steps to reproduce
Additionaly:
Feature Requests
I use submission of hourly vitals to track the health of devices in a commercial context. In case the data stream misses data points or stops altogether, the vitals provide an easy and simple way to preliminary diagnose the cause for the loss of data (be it loss of cellular connection due to weak signal, discharged battery due to loss of power or, if everything looks fine maybe a bug in software). Sometimes drop outs are discovered only days in hindsight and the low resolution of the vitals history makes it hard to identify the time when vitals have been transmitted or not.