RFID tokens are used as authorization to start and stop charging sessions. Tap the token on the charger to start or stop a charging session. It will also identify the users via the RFID, which will show up in reports.
Authorization is set up in two ways.
- Easee portal or app
- CPO, or backend
Authorization using the Easee portal or app
For RFID token authorization through the Easee cloud, the token must be added to the cloud.
To add the RFID, see one of the following methods:
- Adding an Easee Key (RFID keytag) from the Easee app
- How do I add an Easee Key (RFID keytag) to my profile?
You do not need to use both. Using one method will add the token to both app and portal.
Authorization using CPO
When the authorization will be done by the CPO, the RFID token must be added to the CPO's backend.
In these cases, the charging sessions are validated and started by the backend, not the cloud, and this backend will verify and send the authorization message to start the charging session.
There are many possible responses from the backend. These include:
- Accepted. The authorization is accepted by the CPO and the charging session starts
- Rejected. The authorization was rejected by the CPO and the charging session will not start. The charger will show a red LED stripe and will return to the state "Authorization required"
- No Response. If the CPO does not respond for any reason, the authorization request will time out. The charger response will depend on the LocalAuthorizeOfflineEnabled setting:
- LocalAuthorizeOfflineEnabled=FALSE - Charging session will not start
- LocalAuthorizeOfflineEnabled=TRUE - Charging session will start without CPO authorization