FirmwareStatusNotification

FirmwareManagement CS->CSMS OCPP 2.0.1

Sent by the Charging Station to report the progress of a firmware update. Each step of the update process sends a new notification.

Quick Reference

Required Fields

status FirmwareStatusEnumType

Current firmware update status

Optional Fields

requestId integer

The requestId from the UpdateFirmware request (required if this notification is in response to an UpdateFirmware)

Example Payload

{
  "status": "Installing",
  "requestId": 1
}

Example Full Frame

[
  2,
  "msg-001",
  "FirmwareStatusNotification",
  {
    "status": "Installing",
    "requestId": 1
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

FirmwareStatusNotification reports each stage of the firmware update process. The CSMS can track the update from scheduling through download, installation, and reboot.

Status Flow

Typical successful update: Downloading → Downloaded → SignatureVerified → Installing → InstallRebooting → (reconnect) → Installed

Failed download: Downloading → DownloadFailed

Expected Response

Empty response {}.

Key Differences from OCPP 1.6J

More granular status values (14 vs 5 in 1.6J)
requestId links the notification to a specific UpdateFirmware request
SignatureVerified and InvalidSignature for firmware authentication
InstallRebooting to indicate the station is rebooting post-install

Testing Tips

Verify the full happy path notification sequence
Verify InvalidSignature when a tampered firmware is delivered
Verify the station reconnects and sends BootNotification after InstallRebooting

Common Errors

`TypeConstraintViolation`

Cause: status uses a value not in FirmwareStatusEnumType

Solution: Valid values: Downloaded, DownloadFailed, Downloading, DownloadScheduled, DownloadPaused, Idle, InstallationFailed, Installing, Installed, InstallRebooting, InstallScheduled, InstallVerificationFailed, InvalidSignature, SignatureVerified

Related Actions

UpdateFirmware Reset BootNotification