NFC Keycard Info

[McFranky]

Hi folks

Is it possible to transmit the NFC Keycard ID so that you can see who started the charging station?

I use the ABB Terra Charger.

[lbbrhzn]

Yes, if your charger has NFC, it should transmit the NFC Keycard ID into the idTag field of a StartTransaction.req message. Others (like Wallbox Pulsar) do not have NFC, and use the identity of the charger instead.

You can check the debug log to see if the idTag is indeed transmitted.

The central system of the OCPP integration currently ignores the idTag, and always accepts the start of the transaction. It would not be too hard to add a sensor or attribute that displays the idTag to the user. I guess this is what you are looking for? I've created issue #356 for this.

In a future implementation we may also add support an authorization list (idTags that are allowed to start a transaction). Some chargers allow you to upload a local authorization list. This enables you to start a transaction without involving the central system.

[McFranky]

Thats great!

OK, here is my LOG:

2022-02-03 06:33:00 INFO (MainThread) [ocpp] ILET01: receive message [2, "0718116", "StatusNotification", {"connectorId": 1, "errorCode": "NoError", "info": "null", "status": "Preparing", "vendorErrorCode": "0x00"}]
2022-02-03 06:33:00 INFO (MainThread) [ocpp] ILET01: send [3,"0718116",{}]
2022-02-03 06:33:03 INFO (MainThread) [ocpp] ILET01: receive message [2, "4521300", "Authorize", {"idTag": "000000009667"}]
2022-02-03 06:33:03 INFO (MainThread) [ocpp] ILET01: send [3,"4521300",{"idTagInfo":{"status":"Accepted"}}]
2022-02-03 06:33:05 INFO (MainThread) [ocpp] ILET01: receive message [2, "0506558", "StatusNotification", {"connectorId": 1, "errorCode": "NoError", "info": "null", "status": "SuspendedEV", "vendorErrorCode": "0x00"}]

The idTag is 9667. This is the RFID-Tag Number of my Keycard.

It would be great if the idTag and idTagInfo are displayed as entities.

Greeting from Berlin
Frank

[lbbrhzn]

The idTag is now shown. The idTagIndo is not shown, since the current implementation (0.4.19) always sends accepted.
Ive created issue #370 for adding an authorization list.