Timing of sleep and therefore wakeup uses Time.now() which is completely inaccurate without a good recent cloud connection. On first wake/power-up, clock resets to Sat Jan 01 2000, so all subsequent wakes happen at intervals from there, unrelated to real time. Not sure if there's a robust fix to this but it's good to note that first sample or maybe a couple could have terribly inaccurate timestamps.
Does it make sense to add logic block that looks to see if date is in 2000 (or at least before some year closer to present) and not publish that data if so?
Timing of sleep and therefore wakeup uses
Time.now()
which is completely inaccurate without a good recent cloud connection. On first wake/power-up, clock resets to Sat Jan 01 2000, so all subsequent wakes happen at intervals from there, unrelated to real time. Not sure if there's a robust fix to this but it's good to note that first sample or maybe a couple could have terribly inaccurate timestamps.