High Level Process
- Select the Charge Station to update from the Charge Station list. Use available filters (Firmware, Model, Connection status, etc.) to refine your selection
- Review the selection and check for validation issues
- Enter target URL and settings
- Start update
- Monitor and track the update progress in the Charge Station data table
A single Charge Station update can be initiated from the Charge Station Details page. After validation (Step 2), the process follows the same steps as a batch update.

Firmware update basics
OCPP
The firmware update process is based on OCPP specifications (currently version 1.6 only). Here are the fields sent to a Charge Station:
- LocationUrl - Target URL (typically FTP) for downloading the firmware
- Retries (optional) - Specifies how many attempts the Charge Point should make to download the firmware before failing
- retryInterval (optional) - The time in seconds to wait between retry attempts
- retrieveDate - Specifies when the Charge Point should retrieve the new firmware. This is typically set to "now" to avoid issues with future dates
Sending Firmware update request
Once the firmware update is initiated, the GreenFlux backend sends the update request to the charge station immediately.
The next step depends on the Charging Station: Charging Station dependent: OCPP: When a Charging Station receives an UpdateFirmware request, it must send a confirmation. The Charge Point should then begin retrieving the firmware as soon as possible after the retrieve-date.
Note
- Charge Station responses to UpdateFirmware requests are not specified by OCPP. As a result, GreenFlux may or may not receive a response, and response types can vary. While all Charge Stations are tested during integration to verify receipt of the Updated status, intermediate statuses remain optional.
- There are no retries from the GreenFlux side—it operates as a "fire and forget" system
Update behavior
Once the Charge Station has downloaded the firmware, it should begin installation immediately. However, most charge stations wait until all EVSEs (charging points) are inactive and only start the installation when these become available. This behavior can vary by charge station model, so CPOs should verify the specific update process.
Most charge stations require a reboot to complete the firmware installation.
Process Details and Notes
Firmware Validation
GreenFlux will indicate several potential attention points, but will not perform hard validation:
- Number of Charge Stations - Currently, there is no maximum limit on charge stations. However, please verify that the firmware update server can handle simultaneous downloads from multiple stations.
- Manufacturers - We recommend selecting only a single manufacturer.
- Model - Please verify that all selected models support the new firmware.
- Offline - Offline chargers will not receive new firmware. There are no retries or queuing mechanisms.
- Active Session - Please verify whether selected Charge Stations will interrupt ongoing charging sessions, and consider the potential impacts.
- Syncing - We recommend waiting until Charge Stations complete their syncing process before performing firmware updates.
- FW Update in Progress - Please check if selected Charge Stations already have a firmware update in progress. The behavior of Charge Stations receiving multiple firmware update requests is unknown.
Firmware States
The Charge Station can report several potential states during the update process, though not all stations will report every state or follow the same sequence.
For simplicity, GreenFlux groups these states into four main categories:
- Original Firmware - GreenFlux has no logs of past firmware updates
- Processing - A firmware update is currently in progress
- Failed - The firmware update was unsuccessful
- Updated - The firmware update completed successfully
State | GreenFlux grouped State | Origin | Description |
Original Firmware* | original firmware | GreenFux | "This Charge Station has never been updated through the EV Portal." |
Command Sent | processing | GreenFux | "COMMAND SENT: The update request was sent to the Charge Station." |
Command Declined | failed | GreenFux | "COMMAND DECLINED: The update was declined by the Charge Station." |
Downloading | processing | OCPP | "DOWNLOADING: The firmware is being downloaded by the Charge Station." |
Downloaded | processing | OCPP | "DOWNLOADED: The Charge Station has finished downloading the update and will start the update soon." |
Installing | processing | OCPP | "INSTALLING: The Charge Station is updating its configuration." |
Time Out | failed | OCPP | "TIME OUT: The update request timed-out after 2 retries." |
DownloadFailed | failed | OCPP | "DOWNLOAD FAILED: The firmware file could not be downloaded after 2 retries." |
InstallationFailed | failed | OCPP | "INSTALLATION FAILED: The Charge Station failed to update its configuration after 2 retries." |
Installed | updated | OCPP | "INSTALLED: The Charge Station finished updating the configuration." |
You can view the current firmware state in the charger overview by selecting the 'Last Known FW State' column.

Full information can be viewed in the diagnostics page of the Charge Station
Viewing a Batch of Firmware updates
The Charge Station table contains two fields for monitoring batch updates. While there isn't a formal concept of a "batch," you can group updates by their date-time range.
In the column selection, please select 'Last Know FW Stat' and 'Last FW Update'

The 'Last FW Update' field shows the date and time when the firmware update was initiated. All charge stations in the same batch will display identical timestamps.
Retry Failed Firmware Updates
It is recommended to filter charge stations by firmware state and batch/date-time. There is no option to retry using previously used settings. Instead, it is necessary to initiate the process from the start and select firmware. The last used firmware update settings can be obtained from the firmware status and Diagnostics.
Secure Firmware Updates
OCPP 1.6 and later versions, particularly OCPP 2.0 and above, include specifications for secure firmware updates.
Currently, GreenFlux does not offer this security feature. However, it may be implemented during the OCPP 2.0 development phase, at which point this process will be updated.
