Request a firmware update on a charger
POST/chargers/:id/actions/update-firmware
Sends an OCPP UpdateFirmware command instructing the charger to download and install new firmware from a specified location.
Use Cases:
- Deploy firmware updates to fix bugs or add features
- Apply security patches and vulnerability fixes
- Update OCPP protocol version support
- Rollback to previous firmware version if needed
- Standardize firmware versions across fleet
Update Process:
- Charger receives UpdateFirmware command with download URL
- Charger downloads firmware file (may take 5-30 minutes)
- Charger validates firmware signature and compatibility
- Charger installs firmware (charger unavailable during install)
- Charger reboots with new firmware
- Charger sends FirmwareStatusNotification with progress updates
- Charger sends BootNotification with new firmware version
Parameters:
- Location: HTTP(S)/FTP URL of firmware file
- Retrieve Date: When to start download (immediate or scheduled)
- Retries (optional): Number of download retry attempts
- Retry Interval (optional): Seconds between retry attempts
Important Warnings:
- Firmware updates typically require 10-60 minutes total
- Charger unavailable for charging during update
- Failed updates may brick the charger requiring manual recovery
- Always test firmware on development chargers first
- Verify firmware file is compatible with charger hardware
Best Practices:
- Schedule updates during low-usage periods
- Stop all active sessions before updating
- Monitor FirmwareStatusNotification for progress and errors
- Keep backup of previous firmware version for rollback
- Update chargers in small batches, not entire fleet at once
- Verify firmware source and digital signature
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
Standard success response for actions
Standard error response format
Standard error response format
Standard error response format
Standard error response format
Standard error response format