Openwb pro timestamp...

[okaegi]

ich habe letzte Woche neine zweite openwb pro installiert.
Die connect Abfrage bringt bei der neuen openwb pro folgendes zurück:

Neue pro, die denk es ist noch 2022

Code: Alles auswählen

{"date":"2022:08:30-00:18:39","timestamp":1661818719,"powers":[1218.2,0,0],"power_all":1218.2,"currents":[5.418,0,0],"imported":90618,"exported":55,"plug_state":true,"charge_state":true,"phases_actual":1,"phases_target":1,"phases_in_use":1,"offered_current":6,"evse_signaling":"basic iec61851","v2g_ready":0,"vehicle_id":"--","serial":"575978"}

Bestehende pro , die ist schon im 2023

Code: Alles auswählen

{"date":"2023:01:18-22:20:09","timestamp":1674080409,"powers":[1217.2,1.7,2.7],"power_all":1221.2,"currents":[5.513,0.031,0.035],"imported":3102941,"exported":960,"plug_state":true,"charge_state":true,"phases_actual":1,"phases_target":1,"phases_in_use":1,"offered_current":6,"evse_signaling":"basic iec61851","v2g_ready":0,"vehicle_id":"--","serial":"493794"}

Hängen beide am gleichen lan.
Ich habe in meinem dhcp server, als timeserver meine synology zugewiesen:

Code: Alles auswählen

dhcp-option=3,192.168.1.222
dhcp-option=6,8.8.8.8
dhcp-option=42,192.168.1.50
address=/ntp1.dlink.com/192.168.1.50
address=/pool.ntp.org/192.168.1.50

Eine idee woran es liegt ?
Gruss Oliver