I found 2 NaN for MySensors N2S2:
[1423865953173, NaN],[1423865964920, NaN],
Be careful what you are writing in DB. Filter NaN on sensor node.
I've added additional filters in chart and in new release it will work also for cases like this.
It was not a bug but a feature .
I want to know by monitoring the protocol that a node is working properly and its sensors are OK. The ratio of NaN reception is a good health indication.
Previously to EasyIoT, I was using Cacti, RRDtool and a python script to record values of 20x DS18B20 directly attached to the RPi for calibration purpose. I was confronted to readout errors occurrences that I wanted to record. So I meet the NaN concept and found that nowadays databases involved in the RPi area could handle this "no value", (they are now 3-state compliant ) .
I didn't thought it could be a problem for your Framwork and I am happy that you will adapt it so I won't have to remove this feature. Many thanks
EasyIoT wrote: I've added additional filters in chart and in new release it will work also for cases like this.
Does this mean that you change the way you record the samples or the way you process de data extracted from the sqlite dB?
I prefer 2nd solution, but does it affect the reactivity of chart display?
EasyIoT wrote: I've added additional filters in chart and in new release it will work also for cases like this.
Does this mean that you change the way you record the samples or the way you process de data extracted from the sqlite dB?
I prefer 2nd solution, but does it affect the reactivity of chart display?