NexBlue AutoCharge Integration Guide

Implement vehicle registration, automatic authorization and transaction association in your CPMS using NexBlue chargers.

ProtocolOCPP 1.6
Vehicle identityMAC address
Configuration keyAutoChargeEnabled
Supported models
SDU

Edge 2 · Edge Max · Point 2

MDU

Delta · Delta Max

1. Compatibility

1.1 Charger support

Before offering AutoCharge on a charger, send GetConfiguration to retrieve its supported configuration keys. An empty key array requests all supported keys.

CPMS → Charger · GetConfiguration.req
[
  2,
  "ac-config-001",
  "GetConfiguration",
  {
    "key": []
  }
]

Check whether AutoChargeEnabled is present in configurationKey.

Charger → CPMS · GetConfiguration.conf · response excerpt
[
  3,
  "ac-config-001",
  {
    "configurationKey": [
      {
        "key": "AutoChargeEnabled",
        "readonly": false,
        "value": "false"
      }
    ],
    "unknownKey": []
  }
]
Query result Interpretation
Key returned with value = "true" AutoCharge is supported and enabled.
Key returned with value = "false" AutoCharge is supported but disabled.
Key absent from the full list, or listed in unknownKey AutoCharge is not supported by the current charger firmware.

You can also query the key directly with {"key":["AutoChargeEnabled"]}. A failed or timed-out query does not establish support.

1.2 Vehicle compatibility

Charger capability and vehicle compatibility are separate checks. A compatible vehicle must provide a readable, stable and unique MAC address.

During integration testing:

  • Verify that your CPMS receives Authorize with idTag = VID:<MAC> when the vehicle is connected.
  • Complete registration and repeat plug-in sessions. Check that the VID remains consistent and automatic authorization succeeds.
  • Record the vehicle model and software version with the test results. Exclude vehicles known to use randomized or shared identifiers.

Third-party vehicle lists are screening references. Support on another charging network does not establish compatibility with NexBlue AC chargers. Revalidate affected vehicles if a software update changes identification or charging behaviour.

For vehicles without verified identification, keep your existing authorization methods available.

2. Configuration

OCPP configuration key Type Value
AutoChargeEnabled Boolean true: enable AutoCharge.
false: disable AutoCharge.

After confirming charger support, send ChangeConfiguration with AutoChargeEnabled set to "true" to enable the feature, or "false" to disable it. Configuration values are transmitted as strings.

Recognize vehicle identifiers in incoming Authorize.req.idTag values by the following format:

VID:<MAC>

The example MAC 00155D0665D6 becomes VID:00155D0665D6.

3. Vehicle registration

Implement the registration interface, user confirmation and VID-to-account binding in your CPMS. The charger supplies the vehicle identifier.

  1. Provide a registration flow for an authenticated user and prompt them to connect the vehicle.
  2. When the charger enters Preparing, expect an Authorize request containing the vehicle’s VID.
Charger → CPMS · Authorize.req
[
  2,
  "ac-auth-001",
  "Authorize",
  {
    "idTag": "VID:00155D0665D6"
  }
]
  1. Look up the VID. For an unregistered vehicle, return Invalid or Blocked.
  2. After the user confirms registration, bind the VID to the account and send RemoteStartTransaction.
  3. Process the charger’s StartTransaction request and return the transactionId in StartTransaction.conf.
  4. Handle the subsequent DataTransfer message to associate the vehicle with the transaction, as defined in section 5.

4. Automatic authorization

For subsequent plug-in sessions, handle incoming Authorize requests as follows:

01

Read the vehicle identifier from idTag = VID:<MAC>.

02

Look up the vehicle’s account binding and check its authorization status.

03

Return Accepted for an authorized vehicle. Return Invalid for an unknown VID or Blocked for a blocked registration.

04

When the charger sends StartTransaction, process the request and return the transaction identifier.

Keep vehicle identification separate from authorization. Receiving a VID does not authorize the vehicle; your CPMS decides whether the associated account may charge.

5. Transaction metadata

After your CPMS returns StartTransaction.conf, expect the following NexBlue DataTransfer message linking the vehicle MAC address to the transaction.

Charger → CPMS · DataTransfer.req
[
  2,
  "ac-data-001",
  "DataTransfer",
  {
    "vendorId": "com.nexblue.autocharge/v1",
    "messageId": "VID",
    "data": "{\"VID\":\"00155D0665D6\",\"TransactionID\":\"111111111\"}"
  }
]
Field Value / format
vendorId com.nexblue.autocharge/v1
messageId VID
data JSON-encoded string containing VID and TransactionID.
data.VID Vehicle MAC address without the VID: prefix.
data.TransactionID Transaction identifier returned in StartTransaction.conf, represented as a string.

Decode data as JSON, locate the transaction using TransactionID, and associate it with VID. Field names are case-sensitive; VID contains the MAC address without the VID: prefix.