If OCPP is tured off remote start/stop will not work

[fekberg]

There is currently a "bug" (still being investigated by Charge Amps) that if the box has OCPP enabled (not CAPI) stopping charging when a charging session is active does not work. It is unclear if this is intentional or not.

A work-around for this is to use the RFID-endpoint instead:

• PUT /api/v4/chargepoints/{chargePointId}/connectors/{connectorId}/remotestart

• PUT /api/v4/chargepoints/{chargePointId}/connectors/{connectorId}/remotestop

This would require an RFID tag to be created, and associated with the box in the admin UI (or through the API).

It would be a great feature to add to the component to be able to use the RFID remotestart/remotestop functionality.

[mekholm]

I think I see the same. Since a while back the charger will not turn off if a car is charging when I get the switch is set to "off". Unfortunately that means that it's no longer possible to only charge the car when the electricity price is low.

[ReconOperator]

Its possible, you just have to change your automation in HA to use: remote_start -- start a charging sessions when RFID lock is enabled remote_stop -- stop charging sessions when RFID lock is enabled

And set the charger to use RFID lock and then add a RFID tag in https://my.charge.space/admin/nfcTags and use the data from that tag when making the action call.

[ReconOperator]

By the way @fekberg , isn't this feature request implemented since remote_start and remote_stop exist in the integration?

[fekberg]

@ReconOperator It is, I implemented it 😄

[ReconOperator]

@fekberg Thanks for the work! Been using it for a couple of weeks now since i got OCPP to my HALO.