evcc-io
Config UI: Timezone configuration
Describe the bug
While traveling my web browser client is in a different timezone than my charger and auto. I adapted the time of a charging plan via the web client and was surprised to later discover than the time entered was in the timezone of my web client and not the charger and auto. As a consequence, charging did not occur as expected.
Request is to have time entered and shown in the web UI be the timezone of the charger and auto OR to configure and display the effective timezone in the UI in cases where the web browser timezone offset is different than charger and auto.
Steps to reproduce
- Set the timezone of your web browser client to be different than your charger and auto
- Set a schedule time
- Observe in the logs that the scheduled time shown in the web browser client is different than the effective time used by the charging plan
Configuration details
evcc checkconfig
[main ] INFO 2025/11/16 19:31:58 using config file: /etc/evcc.yaml
config valid
Log details
site ] DEBUG 2025/11/16 19:32:44 ----
[lp-1 ] DEBUG 2025/11/16 19:32:44 charge power: 0W
[lp-1 ] DEBUG 2025/11/16 19:32:44 charge currents: [0 0 0]A
[site ] DEBUG 2025/11/16 19:32:44 grid power: 358W
[site ] DEBUG 2025/11/16 19:32:44 pv 1 power: 0W
[site ] DEBUG 2025/11/16 19:32:44 !! solar production: accumulate set pv 4618.477kWh meter total (was: Accumulated: 2114.694kWh updated: 2025-11-16 19:32:14 +0100 CET meter: 4618.477kWh)
[site ] DEBUG 2025/11/16 19:32:44 !! solar production: accumulate moved pv from 2114.694 to 2114.694
[site ] DEBUG 2025/11/16 19:32:44 site power: 358W
[lp-1 ] DEBUG 2025/11/16 19:32:44 charge voltages: [233 0 0]V
[lp-1 ] DEBUG 2025/11/16 19:32:44 charge total import: 853.598kWh
[lp-1 ] DEBUG 2025/11/16 19:32:44 charger status: B
[lp-1 ] DEBUG 2025/11/16 19:32:44 next soc poll remaining time: 4m30s
[lp-1 ] DEBUG 2025/11/16 19:32:44 plan: charge 3h38m55s between 2025-11-17 02:21:05 +0100 CET until 2025-11-17 06:00:00 +0100 CET (power: 3680W, avg cost: 0.237)
[lp-1 ] DEBUG 2025/11/16 19:32:44 pv charge current: 0A = 0A + -1.56A (358W @ 1p)
[site ] DEBUG 2025/11/16 19:32:44 solar forecast: accumulated 0.000Wh from 2025-11-16 19:32:14 +0100 CET to 2025-11-16 19:32:44 +0100 CET
[site ] DEBUG 2025/11/16 19:32:44 solar forecast: produced 2114.694
[site ] DEBUG 2025/11/16 19:32:44 solar forecast: accumulated 1452.915kWh, produced 2114.694kWh, scale 1.455
What type of operating system or environment does evcc run on?
Docker container
External automation
- [x] I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.
Nightly build
- [x] I have verified that the issue is reproducible with the latest nightly build
Version
evcc version 0.207.6
While traveling my web browser client is in a different timezone than my charger and auto.
I'm not sure this is something worth fixing. How often would one charge a vehicle in a different timezone? If we changed this, time displayed would be server time. How would we relay this difference to local time to the user?
I'm not sure this is something worth fixing. How often would one charge a vehicle in a different timezone?
I agree it's uncommon but I ran into it while traveling and helping someone less technical who stayed home. From the current UI there is no way to know that the app wants you to enter the time in the browser's timezone and not the server's timezone.
If we changed this, time displayed would be server time.
Perfect. This effective ignores the timezone settings on the client. If you are setting charging details you care about the timezone of the charger and auto anyway.
How would we relay this difference to local time to the user?
Don't, if a user sets 9am in their browser, regardless of their client timezone settings make it 9am in the charger timezone.
Similar to Chris, I also ran into this remotely changing settings while being abroad. Especially his last paragraph, the actual grid connection/charger time zone, is what should matter in the end. Once dynamic pricing and/or different/time based additional chargers apply, anything but the actual grid connection/charger time zone will otherwise cause confusion and produce inconsistent results for the user.
While this may be an edge case, IMO it is a good reason to change this and make the actual grid connection/charger time zone the primary. The question might be though, if there is a need to adjust the time zone in the UI if the server time differs.
I agree, the clean solution would be to make the timezone of the evcc instance UI-configurable with default to browser timezone during the initial setup flow.
This however is indeed an edge-case. I'd assume that most repeating plan configuration happens in home timezone.
@naltatis this is a niche case. Either UI shows backend timezone or we should close here. No priority.