evcc-io
Tesla never sleeps when using `tesla-ble` and `twc3` after 0.209.6 introduced Tesla BLE: add getmaxcurrent
When using tesla-ble and twc3 after updating to latest evcc version, after car completes charging, because vehicle SOC limit is reached, the car never goes to sleep anymore.
After investigating the changelog and debugging the evcc I found that this PR https://github.com/evcc-io/evcc/pull/24893 may be related.
When debugging the application I noticed that this code called by loadpoint syncCharger()
// GetMaxCurrent implements the api.CurrentGetter interface
func (c *Twc3) GetMaxCurrent() (float64, error) {
v, ok := c.lp.GetVehicle().(api.CurrentGetter)
if !ok {
return 0, api.ErrNotAvailableS
}
return v.GetMaxCurrent()
}
now calls tesla-ble to check charge state on every loadpoint update and tesla-ble wakes up the car to get the max current.
Steps to reproduce
- Connect ant wait for Tesla to complete charging by reaching vehicle SOC limit
- See that the car never sleeps. On every loadpoint update charger max current is synced and wakes up the car.
Configuration details
vehicles:
- name: tesla
type: template
template: tesla-ble
capacity: 75
vin: XXXXXXX
url: http://192.168.0.101
port: 8081
phases: 1
loadpoints:
- title: Home
vehicle: tesla
charger: charger
chargers:
- name: charger
type: template
template: twc3
host: 192.168.0.101:81
Log details
[tesla ] TRACE 2025/11/30 18:47:04 GET http://tesla-ble-proxy.tesla-ble-proxy:8081/api/1/vehicles/XXXXXXXXXXXXX/vehicle_data?endpoints=charge_state
[tesla ] TRACE 2025/11/30 18:47:04 {"response":{"result":true,"reason":"The request was successfully processed.","vin":"XXXXXXXXXXXXX","command":"vehicle_data","response":{"charge_state":{"timestamp":1764524824,"charging_state":"Complete","charge_limit_soc":60,"charge_limit_soc_std":80,"charge_limit_soc_min":50,"charge_limit_soc_max":100,"battery_heater_on":false,"not_enough_power_to_heat":false,"max_range_charge_counter":0,"fast_charger_present":false,"fast_charger_type":"MCSingleWireCAN","battery_range":191.88846,"est_battery_range":191.88846,"ideal_battery_range":191.88846,"battery_level":60,"usable_battery_level":59,"charge_energy_added":6.62,"charge_miles_added_rated":28,"charge_miles_added_ideal":28,"charger_voltage":2,"charger_pilot_current":13,"charger_actual_current":0,"charger_power":0,"trip_charging":false,"charge_rate":0,"charge_port_door_open":true,"scheduled_charging_mode":"ScheduledChargingModeOff","scheduled_departure_time":1764569700,"scheduled_departure_time_minutes":495,"supercharger_session_trip_planner":false,"scheduled_charging_start_time":0,"scheduled_charging_pending":false,"user_charge_enable_request":false,"charge_enable_request":false,"charger_phases":0,"charge_port_latch":"Engaged","charge_current_request":13,"charge_current_request_max":13,"charge_amps":13,"off_peak_charging_enabled":false,"off_peak_charging_times":"","off_peak_hours_end_time":0,"preconditioning_enabled":true,"preconditioning_times":"weekdays","managed_charging_active":false,"managed_charging_user_canceled":false,"managed_charging_start_time":0,"charge_port_cold_weather_mode":false,"charge_port_color":"ChargePortColorOff","conn_charge_cable":"IEC","fast_charger_brand":"\u003cnil\u003e","minutes_to_full_charge":0}}}}
[twc3 ] TRACE 2025/11/30 18:47:34 GET http://twc3.teslamate/api/1/vitals
[twc3 ] TRACE 2025/11/30 18:47:34 {"contactor_closed":false,"vehicle_connected":true,"session_s":0,"grid_v":0.0,"grid_hz":49.828,"vehicle_current_a":0.0,"currentA_a":0.0,"currentB_a":0.0,"currentC_a":0.0,"currentN_a":0.0,"voltageA_v":0.0,"voltageB_v":0.0,"voltageC_v":0.0,"relay_coil_v":11.9,"pcba_temp_c":7.4,"handle_temp_c":1.8,"mcu_temp_c":6.4,"uptime_s":26103,"input_thermopile_uv":-176,"prox_v":0.0,"pilot_high_v":11.9,"pilot_low_v":11.8,"session_energy_wh":6660.0,"config_status":5,"evse_state":1,"current_alerts":[]}
[lp-1 ] DEBUG 2025/11/30 18:47:34 charge power: 0W
[lp-1 ] DEBUG 2025/11/30 18:47:34 charge currents: [0 0 0]A
[lp-1 ] DEBUG 2025/11/30 18:47:34 charge voltages: [0 0 0]V
[lp-1 ] DEBUG 2025/11/30 18:47:34 charger status: B
[tesla ] TRACE 2025/11/30 18:47:34 GET http://tesla-ble-proxy.tesla-ble-proxy:8081/api/1/vehicles/XXXXXXXXXXXXX/vehicle_data?endpoints=charge_state
[tesla ] TRACE 2025/11/30 18:47:35 {"response":{"result":true,"reason":"The request was successfully processed.","vin":"XXXXXXXXXXXXX","command":"vehicle_data","response":{"charge_state":{"timestamp":1764524855,"charging_state":"Complete","charge_limit_soc":60,"charge_limit_soc_std":80,"charge_limit_soc_min":50,"charge_limit_soc_max":100,"battery_heater_on":false,"not_enough_power_to_heat":false,"max_range_charge_counter":0,"fast_charger_present":false,"fast_charger_type":"MCSingleWireCAN","battery_range":191.88846,"est_battery_range":191.88846,"ideal_battery_range":191.88846,"battery_level":60,"usable_battery_level":59,"charge_energy_added":6.62,"charge_miles_added_rated":28,"charge_miles_added_ideal":28,"charger_voltage":2,"charger_pilot_current":13,"charger_actual_current":0,"charger_power":0,"trip_charging":false,"charge_rate":0,"charge_port_door_open":true,"scheduled_charging_mode":"ScheduledChargingModeOff","scheduled_departure_time":1764569700,"scheduled_departure_time_minutes":495,"supercharger_session_trip_planner":false,"scheduled_charging_start_time":0,"scheduled_charging_pending":false,"user_charge_enable_request":false,"charge_enable_request":false,"charger_phases":0,"charge_port_latch":"Engaged","charge_current_request":13,"charge_current_request_max":13,"charge_amps":13,"off_peak_charging_enabled":false,"off_peak_charging_times":"","off_peak_hours_end_time":0,"preconditioning_enabled":true,"preconditioning_times":"weekdays","managed_charging_active":false,"managed_charging_user_canceled":false,"managed_charging_start_time":0,"charge_port_cold_weather_mode":false,"charge_port_color":"ChargePortColorOff","conn_charge_cable":"IEC","fast_charger_brand":"\u003cnil\u003e","minutes_to_full_charge":0}}}}
[twc3 ] TRACE 2025/11/30 18:48:04 GET http://twc3.teslamate/api/1/vitals
[twc3 ] TRACE 2025/11/30 18:48:04 {"contactor_closed":false,"vehicle_connected":true,"session_s":0,"grid_v":0.0,"grid_hz":49.828,"vehicle_current_a":0.0,"currentA_a":0.0,"currentB_a":0.0,"currentC_a":0.0,"currentN_a":0.0,"voltageA_v":0.0,"voltageB_v":0.0,"voltageC_v":0.0,"relay_coil_v":11.9,"pcba_temp_c":7.4,"handle_temp_c":1.8,"mcu_temp_c":6.4,"uptime_s":26103,"input_thermopile_uv":-176,"prox_v":0.0,"pilot_high_v":11.9,"pilot_low_v":11.8,"session_energy_wh":6660.0,"config_status":5,"evse_state":1,"current_alerts":[]}
[lp-1 ] DEBUG 2025/11/30 18:48:04 charge power: 0W
[lp-1 ] DEBUG 2025/11/30 18:48:04 charge currents: [0 0 0]A
[lp-1 ] DEBUG 2025/11/30 18:48:04 charge voltages: [0 0 0]V
[lp-1 ] DEBUG 2025/11/30 18:48:04 charger status: B
[tesla ] TRACE 2025/11/30 18:48:04 GET http://tesla-ble-proxy.tesla-ble-proxy:8081/api/1/vehicles/XXXXXXXXXXXXX/vehicle_data?endpoints=charge_state
2025/11/30 18:48:04 DEBU Connection timeout ...
2025/11/30 18:48:04 DEBU Received HTTP request Handler=VehicleData Method=GET Endpoint="/api/1/vehicles/XXXXXXXXXXXXX/vehicle_data?endpoints=charge_state" Client=10.244.1.71:40236
2025/11/30 18:48:05 DEBU Waiting for next command ...
2025/11/30 18:48:05 INFO Connecting to Vehicle ...
2025/11/30 18:48:05 DEBU Connecting to vehicle (Attempt 1) ...
2025/11/30 18:48:05 DEBU Scanning for vehicle ...
2025/11/30 18:48:05 DEBU Beacon found LocalName=XXXXXXXXX Address=xXXXXXXXXXXXXXXX RSSI=-77
2025/11/30 18:48:06 DEBU Creating vehicle object ...
2025/11/30 18:48:06 DEBU Connecting ...
2025/11/30 18:48:06 DEBU Starting VCSEC session ...
2025/11/30 18:48:06 DEBU Car successfully wakeup
2025/11/30 18:48:06 DEBU Starting Infotainment session ...
2025/11/30 18:48:18 INFO Connection to vehicle established
2025/11/30 18:48:18 DEBU Operating connection ...
2025/11/30 18:48:18 INFO Executing command Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/11/30 18:48:18 INFO Successfully executed Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/11/30 18:48:18 DEBU Response Command=vehicle_data Status=200 Result=true Reason="The request was successfully processed."
2025/11/30 18:48:34 DEBU Received HTTP request Handler=VehicleData Method=GET Endpoint="/api/1/vehicles/XXXXXXXXXXXXX/vehicle_data?endpoints=charge_state" Client=10.244.1.71:40236
2025/11/30 18:48:34 INFO Executing command Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/11/30 18:48:34 INFO Successfully executed Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/11/30 18:48:34 DEBU Response Command=vehicle_data Status=200 Result=true Reason="The request was successfully processed."
2025/11/30 18:48:47 DEBU Connection timeout ...
2025/11/30 18:48:48 DEBU Waiting for next command ...
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.210.2
@wimaha I guess that's because getMaxCurrent gets evaluated at every single cycle. Only option I see is rolling back this addition?
/cc @ScumbagSteve @darkenbula @Dirk77777 @gaetancollaud @wimaha we can either accept the battery drain or remove the interface.
Or somebody has a batter idea- it's up to you ;)
To note that this bug doesn't seem to be restricted to twc3 (Tesla Wall Connector 3), but to all setups using Tesla ble vehicle-api. Can we restrict all calls through Tesla-ble (including the getmaxcurrent) to be limited to the times set up in polling configuration - which is usually while "charging"?
I think we have to remove getMaxCurrent for now. Maybe there is a better solution. https://github.com/evcc-io/evcc/pull/25890
Maybe I can add a function to the proxy that allows getMaxCurrent to be retrieved only when the car is awake.
Hello,
EVCC 0.211.0 here with Tesla Y, WC3 and tesla-ble config with a raspberry.
I didn't noticed this behavior. In fact my car goes "offline" which means asleep as far as I know. I'm using teslamate to check (this is the last 30days):
So for me I'm not bothered at all. Let me know if I ca enable some debug log if you're interested.
But if it's a problem, my suggestion would be to only get the maxCurrent when charging.
There might be more into this. I downgraded to 0.209.5 (which is the version prior the problematic getMaxCurrent polling) but it did not solve the issue. Car still not sleeping.
Maybe #25866 is not connected to this.
lp-1 ] DEBUG 2025/12/08 08:58:02 charger status: B
[lp-1 ] DEBUG 2025/12/08 08:58:02 pv charge current: 0A = 0A + -1.74A (400W @ 1p)
[site ] DEBUG 2025/12/08 08:58:02 solar forecast: accumulated 0.001Wh from 2025-12-08 08:57:29 +0100 CET to 2025-12-08 08:58:02 +0100 CET
[site ] DEBUG 2025/12/08 08:58:02 solar forecast: produced 0.357
[site ] DEBUG 2025/12/08 08:58:02 solar forecast: accumulated 0.690kWh, produced 0.357kWh, scale 0.518
[httpd ] TRACE 2025/12/08 08:58:03 GET /api/system/log
[httpd ] TRACE 2025/12/08 08:58:05 GET /api/state
[httpd ] TRACE 2025/12/08 08:58:15 GET /api/state
[httpd ] TRACE 2025/12/08 08:58:23 GET /api/system/log
[httpd ] TRACE 2025/12/08 08:58:24 GET /api/system/log
[httpd ] TRACE 2025/12/08 08:58:25 GET /api/state
[site ] DEBUG 2025/12/08 08:58:28 ----
[shelly] TRACE 2025/12/08 08:58:28 POST http://192.168.10.28/rpc/Switch.GetStatus
[shelly] TRACE 2025/12/08 08:58:28 {"id":0,"src":"evcc","method":"Switch.GetStatus"} -- {"id":0, "source":"init", "output":true, "apower":2.3, "voltage":230.9, "freq":50.0, "current":0.038, "aenergy":{"total":73723.440,"by_minute":[200.221,0.000,0.000],"minute_ts":1765180680}, "ret_aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1765180680},"temperature":{"tC":27.6, "tF":81.7}}
[lp-1 ] DEBUG 2025/12/08 08:58:28 charge power: 2W
[lp-1 ] DEBUG 2025/12/08 08:58:28 charge currents: [0.038 0 0]A
[site ] DEBUG 2025/12/08 08:58:28 grid power: 382W
[tasmota] TRACE 2025/12/08 08:58:28 GET http://192.168.10.234/cm?cmnd=Status+8&passwordXX=&user=XX
[db:4 ] TRACE 2025/12/08 08:58:28 GET http://192.168.10.110/api/inverter/id/0
[site ] DEBUG 2025/12/08 08:58:28 battery 1 power: 0W
[BKW_HP_L] TRACE 2025/12/08 08:58:28 GET http://192.168.10.205/status.html
[site ] DEBUG 2025/12/08 08:58:28 battery 1 soc: 50%
[site ] DEBUG 2025/12/08 08:58:28 pv 1 power: 1W
[db:4 ] TRACE 2025/12/08 08:58:29 {"id":0,"enabled":true,"name":"HP-rechts","serial":"112183215236","version":"10014","power_limit_read":100,"power_limit_ack":false,"max_pwr":300,"ts_last_success":1765180707,"generation":1,"status":2,"alarm_cnt":1,"rssi":-75,"ts_max_ac_pwr":1765180707,"ts_max_temp":1765180587,"ch":[[231.7,0.03,5.8,50.01,1.001,14.4,608.863,2,6.1,95.082,0,5.8,14.6],[31.4,0.2,6.1,2,608.863,2.033,6.1]],"ch_name":["AC",""],"ch_max_pwr":[null,300]}
[site ] DEBUG 2025/12/08 08:58:29 pv 2 power: 6W
[db:4 ] TRACE 2025/12/08 08:58:29 GET http://192.168.10.110/api/inverter/id/0
[tasmota] TRACE 2025/12/08 08:58:29 {"StatusSNS":{"Time":"2025-12-08T08:58:29","Switch1":"OFF","ENERGY":{"TotalStartTime":"2021-08-10T22:45:30","Total":2101.205,"Yesterday":0.215,"Today":0.004,"Power":11}}}
[site ] DEBUG 2025/12/08 08:58:29 pv 3 power: 11W
[db:4 ] TRACE 2025/12/08 08:58:29 {"id":0,"enabled":true,"name":"HP-rechts","serial":"112183215236","version":"10014","power_limit_read":100,"power_limit_ack":false,"max_pwr":300,"ts_last_success":1765180707,"generation":1,"status":2,"alarm_cnt":1,"rssi":-75,"ts_max_ac_pwr":1765180707,"ts_max_temp":1765180587,"ch":[[231.7,0.03,5.8,50.01,1.001,14.4,608.863,2,6.1,95.082,0,5.8,14.6],[31.4,0.2,6.1,2,608.863,2.033,6.1]],"ch_name":["AC",""],"ch_max_pwr":[null,300]}
[site ] DEBUG 2025/12/08 08:58:29 pv power: 18W
[site ] DEBUG 2025/12/08 08:58:29 !! solar production: accumulate add BKW_HP_L 0.000W power (was: Accumulated: 0.069kWh updated: 2025-12-08 08:57:59 +0100 CET)
[site ] DEBUG 2025/12/08 08:58:29 !! solar production: accumulate moved BKW_HP_L from 0.069 to 0.069
[site ] DEBUG 2025/12/08 08:58:29 !! solar production: accumulate set db:4 608.863kWh meter total (was: Accumulated: 0.091kWh updated: 2025-12-08 08:57:59 +0100 CET meter: 608.863kWh)
[site ] DEBUG 2025/12/08 08:58:29 !! solar production: accumulate moved db:4 from 0.091 to 0.091
[site ] DEBUG 2025/12/08 08:58:29 !! solar production: accumulate set db:9 2101.205kWh meter total (was: Accumulated: 0.197kWh updated: 2025-12-08 08:57:59 +0100 CET meter: 2101.205kWh)
[site ] DEBUG 2025/12/08 08:58:29 !! solar production: accumulate moved db:9 from 0.197 to 0.197
[site ] DEBUG 2025/12/08 08:58:29 site power: 382W
[lp-1 ] DEBUG 2025/12/08 08:58:29 charge voltages: [231 0 0]V
[lp-1 ] DEBUG 2025/12/08 08:58:29 detected connected phases: 1p
[lp-1 ] DEBUG 2025/12/08 08:58:29 charge total import: 73.723kWh
[db:1 ] TRACE 2025/12/08 08:58:29 GET http://192.168.1.7:8080/api/1/vehicles/XXX/vehicle_data?endpoints=charge_state
[httpd ] TRACE 2025/12/08 08:58:29 GET /api/system/log
The last two lines show the TeslaBLE call, even though the charger status is only "B" (Connected). My evcc.yaml however is set up to only query while charging.
I've just scanned back through my last 2 weeks of battery stats and i don't see any unusual battery drain at all
@darkenbula @gaetancollaud maybe the configuration is different if you don't see this behavior. Can you attach the logs during the time the car reaches set vehicle SoC limit?
I have set SoC limit on the vehicle less than current charge and restarted latest 0.211.0 version of EVCC. The logs shows some kind of timer: wake-up vehicle, attempts left: 5 and tries to wake up the car by sending wake_up command to tesla-ble.
After timer finishes, the car should not be waked up anymore, but the charge_state is still queried every 30 seconds (update interval) and then tesla-ble wakes up the car.
I am attaching the logs from today.
Maybe I am missing some configuration which would prevent querying the charge_state if charger is completed: charger_status: B
Car finished charging at 5:40am
I also see no battery drain once car has finished charging
Can you provide TRACE logging and add additional areas: tesla-ble and twc3? I only see loadpoints and site areas.
On Mon, 8 Dec 2025 at 21:20, darkenbula @.***> wrote:
darkenbula left a comment (evcc-io/evcc#25707) https://github.com/evcc-io/evcc/issues/25707#issuecomment-3628650176
Car finished charging at 5:40am
I also see no battery drain once car has finished charging
evcc.txt https://github.com/user-attachments/files/24039980/evcc.txt
— Reply to this email directly, view it on GitHub https://github.com/evcc-io/evcc/issues/25707#issuecomment-3628650176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKW7PWIUQ6HW2MRKAK5SYD4AXFRLAVCNFSM6AAAAACNTKM75GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRYGY2TAMJXGY . You are receiving this because you authored the thread.Message ID: @.***>
Thanks for providing the logs. Are you using Tesla Wall Charger and how charging is controlled? Are you using tesla-ble? Can you show the EVCC configuration?
In my case I am using Mobile Connector, the pne where you connect the car to the 220V outlet directly and controlling is via tesla-ble. I wonder if it works differently. The teslamate vitas response is also a bit different.
On Mon, 8 Dec 2025 at 21:36, darkenbula @.***> wrote:
darkenbula left a comment (evcc-io/evcc#25707) https://github.com/evcc-io/evcc/issues/25707#issuecomment-3628704015
trace.txt https://github.com/user-attachments/files/24040195/trace.txt
— Reply to this email directly, view it on GitHub https://github.com/evcc-io/evcc/issues/25707#issuecomment-3628704015, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKW7PSDQJQJ76EHCLKB6RL4AXHLBAVCNFSM6AAAAACNTKM75GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRYG4YDIMBRGU . You are receiving this because you authored the thread.Message ID: @.***>
I'm using the Tesla Wall Connector, Tesla-BLE running in docker on a Pi Zero 2
- name: my_car2
type: template
template: tesla-ble
title: Tesla Model 3 # Title, Will be displayed in the user interface (optional)
capacity: 62.3 # Battery capacity (kWh), optional
vin: LRW3F7FS***705365 # Vehicle Identification Number, Required for BLE connection
url: http://192.168.1.80 # URL, URL of the Tesla BLE HTTP Proxy
port: 8080 # Port, Port of the Tesla BLE HTTP Proxy (optional)
mode: PV
Sorry, I missed ble.txt logs. I see that it queries the charge state every minute as well, but because log verbosity is only INFO, I cannot confirm if it wakes up the car.
Can you verify that the car is sleeping in Tesla app? Is it possible to enable DEBUG logging in tesla-ble by setting:
env:
- name: logLevel
value: debug
@wimaha can you confirm that you cannot query charge_state without waking up the car? Because from @darkenbula ble.txt logs clearly the vehicle is queried every minute for charge_state:
2025/12/08 19:38:52 INFO Connecting to Vehicle ...
2025/12/08 19:38:54 INFO Connection to vehicle established
2025/12/08 19:38:54 INFO Executing command Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/12/08 19:38:54 INFO Successfully executed Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/12/08 19:38:54 INFO Executing command Command=charge_stop Body=map[]
2025/12/08 19:38:54 INFO Successfully executed Command=charge_stop Body=map[]
I can get additional logs tomorrow, but I don’t experience any unusual battery drain
Thanks. I understand that battery drain can be minimal, but Tesla is supposted to go to sleep after it finishes charging. Especially when it is winter and cold outside, like in my country.
I did some more testing. I plugged in my mobile charger, but stopped charging and as expected the car did not go to sleep (even though no charge was running). I left the mobile charger plugged in the car, but removed the plug from the power outlet (so there is no more standby energy drain).
Then the car was sleeping all night.
Is it possible my initial assumption is correct (see the separate issue I linked above) and the polling (which keeps the car awake) has to do with the standby energy pulled by the charger?
Maybe the people whose car goes to sleep correctly have no standby energy drain, and for the rest evcc considers the standby energy of the charger as as a charging process?
In loadpoint.go syncCharger the current is always validated when the charger is in enabled state. We don't check charging. Wondering why- in the issue here- the charger would be enabled? Fast charging after vehicle has reached 100%?
When is a charging brick (which has no direct connection, energy only measured by Shelly) considered enabled?
I understood this issue is about tesla-ble? So that's the charger considered enabled. It is enabled when vehicle is allowed to charge and visible in the logfile.
Not sure if I miss the point, but it's a henn-egg problem.
Tesla-ble is usually set to only query when charging - but how is determined if the car is charging without polling it?
That's where my assumption came from, that in order to realize if a charge started, the energy consumption from the charger (which is in my case measured by Shelly, because the charging brick does not deliver information) might be used.