ChangeConfiguration

Core CSMS->CP

Sent by the Central System to change a configuration parameter on the Charge Point.

Quick Reference

Required Fields

key string(50)

Name of the configuration parameter

value string(500)

New value for the parameter

Example Payload

{
  "key": "HeartbeatInterval",
  "value": "300"
}

Example Full Frame

[
  2,
  "msg-001",
  "ChangeConfiguration",
  {
    "key": "HeartbeatInterval",
    "value": "300"
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

The ChangeConfiguration command allows the Central System to modify Charge Point configuration parameters remotely.

When Received

  • Adjusting operational parameters (heartbeat interval, timeouts)
  • Enabling/disabling features
  • Updating connectivity settings
  • Configuring charging behavior

Expected Response

The CP responds with:

  • status: Accepted, Rejected, RebootRequired, or NotSupported

Common Configuration Keys

  • HeartbeatInterval: Heartbeat frequency (seconds)
  • MeterValueSampleInterval: Meter values frequency (seconds)
  • ClockAlignedDataInterval: Clock-aligned sampling interval
  • ConnectionTimeOut: WebSocket connection timeout
  • AuthorizeRemoteTxRequests: Allow remote start without local authorization
  • LocalAuthorizeOffline: Allow offline authorization
  • LocalPreAuthorize: Skip authorization for local transactions

Usage Notes

  • All values are transmitted as strings (even numbers: “300” not 300)
  • Some changes require reboot (status: RebootRequired)
  • Read-only keys return NotSupported
  • Invalid values return Rejected

Best Practices

  1. Use GetConfiguration first - Verify key exists and is writable
  2. Validate values - Check constraints before sending
  3. Handle reboot - Be prepared for RebootRequired status
  4. Document changes - Log all configuration changes for audit
  5. Test carefully - Invalid settings can affect CP operation

Testing Tips

  • Test with standard keys (HeartbeatInterval)
  • Test with invalid key to verify NotSupported
  • Test with invalid value to verify Rejected
  • Test keys that require reboot
  • Test read-only keys

Common Errors

NotSupported

Cause: Configuration key doesn't exist

Solution: Use GetConfiguration to check available keys

Rejected

Cause: Value is invalid or out of range

Solution: Check parameter constraints and valid values

Related Actions

GetConfiguration