pH chart data not in sequential order

Osbie Feel · Feb 1, 2024

Hi everyone, wondering if you can help with an issue I am having with my historical pH chart.

I have had my reef-pi set up for about 3 weeks and everything has been running very satisfactorily. However this morning I saw the following when I checked the historical pH chart:

As you can see the data for February 1st has been overlaid on the data from January 30. Rebooting the pi and reloading reef-pi has not fixed the issue. I also found this thread here where @Ranjib suggested increasing the values in the telemetry section, but this did not work, not to mention that I don't have enough data here to run up against that limit (default is 720 which is 30 days of readings). Please let me know what else I can try to get this data straightened out! Thanks

Sral · Feb 2, 2024

Osbie Feel said:
Hi everyone, wondering if you can help with an issue I am having with my historical pH chart.

I have had my reef-pi set up for about 3 weeks and everything has been running very satisfactorily. However this morning I saw the following when I checked the historical pH chart:

As you can see the data for February 1st has been overlaid on the data from January 30. Rebooting the pi and reloading reef-pi has not fixed the issue. I also found this thread here where @Ranjib suggested increasing the values in the telemetry section, but this did not work, not to mention that I don't have enough data here to run up against that limit (default is 720 which is 30 days of readings). Please let me know what else I can try to get this data straightened out! Thanks

For me rebooting the PI and clearing the browser's cache (CTRL+F5) helped.

Osbie Feel · Feb 2, 2024

Thanks for the input. Unfortunately I have tried that multiple times and it does not seem to have helped. Tomorrow the chart will 'catch up' with itself, I'm wondering if the problem will simply sort itself out then...

Osbie Feel · Feb 4, 2024

Well good news, it was as I suspected, once the data caught up to data from the 31st, the chart seems to be back on track. So it seems the issue has sorted itself out.