Pair EVSE using OCPI format

In OCPI 2.2 the charger is identified by an EVSE object and consists of a 2-tier model.

Example of EVSE pairing using code issued by the CPO

Request from Jedlix to CPO

POST /v1/cpo/ocpi2.2/pair
Content-Type: application/json
Authorization: Bearer <Your_Auth_Token>

{
  "code": "362821"
}

Response from CPO to Jedlix

1. 200: OK - Verification successful

   JSON

   {
   	"evse":{
   	  "uid": "3256",
   	  "evse_id": "BE*BEC*E041503001",
   	  "capabilities": [
   	    "CHARGING_PROFILE_CAPABLE"
   	  ],
   	  "connectors": [{
   	    "id": "1",
   	    "power_type": "AC_3_PHASE",
   	    "max_voltage": 220,
   	    "max_amperage": 16
   	  }, {
   	    "id": "2",
   	    "power_type": "AC_3_PHASE",
   	    "max_voltage": 220,
   	    "max_amperage": 16,
   	    }]
   	  }
   }
   

• 404: Not found - Incorrect pairing code
  JSON

  {
    "message": "Incorrect Code, please check the code and try again.",
  }
  

Example of EVSE pairing using code issued by the SCSP

Request from CPO to Jedlix

POST /v1/scsp/ocpi2.2/pair
Content-Type: application/json
Authorization: Bearer <Your_Auth_Token>

{
  "code": "362821",
  "evse": {
    "uid": "3256",
    "evse_id": "BE*BEC*E041503001",
    "capabilities": ["CHARGING_PROFILE_CAPABLE"],
    "connectors": [
      {
        "id": "1",
        "power_type": "AC_3_PHASE",
        "max_voltage": 220,
        "max_amperage": 16
      },
      {
        "id": "2",
        "power_type": "AC_3_PHASE",
        "max_voltage": 220,
        "max_amperage": 16
      }
    ]
  }
}

• Jedlix receives the Pairing Code and the EVSE object and conducts the following verifications:
  • Cross-references the received Pairing Code with the list of valid Pairing Codes to confirm the pairing.
  • Checks whether the uid in the EVSE object to ensure it doesn’t already exist within the Jedlix platform.
• Depending on Jedlix’s synchronous response:
  • A success message is displayed on the CPO’s user interface, confirming successful pairing.
  • An error message is displayed on the CPO’s user interface if the Pairing Code is incorrect, advising the user to verify and try again.
  • An error message is displayed on the CPO’s user interface if the charger is already paired to another account, informing the user of the existing pairing.

Responses from CPO to Jedlix

• 200: OK - Verification successful
• 404: Not Found - Verification failed due to incorrect activation code
  JSON

  { 
  	"message": "Incorrect or expired code, please check the code and try again."
  }
  

• 409: Conflict - Verification failed as UID already exists in Jedlix platform
  JSON

  {
    "message": "This charger is already paired to another account."
  }