Wrong Time in Logbook if refreshed (sqllite to mariadb conversion)

[badbee]

If I am staying the logbook, all new entries are fine. But If I am refreshing it, then everything jumps one hour back.

I am using a HASS Container and a seperate mariadb / influxdb2 container. The host and the LXC have TZ Europe/Berlin, for the containers I tried the same or left it at UTC.
Currently, HA is 36 minutes off, sometimes different, but the time is right, for every container/device/host.

It seems, that the time for all entries is set to the same time. Like the time isn’t saved as it should and gets ‘rounded’.

If I check the events in the database, the unix timestamp is always ending with ‘0000’.

If I am checking the time with the date_time sensor, it is okay.

[tom_l]

The time displayed by the logbook is represented by the timezone your PC / mobile device on which the web browser is used is set to.

Home timezone display in browser

I’m currently at a location 6 hours behind my home timezone. Nearly all times showing the browser (graphs etc…, with the exception of sensor.time) are for my current local timezone (UTC +5) rather than my actual home timezone (UTC +11) where the HA server is located. This is really confusing. “No, the alarm wasn’t armed at 1am, it was 7am, etc…” Can the frontend be set to use the home timezone no matter where the client is located?

[badbee]

My Browser is also in the Europe/Berlin Timezone.

[badbee]

Problem was the wrong datatype from the sqllite to mariadb conversion.
I had to change the float datatypes in the tables to double.