Pair a charger with a Stekker account

To determine which Stekker account a charger belongs to, the user could enter a simple pairing code from the Stekker app into the CSMS, for example something like "PEN4E". If this code is then sent (once) to the Stekker API along with the other details of the charger, enough information to plan charging sessions. The CSMS could use the presence of such a code to filter which chargers messages are sent to the Stekker API.

After the pairing, subsequent messages from the charger only need to include a unique identifier of the charger.

This is what the user sees in the Stekker App

Note: If entering such a pairing code (pairing_code) is not desirable, we can agree on a different workflow to establish the connection between charger and Stekker account. As far as we can see, all alternative workflows involve more administrative work for the CPO or Stekker (or the VAR), which is why our preference is for the described principle.

Determining the max theoretical charging speed

To calculate the max theoretical charging speed we use the formula: maxPower = maxVoltage * maxAmperage * numberOfPhases. The number of phases is derived from the field powerType. If powerType is not specified, we assume it's a single-phase charger.

Important to note: when maxVoltage and maxAmperage are provided, we (re)calculate maxPower and disregard any directly provided maxPower value.

PUT/api/v1/events

Event: ChargePointDetailsNotification

Name
chargePointId
Type
string
Description
The chargePointId field contains the identifier of the charging point that is returned in other messages, such as start and stop session.
Name
pairingCode
Type
string
Description
The pairingCode field contains the code that has been manually entered (e.g. by a user) in the CSMS. This field becomes obsolete if an alternative method for linking is chosen.
Name
geometry
Type
string
Description
The geometry field (optional) is used to automatically make charging sessions smart if the GPS location of the EV matches the charging point. Users can also enter or adjust this information themselves in the Stekker app.

Request

curl --location --request PUT 'https://api.stekker.app/api/v1/events' \
--header 'Authorization: Token provided-secret' \
--header 'Content-Type: application/json' \
--data-raw '{
 "event": "ChargePointDetailsNotification",
 "chargePointId": 6,
 "pairingCode": "DWXYZ",
 "name": "Stekker.app - Jankees",
 "ocppIdentity": "SOLAR_0213",
 "locationId": 3,
 "country": "NLD",
 "geometry": {
   "type": "Point",
   "coordinates": [52.583, 5.365]
 },
 "connectors": [
   {
     "connectorId": "1",
     "physicalReference": "NLSTKE000002",
     "maxPower": 22080,
     "maxVoltage": 230,
     "maxAmperage": 32,
     "powerType": "AC_3_PHASE"
    },
   }
 ]
}
'