Connector 0/zero causes Exception about steve

[andle]

Apologies, Earlier I meant to say I was unable to reproduce with the other calls. I messed up the quotation on the comment.

[goekay]

in various places of the flow (where the station is sending some connector-specific message to steve) we have an optional step "if you see this connector id for the first time, insert into db".

the fact that you see this exception means that your station did not communicate with steve beforehand. possible?

This is also seen in other OCPP calls when connector zero is used.

this should not be happening. can you elaborate these calls, and the use cases etc?

[andle]

@goekay

The station had performed BootNotification, StatusNotifications, StartTransactions, etc. Is this what you mean by communication beforehand?
Subsequent SetChargingProfile.req's result in the same behavior, exception is seen.

This is also seen in other OCPP calls when connector zero is used.<

As for the other calls, I may be mistaken. I thought I had seen it in other connectorId=0 situations, but I can't currently reproduce them.

[goekay]

can you pls post some logs, for ex from StartTransaction?

[goekay]

actually the events/logs where connector 0 is used.

[andle]

If you look at the first line of the log in Additional Context, you can see the SetChargingProfile.req where connectorId:0 is used.

[goekay]

i am aware of SetChargingProfile.req with connectorId:0. i did not mean that.

i meant: can you pls post logs from other operations you mentioned (BootNotification, StatusNotifications, StartTransactions, etc.) where connector 0 is used?

[andle]

@goekay What are next steps? Will this be merged?

[goekay]

there is some discourse happening. it will be merged after the resolution of raised concerns.