I’ve added a gauge and a graph for a temperature measurement and the graph scaling seems to be incorrect in the day view but ok in the 1hr view.
@gadjet Do you have the day view covering 10am to 11am as the one you show at present only goes up to 9am so it is impossible to tell if the scale is incorrect?
Ah! OK, this may be my misunderstanding, my expectation was that the rightmost point on both graphs would be the latest reading therefore they would both be ~6 degrees no matter what the zoom level?
It appears that the timescale on the day view is older, why would this be?
Cheers,
Phil
Probably because you have the last hour in the one hour view.
I don’t want to make this into a big issue but I expect to see the latest data on a graph whatever the zoom level I use !
If I select a day view why should I lose the last hour(s) data from the graph, that doesn’t make sense to me.
Am I wrong ?
Yes it’s a fair expectation to see the latest data in each zoom level.
Maybe @Dmitriy knows why it is not available.
@gadjet there is a known bug with the scale for all Blynk graphs on Android. I think your actual reading of 5.9 degrees is showing the bug offset of less than 5.9 degrees in the graphs. Difficult to tell with the scales involved but as the temperature went above 6 degrees you should see that the graph is still significantly below 6 degrees.
@Dmitriy I can understand the design of the granularities but maybe as an ‘enhancement’ join up the dots to current time when each graph is selected? This data doesn’t have to be stored, use existing data plus last available reading from the 1 minute data.
1 Like
Ok. I’ll think on that.
1 Like
Yes, the more I look at the graphs and axes the more issues I’m noticing. The scales do not seem to be consistent across the zoom levels or even accurate.
I hope the bug is soon fixed.
Cheers.
I am considering Blynk for my application using Android. I am mainly interested in plotting a number of weather station variables. If the graphs are not reliable then the app is not much use to me. Any chance this will be fixed in the near future?
also if you get a random (error) reading - it will be plotted and kill the scale…
thingspeak is better for graphing, plus has .csv data dumps…