You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I now had the problem that a single entry was from 1970. This makes the diagram look very strange.
Is there a feature that checks whether the data set matches the previous one? (Timestamp)
There is a flag for the maximum delta water length.
The text was updated successfully, but these errors were encountered:
The date of 01.01.1970 is the fallback date if NTP is disabled or no NTP server can be reached. After a cold start (but not on a reboot), the ESP does not yet have any date/time information, thus must fallback to the fall back date/time.
Please check the log of the device. Did you have a power cycle?
If you transmit the data with MQTT or to InfluxDB or so, this should not be an issue.
I was already aware that this date is set after a cold start of Linux systems and that the NTP has not yet set a current date. It makes sense to mark this entry as ERROR if the previous date is more recent.
Perhaps a plausibility check will be added after all.
This has nothing to with Linux. It is n issue of any system without a RTC (Real time Clock) which would keep the clock running even if the device is switched off.
The Feature
Plausibility check for the date?
I now had the problem that a single entry was from 1970. This makes the diagram look very strange.
Is there a feature that checks whether the data set matches the previous one? (Timestamp)
There is a flag for the maximum delta water length.
The text was updated successfully, but these errors were encountered: