Edge Agent time is independent of the system time

[Tim_Hoffman]

Hi

Finally narrowed down the specifics of on ongoing issue with the Edge Agent.
If the edge agent starts before a raspberry pi can get a internet connection and update its time, then the edge agent uses the old time as its wall clock.

Data is then sent that is old (based on the hwclock).

Once the date is set, the edge agent does not appear to pick up the clock change, and requires a restart.

Cheers

Tim

[anaptfox]

Hi @Tim_Hoffman,

Just had a chat with one of our engineers, we have a hunch that it might be related to another bug you filed a while ago:

After a period of time - Timer in edge workflow doesn't fire

Please zip it and send it to support@losant.com. The system time changing is most likely the issue. The timer does use the system time to determine when to fire, even for simple intervals. When a timer fires, it calculates the next time it should fire based on the system’s time. When that time occurs, it fires again. This mechanism allows both the simple timer and the much more advanced “every day at 2pm” configurations to use the same underlying timer system. If the date were reset back sever…

In this case, if a Timer Node is triggering the workflow and you’re using “Use the time of the current payload”. I wonder if that may be the problem. Independent of the Timer Node, Device State should be using system time in all cases ( even if it changes ). I’m going to do some digging to see if I can reproduce what you’re seeing.