wrong time in reported events

Marek Skrzypczynski shared this problem ago

Solved

Hi,

my zipato reports wrong time in events. My time is set correct GMT+2 but in reports I have GMT?

Any idea why is so?

The same problem 0

Replies (8)

Andre ●

Same issue here. problem coming from Zipato.

Reply URL

Andre ●

Always the problem !.!

Reply URL

Guest ●

Hello,

we will investigate and if any issues appear we will fix them accordingly.

Thank you for your report

Reply URL

Henning ●

I also see a 2hr difference in my logs today!?

Reply URL

John Rabbit ●

Maybe it is fixed but i don't see any offset in the (latest and live) events on desktop and ZP2. However on Android there is a delta of 2 hours. I guess it has something to do with the api.

Reply URL

Henning ●

Hi John! That is strange because I still have the 2hr offset right now.

// Henning

Reply URL

John Rabbit ●

Hi Henning, I just saw there is also a 2 hr offset when you choose a device in the desktop. if you make no selection (so latest or live) event there is no delay.

If i remember it well the events are first recorded raw in some kind of table (look like this table is correct). However there is another mechanism to split these events (devices etc) and there is something wrong

URL

David Pritchard ●

Yep, all the log times are wrong - all appearing in UTC. This is just like the end-of-month log disappearance bug: the same thing keeps happening and Zipato never do anything to stop it.

Reply URL

Henning ●

I submitted a ticket and my 2hr offset was fixed today around 17:20 in my local time CET+2.

So my logs now have a gap from 15:20 to 17:20 even if two events happened the same minutes.

Anyway. I am happy for now.

Reply URL