Cannot fully understand to es.
Could explain please?
In the event log there is "timestamp (+01:00)" seems to be server.timestamp... but then why +01:00?
It is not the "timestamp (+01:00)" in the messages log.
The counters seems to get this second "timestamp (+01:00)"
None is on time:
Server.timestamp seems UTC +1 (and is like the time on my tablet where I access flespi).
Timestamp (+01:00) in messages list is not the time setted in my device (when I ask position via SMS it sends the actual correct time: UTC +2 where I am now).

For example the first timestamp (+01:00) shown (08:37:39) was sent by device at 09:37:39 (UTC+2).
Maybe I have some wrong settings in flespi?
What to do in order to let flespi show the actual time of the device, and thus I get correct results from calculations, as now I get 1 hour more

    • dexif

    • Post #2
    • Edited

    All timestamps on flespi are stored in utc+0 timezone. But for web applications, we convert unix timestamps to formatted values like date and time, with the timezone offset configured on your system (browser). This offset you can see in the column headers of the toolbox.

      Logged out
      Updated timezone on tablet (now +2, was +1)
      Logged in
      Timestamps have now all 1 hour more
      server.timestamp is like local time
      timestamp in events log is like local time (but label still shows +01:00)
      timestamp in messages log is +2 hours respect local time (and label still shows +01:00).
      Thus if I have correctly understood I shell update timezone of device (now +2) to plain UTC (i.e. +0)?

        Yes your device should be configured to plain UTC +0

          Write a Reply...