Tesla Wall Connector Gen3 API timeout after prolonged polling (/api/1/vitals)

[GillesWi]

Describe the bug

After a few hours of operation, EVCC loses connection to the Tesla Wall Connector (Gen 3).
Also in logs seems like EVCC is polling the TWC too much, and this overloads the API

Error:
Get "http://192.168.1.xxx/api/1/vitals": dial tcp 192.168.1.xxx:80: i/o timeout

Important observations:

• Device is still reachable via ping
• Tesla app continues to work
• Restarting EVCC does NOT fix the issue
• Only power cycling the Wall Connector (via circuit breaker) restores API functionality

This suggests the local HTTP API of the Wall Connector becomes unresponsive over time.

Steps to reproduce

1. Connect EVCC to Tesla Wall Connector (Gen 3) using local API
2. Let EVCC poll the charger (default or 30–60s interval)
3. After several hours, API stops responding
4. EVCC shows timeout errors
5. Power cycle required to recover

Configuration details

/

Log details

[lp-1 ] ERROR 2026/03/24 14:16:27 charge voltages: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[lp-1 ] ERROR 2026/03/24 14:16:27 charge rater: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[lp-1 ] ERROR 2026/03/24 14:16:27 charger status: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[site ] DEBUG 2026/03/24 14:16:27 solar forecast: accumulated 0.013Wh from 2026-03-24 14:15:27 +0100 CET to 2026-03-24 14:16:27 +0100 CET
[site ] DEBUG 2026/03/24 14:16:27 solar forecast: produced 41.142
[site ] DEBUG 2026/03/24 14:16:27 solar forecast: accumulated 27.040kWh, produced 41.142kWh, scale 1.522
[site ] DEBUG 2026/03/24 14:17:02 ----
[lp-1 ] ERROR 2026/03/24 14:17:13 charge power: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[lp-1 ] ERROR 2026/03/24 14:17:27 charge currents: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[circuit-main] DEBUG 2026/03/24 14:17:27 power: -31W
[circuit-main] DEBUG 2026/03/24 14:17:27 current: 2.96A
[site ] DEBUG 2026/03/24 14:17:27 grid power: -31W
[site ] DEBUG 2026/03/24 14:17:27 grid currents: [2.96 0 0]A
[site ] DEBUG 2026/03/24 14:17:27 battery 2 power: -6W
[site ] DEBUG 2026/03/24 14:17:27 battery 1 power: -8W
[site ] DEBUG 2026/03/24 14:17:27 battery 1 soc: 47%
[site ] DEBUG 2026/03/24 14:17:27 battery 2 soc: 47%
[site ] DEBUG 2026/03/24 14:17:27 battery power: -14W
[site ] DEBUG 2026/03/24 14:17:27 battery soc: 47%
[site ] DEBUG 2026/03/24 14:17:27 pv 1 power: 2071W
[site ] DEBUG 2026/03/24 14:17:28 !! solar production: accumulate set db:11 531.441kWh meter total (was: Accumulated: 41.142kWh updated: 2026-03-24 14:16:27 +0100 CET meter: 531.405kWh)
[site ] DEBUG 2026/03/24 14:17:28 !! solar production: accumulate moved db:11 from 41.142 to 41.178
[site ] DEBUG 2026/03/24 14:17:28 battery has priority at soc 47% (< 50%)
[site ] DEBUG 2026/03/24 14:17:28 site power: 69W
[lp-1 ] ERROR 2026/03/24 14:17:28 charge voltages: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[lp-1 ] ERROR 2026/03/24 14:17:28 charge rater: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[lp-1 ] ERROR 2026/03/24 14:17:28 charger status: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout
[site ] DEBUG 2026/03/24 14:17:28 solar forecast: accumulated 0.013Wh from 2026-03-24 14:16:27 +0100 CET to 2026-03-24 14:17:28 +0100 CET
[site ] DEBUG 2026/03/24 14:17:28 solar forecast: produced 41.178
[site ] DEBUG 2026/03/24 14:17:28 solar forecast: accumulated 27.053kWh, produced 41.178kWh, scale 1.522
[site ] DEBUG 2026/03/24 14:18:02 ----
[lp-1 ] ERROR 2026/03/24 14:18:13 charge power: Get "http://192.168.1.165/api/1/vitals": dial tcp 192.168.1.1xx:80: i/o timeout

What type of operating system or environment does evcc run on?

Linux

External automation

• 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

• I have verified that the issue is reproducible with the latest nightly build

Version

No response