Toyota 403 forbidden

[PGnl]

Describe the bug

I just started testing EVCC again following the new implementation of the Toyota integration.

While I am able to add the car and get a SoC. this is only at configuration.

When going to the menu I get the SoC it just got during the config however also errors.
vehicle soc: unexpected status: 403 (Forbidden) (ignored by estimator)

The car will however be charged.

When I disconnect the car (and typically take it for a drive) it looses the SoC and will not regain it at connecting/restarting charging.
I need to go back into config. Press validate again and restart EVCC after which it will use the value from when I validated it again.

For now that is what I am doing.

For the remainder everything is working perfectly.

Is there maybe a difference between how it gets the SoC during validate and when charging?

Note. Also checked with a separately installed Linux install rather than the HA addon.

Steps to reproduce

1.Toyota config
2.restart EVCC
3.disconnect/switch off charger (typically while taking the car for a drive)
4. Connecting the car again and start charging

Configuration details

I will upload my setting later this evening. Note that Toyota was added via EVCC rather than the yaml.

Log details

[lp-1 ] WARN 2025/02/26 14:27:54 vehicle soc: unexpected status: 403 (Forbidden) (ignored by estimator)
[lp-1 ] DEBUG 2025/02/26 14:27:54 soc estimated: 56.09% (vehicle: 46.00%)
[lp-1 ] DEBUG 2025/02/26 14:27:54 vehicle soc: 56%
[lp-1 ] DEBUG 2025/02/26 14:27:54 pv charge current: min 8A > 0A (2050W @ 1p, battery: false)
[site ] DEBUG 2025/02/26 14:27:57 ----
[lp-1 ] DEBUG 2025/02/26 14:27:57 charge power: 2365W
[site ] DEBUG 2025/02/26 14:27:57 grid power: 2052W
[site ] DEBUG 2025/02/26 14:27:57 grid currents: [-0.48 10.3 -1.27]A
[site ] DEBUG 2025/02/26 14:27:57 pv 1 power: 776W
[site ] DEBUG 2025/02/26 14:27:57 pv 2 power: 195W
[site ] DEBUG 2025/02/26 14:27:57 pv power: 970W
[site ] DEBUG 2025/02/26 14:27:57 site power: 2052W
[lp-1 ] DEBUG 2025/02/26 14:27:57 charge total import: 50.630kWh
[lp-1 ] DEBUG 2025/02/26 14:27:58 charger status: C

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

HomeAssistant Add-on

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

0.200.3

[andig]

/cc @thomasbecker

[thomasbecker]

Yeah, noticed that myself. Refreshing the access token is missing. I already implemented that, but can't test it as I installed MacOS 15.4 beta which broke all hardware virtualization. So I can't build any docker images to test it. In Integration tests it works.

@andig Want me to push the fix anyhow and untested? I mean the current implementation works only for an hour, so it can't get worse.

[thomasbecker]

@PGnl Out of curiosity and not related to the 403 issue: What Toyota Model do you have?
@andig: Created the PR: #19209

Guess it's safe to merge it as it's broken anyhow as described above.

[PGnl]

@thomasbecker
I have the full electric bz4x

[thomasbecker]

Too bad. Me too. Was hoping to see if my implementation works with other models as well. Nice car! I like mine a lot.

[PGnl]

Just got mine last Friday and still figuring out how everything works. Good to hear you like yours 😉

[PGnl]

Works like a charm for now .
Thanks @thomasbecker

[thomasbecker]

Awesome, thank you for testing it.

[PGnl]

@thomasbecker

Seems issue is back. Worked for a while though. Not sure what is happening but the error is back.

[lp-1 ] ERROR 2025/02/27 13:39:59 vehicle soc: unexpected status: 403 (Forbidden)
[lp-1 ] DEBUG 2025/02/27 13:39:59 pv charge current: min 8A > 0A (1955W @ 1p, battery: false)
[site ] DEBUG 2025/02/27 13:40:02 ----
[lp-1 ] DEBUG 2025/02/27 13:40:02 charge power: 2336W
[site ] DEBUG 2025/02/27 13:40:02 grid power: 1981W
[site ] DEBUG 2025/02/27 13:40:02 grid currents: [-0.509 10 -1.16]A
[site ] DEBUG 2025/02/27 13:40:02 pv 1 power: 838W
[site ] DEBUG 2025/02/27 13:40:02 pv 2 power: 205W
[site ] DEBUG 2025/02/27 13:40:02 pv power: 1042W
[site ] DEBUG 2025/02/27 13:40:02 site power: 1981W
[lp-1 ] DEBUG 2025/02/27 13:40:02 charge total import: 65.945kWh
[lp-1 ] DEBUG 2025/02/27 13:40:02 charger status: C
[lp-1 ] ERROR 2025/02/27 13:40:02 vehicle soc: unexpected status: 403 (Forbidden)

Now on version 200.4

[andig]

We need a trace log for toyota

[PGnl]

Trace log of Toyota

ctp-prd.toyotaconnectedeurope.io/v1/global/remote/electric/status
[toyota] TRACE 2025/02/27 17:05:49 { "status": { "messages": [ { "responseCode": "APIGW-403", "description": "Unauthorized", "detailedDescription": "jwt expired" } ] } }
[toyota] TRACE 2025/02/27 17:22:08 GET https://ctpa-oneapi.tceu-ctp-prd.toyotaconnectedeurope.io/v1/global/remote/electric/status
[toyota] TRACE 2025/02/27 17:22:08 { "status": { "messages": [ { "responseCode": "APIGW-403", "description": "Unauthorized", "detailedDescription": "jwt expired" } ] } }
[toyota] TRACE 2025/02/27 17:23:08 GET https://ctpa-oneapi.tceu-ctp-prd.toyotaconnectedeurope.io/v1/global/remote/electric/status
[toyota] TRACE 2025/02/27 17:23:08 { "status": { "messages": [ { "responseCode": "APIGW-403", "description": "Unauthorized", "detailedDescription": "jwt expired" } ] } }
[toyota] TRACE 2025/02/27 17:23:19 GET https://ctpa-oneapi.tceu-ctp-prd.toyotaconnectedeurope.io/v1/global/remote/electric/status
[toyota] TRACE 2025/02/27 17:23:19 { "status": { "messages": [ { "responseCode": "APIGW-403", "description": "Unauthorized", "detailedDescription": "jwt expired" } ] } }