When setting evse 0 to unavailable and evse 1 to available and start a transaction on connector 1, it is accepted.

EVerest / libocpp

C++ implementation of the Open Charge Point Protocol

Apache License 2.0

88 stars 48 forks source link

When setting evse 0 to unavailable and evse 1 to available and start a transaction on connector 1, it is accepted. #812

Open maaikez opened 2 days ago

maaikez commented 2 days ago

OCPP Version

OCPP1.6

Describe the bug

Set evse 0 to unavailable. This will set all evse's to unavailable.
Set evse 1 to available. evse 0 is still unavailable. This will change evse 1 to available.
Start a charging session on evse 1. This will work.

After setting evse 0 to unavailable, it should no be possible to set the 'real' evse's to available and start a charging session on them as long as evse 0 is still unavailable.

To Reproduce

No response

Anything else?

No response

Pietfried commented 2 days ago

After setting evse 0 to unavailable, it should no be possible to set the 'real' evse's to available and start a charging session on them as long as evse 0 is still unavailable.

Can you point to the requirement from the OCPP1.6 spec that states this?

maaikez commented 2 days ago

Good one, the 'test partner' at Plugfest assumed this and it also seemed logical to me and I also discussed it with @hikinggrass . But I did not (yet) look in the spec if this is expected behavior.