Page 1 of 1

All logs are two hours off (late) probably since 2025.1

Posted: Tuesday 10 June 2025 20:02
by WilcoEHV
Hi,
I noticed before but did not pay attention to it (like Solaredge producing power around 3:30 am) but now I found out all my logs are 2 hours late.

Today I had the dishwasher and laundry running and there should be power consumption spikes around/ between 15:00 and 16:00.
Logs show spikes between 13:00 and 14:00; I wasn't even at home around that time!

This happens with temperature with RFX com, Power by P1 with LAN interface, Z-wave temp and power consumption, water by HW API and solaredge via API.
In all these logs the last entry is 2 hours ago (I look now at 19:47 and P1 shows last entry 17:45).
The tiles on the utility page show correct time and (I assume) correct values.

Logs of switches are accurate and light run at the right time (RFX com).

Time on the Domoticz dashboard is correct as is the time on my raspberry desktop when i log in with VNC.
Time zone is set to Amsterdam (wich is correct for me).

Anybody any idea what is wrong?

I'm on raspberry 3B with Bullseye and Domoticz 2025.1 (stable).

Re: All logs are two hours off (late) probably since 2025.1

Posted: Tuesday 10 June 2025 20:18
by Varazir
Running in docker ?

Re: All logs are two hours off (late) probably since 2025.1

Posted: Wednesday 11 June 2025 1:15
by waltervl
Did you set location settings in menu Setup settings correctly?
Time on your server is correctly?
When running docker time settings are set correctly?

Re: All logs are two hours off (late) probably since 2025.1

Posted: Wednesday 11 June 2025 7:57
by gizmocuz
Did you set the date/time correct on your Raspberry Pi? (with raspi-config)

"If" you are using docker, you of course had a look at the config, and noticed that there is a timezone setting that you might need to change?

Code: Select all

environment:
      - TZ=Europe/Amsterdam