Tesla not woken before scheduled charging starts - evcc repeatedly sends charge current commands to sleeping vehicle

[Burnd100]

Title

Tesla remains asleep when charging should start — evcc repeatedly sends charge current commands without waking vehicle

Description

Hi,

Before opening a formal bug report, I would like to check whether this is expected behaviour, a configuration issue, or an evcc bug.

I use:

• Tesla Model Y Long Range
• Tesla Wall Connector Gen 3
• evcc
• Tesla vehicle integration with wake-up support
• PV charging / scheduled charging

The Tesla is connected overnight and goes into sleep mode.

On the morning of August 2, 2026, evcc should have started charging when sufficient PV surplus became available. However, charging did not start because the Tesla remained asleep.

The log shows that evcc repeatedly tried to change the charging current:

set charge current limit 6A: asleep
set charge current limit 14A: asleep
set charge current limit 13A: asleep

These messages repeated approximately every 90 seconds for more than an hour.

I could not find any log entry showing that evcc first attempted to wake the vehicle. It appears that evcc kept sending charge-current commands while the Tesla was still asleep.

The configuration/capabilities output indicates that wake-up is supported:

vehicle:
wakeup ✓

Eventually, I manually opened the Tesla app and pressed Start Charging.

This woke the Tesla immediately. After that, evcc was able to communicate with the vehicle and charging continued normally.

Timeline

From the longer debug log:

• Around 04:42, the log shows the vehicle disconnecting and reconnecting.
• After that, there is no relevant vehicle activity for several hours.
• From approximately 09:06 onward, evcc repeatedly tries to set the charge current.
• Each attempt fails with asleep.
• This continues for more than an hour.
• The vehicle only wakes after I manually press Start Charging in the Tesla app.

Expected behaviour

When charging should start while the Tesla is asleep, I would expect evcc to:

1. Detect that the vehicle is asleep.
2. Send a wake-up request.
3. Wait until the vehicle is online.
4. Set the required charging current.
5. Start or continue charging.

Actual behaviour

evcc repeatedly sends charge-current commands while the Tesla remains asleep.

Charging does not start until the vehicle is manually awakened through the Tesla app.

Questions

• Should evcc automatically wake the Tesla in this situation?
• Is a separate setting required to allow evcc to wake the vehicle before starting scheduled or PV charging?
• Could this be a bug where the wake-up action is not called, or where a failed wake-up is not clearly logged?
• Is it expected that evcc keeps retrying set charge current limit without first waiting for the vehicle to become online?

I have attached the longer debug log covering the period from early morning until after the failed charging attempts.

Thanks in advance.
49686a9f_evcc_2026-08-02T09-56-41.313Z.log

[Burnd100]

Update 2026-08-10 – reproduced again with clearer debug logging

I was able to reproduce the same issue again today. This time the debug log shows quite clearly what happens when EVCC tries to start charging while the Tesla is asleep.

The car was connected to the charger the entire time (charger status: B).

At 11:07 I switched to minpv. EVCC determined that charging should start and tried to set the Tesla charge current, but the command failed because the vehicle was asleep:

11:07:31 set charge mode: minpv
11:07:31 charger status: B
11:07:31 pv charge current: min 6A > 1.48A (-1018W @ 3p, battery: false)
11:07:34 ERROR set charge current limit 6A: asleep

About one minute later EVCC tried again. At this point there was already approximately 3.2 kW of grid export:

11:08:40 grid power: -3224W
11:08:40 pv 1 power: 8310W
11:08:40 charger status: B
11:08:40 pv charge current: min 6A > 4.67A (-3224W @ 3p, battery: false)
11:08:42 ERROR set charge current limit 6A: asleep

To rule out this being related specifically to PV/min+PV logic, I manually switched the charge mode to now at 11:08:54.

EVCC immediately tried to set the charging current, but again the Tesla was asleep:

11:08:54 set charge mode: now
11:08:55 charger status: B
11:08:55 validate current: 12A + (0A -> 16A) > 23A capped at 11A
11:08:57 ERROR set charge current limit 11A: asleep

Interestingly, at the next control cycle the command suddenly succeeded:

11:10:10 charger status: B
11:10:10 validate current: 11A + (0A -> 16A) > 23A capped at 12A
11:10:13 set charge current limit: 12A
11:10:15 charger enable

This seems to confirm the issue described in my original post: EVCC correctly decides that charging should start, but the command to the Tesla fails while the vehicle is asleep.

Once the Tesla becomes available, the same operation succeeds.

The particularly interesting part for me is that explicitly selecting now also initially fails with:

ERROR set charge current limit 11A: asleep

So this does not appear to be caused by the PV charging conditions themselves.

For scheduled/unattended charging this can result in charging not starting at the intended time if the Tesla has been parked long enough to be asleep.

I have attached the complete debug log covering the period leading up to this event as well.

Hopefully this additional log helps pinpoint whether EVCC should actively wake the Tesla and retry the command when it receives an asleep response.
evcc-20260810-111054-debug.log

[Burnd100]

Update: possible cause found – wake-up calls were disabled

I may have found the cause of the issue.

While checking my Tesla vehicle configuration in EVCC, I noticed that:

Disable wake-up calls was set to yes.

I have now changed this to no and will test later today whether scheduled charging starts correctly while the Tesla is asleep.

This would explain why EVCC was unable to start charging when the vehicle was asleep. However, if this turns out to be the cause, I think the logging could be clearer about it.

The logs showed errors related to the vehicle being asleep, for example when EVCC tried to execute a charging command, but there was no clear indication that EVCC was deliberately not attempting to wake the vehicle because wake-up calls were disabled in the configuration.

A message such as:

vehicle is asleep; wake-up skipped because wake-up calls are disabled

would have made the cause immediately clear and would have prevented a lot of troubleshooting around the Tesla Fleet API / MyTeslaMate command proxy.

For completeness: I have now also created a new Tesla API application and reconnected MyTeslaMate. EVCC is using the new Client ID, access token and refresh token. The MyTeslaMate command proxy and proxy token are working and EVCC validates the vehicle configuration successfully.

I will report back after testing whether changing Disable wake-up calls to no fully resolves the charging issue.