start_charging doesn't work with whitelisted charger (RFID-only auth) — need ability to specify token/badge, and it leaves charger in a stuck state blocking physical badge

[Daviddepaepe]

Pressing button.start_charging_1 in Home Assistant does not actually start a charging session (no real power delivery), and it also puts the charger into a state that then blocks a subsequent physical RFID badge scan with an error (red LED on the charger). Pressing button.stop_charging_1 clears this state and a badge scan works normally again afterward.

Steps to reproduce
Plug in the vehicle (cable connected, IEC state transitions to C2)
In Home Assistant, press Start charging 1
Observe: chargingState briefly flickers STOPPED → status:CHARGING → status:CHARGING_FINISHED → CABLE_CONNECTED within ~200ms (log below) — no actual charging occurs
Badge the RFID card physically on the charger
Result: charger shows a red light / error, badge is rejected
In Home Assistant, press Stop charging 1
Badge the RFID card again
Result: badge is accepted normally, session starts as expected
Expected behavior
start_charging should be able to actually start a real session on a whitelisted/RFID-restricted charger, and should not leave the charger in a state that blocks a subsequent physical badge.

Request — please let us specify which badge/token authorizes the remote start
My charger requires RFID authorization for every session (whitelisting enabled). I believe start_charging currently calls the Dashboard API without specifying which registered token authorizes the session, which is why the charger rejects it — and apparently leaves it in an inconsistent state in the process.

What I'd like: the ability to pass a token_id (or similarly named parameter) when calling start, e.g.:

service: smappee_ev.start_charging
data:
token_id: "046C914ACF1E80" # alias "Private charges"
This would let start_charging authorize the session exactly as if I had physically badged with that card, using one of the tokens already registered in my Whitelisting. If the Smappee Dashboard API's remote-start endpoint accepts a chargingTokenId (or equivalent) parameter, exposing it here would fix the root cause — the HA button would become genuinely functional instead of a no-op that also breaks physical badging.

Debug log excerpt (MQTT RX, custom_components.smappee_ev.mqtt_gateway, debug level)
18:43:27.310 property/chargingstate: {"available":true,"percentageLimit":0,"chargingState":"STOPPED","chargingMode":"NORMAL","optimizationStrategy":"NONE","iecStatus":{"current":"C2"},"status":{"current":"CHARGING","stoppedByCloud":false,"errors":[]}}
18:43:27.322 property/chargingstate: {"available":true,"percentageLimit":0,"chargingState":"STOPPED","chargingMode":"NORMAL","optimizationStrategy":"NONE","iecStatus":{"previous":"B2","current":"C2"},"status":{"previous":"CHARGING_FINISHED","current":"CHARGING","stoppedByCloud":false,"errors":[]}}
18:43:27.497 property/chargingstate: {"available":true,"percentageLimit":0,"chargingState":"STOPPED","chargingMode":"NORMAL","optimizationStrategy":"NONE","iecStatus":{"previous":"C2","current":"B1"},"status":{"previous":"CHARGING","current":"CABLE_CONNECTED","stoppedByCloud":false,"errors":[]}}

[geertmeersman]

Hi @Daviddepaepe , this is a feature the Smappee API doesn't support (I whish it would, as I need it too).
So perhaps you can send Smappee an email with the feature request?

[geertmeersman]

If you would see the feature on the smappee app/website, please let us know

[myny-git]

I agree, I also did not see anything like that in de Smappee dashboard. Unfortunately

[PFuHu]

I think this is due to the fact that the smappee charger always does a quick check when you connect the cable AND after you have badged. This is a check to see at what speed the car can charge (I will call it 'smappeecheck')

But I found out in the past that (I use EVCC) if you have already set it to charging, this 'smappeecheck' happens before you badge. This means he (very shortly) tries charging before the car is authenticated, so the charger gives an error (red light).

I will quote here under an earlier message from an earlier 'issue': is this the problem you are facing?

`When the car has been disconnected for a while, EVCC switches 'Connector EVCC 1 charging' on. If the car is not authenticated (by holding the batch near the charger), it will block and you have to disconnect and reconnect the car. When disconnecting/reconnecting, I only disconnect the car for a few seconds which means 'connector EVCC 1 charging' stays activated.

So it really seems to be the problem when 'Connector EVCC 1 charging' gets activated while the car is not yet authenticated to the charger (which is not a problem if you choose not to authenticate the car).

It also explains why sometimes I have the problem and sometimes not. If the car is not scheduled to charge, EVCC does not change the 'connector EVCC 1 charging' and it works without disconnecting/reconnecting.

/edit: already made a workaround through 2 automations: Home Assistant switches EVCC to 'OFF' through a rest command when the cable is disconnected and sets it back to 'PV' about 1 minute after the cable is connected.`