Require Valid time hierarchy

[neilh10]

For a node LCC45, on 2024Feb27 12:11 it was found in a loop using time, that was determined to be invalid, that lead to it setting a default time, and POSTing using that time
Its a Mayfly 0.5b with an external humidity sensor on I2C, that was showing to be invalid -9999.0
The "Bad time 1119829665" or - 0x42BF3EA1

Bad time 1119829665 2005-06-26 Setting to 2022-01-02T00:00:00-08:00

The .csv file, nh_LCC45_2023-11-17 showed that on the 26th at 6:15am it had a bad read humidiy sensor reading,
and then all subsequent time stamps are 2022-01-02T00:00:00-08:00

Are rebooting with an external LiIon battery pack to provide charging, it returned to normal operation.