[vz-dev] [volkszaehler/vzlogger] 975740: reject readings with really old timestamps, ... (#...

[Thorben T.]

  Branch: refs/heads/master
  Home:   https://github.com/volkszaehler/vzlogger
  Commit: 97574081fb194b170eb83e18584cc2b3a5866716
      https://github.com/volkszaehler/vzlogger/commit/97574081fb194b170eb83e18584cc2b3a5866716
  Author: Thorben T <r00t at constancy.org>
  Date:   2022-04-20 (Wed, 20 Apr 2022)

  Changed paths:
    M include/Config_Options.hpp
    M src/Config_Options.cpp
    M src/threads.cpp

  Log Message:
  -----------
  reject readings with really old timestamps, ... (#491)

these typically occur when a meter is sending timestamps but does
not have it's clock set properly, typically returning seconds since
power-up instead of seconds since the unix epoch (1970-01-01).
this often causes confusion, which can be easily avoided.

i arbitrarily picked 1990-01-01 as a cut-off point,
for one, few or no smart meters should have existed back then,
so nobody will be trying to read archived data that old,
for another a meter counting it's uptime would need twenty
years of uptime to generate a timestamp that is accepted.

for any obscure corner cases, a config option:
	"i_have_a_time_machine"
is provided to disable the check.