Firmware management

The Firmware section is used to upload firmware files, manage firmware versions per charger model, and roll out updates to chargers.

Firmware management is available per charger model. From here, you can:

  • See your fleet's firmware status by model
  • Upload firmware files to the firmware library
  • Start a firmware rollout to selected chargers
  • Track rollout progress and per-charger update status
  • Cancel an active rollout
📌

Access to this section requires the Firmware permission.

Overview

The Firmware page has two main tabs:

  • Overview
  • Firmware library

Overview tab

The Overview tab groups chargers by hardware model.

For each model, the page shows:

  • Model
  • Brand
  • Sites
  • Chargers
  • Firmware versions currently reported in the fleet
  • Status

The model status can appear as:

  • Uniform: chargers of that model report the same firmware version
  • Fragmented: multiple firmware versions are in use
  • Updating: an active rollout is in progress
  • Scheduled: a rollout is created and waiting for its update window
  • Unknown: chargers have not yet reported a firmware version

Click Manage firmware for a model to open its detail view.

Model detail view

The model detail view shows three main areas:

  • Current firmware versions across chargers of that model
  • Active or recent rollouts
  • Start a new rollout

Current firmware versions

This section shows which firmware version is currently installed across chargers of the selected model.

You can see:

  • How many versions are present in the fleet
  • Which locations use each version
  • Which chargers have not yet reported a firmware version

Active and recent rollouts

When a rollout exists for the model, the page shows:

  • Rollout status
  • Target firmware version
  • Rollout strategy
  • Scheduled update window, if used
  • Progress across chargers
  • Per-site and per-charger update status

Per-charger statuses include:

  • Pending
  • Queued
  • Downloading
  • Downloaded
  • Installing
  • Installed
  • Download failed
  • Installation failed
  • Cancelled
  • Unknown

While a rollout is active, the status panel refreshes automatically.

Cancelling a rollout

You can cancel a rollout from the model detail view.

When a rollout is cancelled:

  • The rollout status changes to Cancelled
  • Chargers that have not finished yet are marked as cancelled where applicable

Firmware library

The Firmware library tab stores firmware files by charger model.

Select a model from the sidebar to view its firmware versions.

Each firmware version entry shows:

  • Version
  • SHA-256 checksum
  • Uploaded date
  • Uploader
  • Notes
  • How many chargers in the fleet use that version

The library also shows a fleet distribution bar for the selected model.

Uploading a firmware file

To upload a new firmware version:

  1. Open Firmware library.
  2. Select the charger model.
  3. Click Add firmware file.
  4. Enter the Version string.
  5. Select the Firmware file.
  6. Optionally add Notes.
  7. Click Upload.

The uploaded file is added to the firmware library for that charger model.

💡

Firmware files are uploaded per charger model. A rollout can only use firmware versions that belong to the selected hardware model.

Deleting a firmware version

You can delete a firmware version from the library.

A firmware version cannot be deleted while a rollout using that version is still in progress.

Starting a rollout

Rollouts are started from the selected model's detail view.

Click Start rollout to open the rollout wizard.

Step 1: Select targets

Choose:

  • The target firmware version
  • The chargers that should receive it

Chargers already using the selected version can be left out. Chargers already participating in another active rollout for that model cannot be selected.

Step 2: Rollout strategy

Choose how the rollout should proceed.

Available strategies are:

  • One per site: sites update in parallel, but only one charger at a time per site
  • Sequential: chargers update one by one across the whole fleet
  • Parallel: all selected chargers update at the same time
💡

One per site is the recommended strategy in the current interface.

Step 3: Failure handling

Choose what should happen if a charger fails during the rollout.

Options are:

  • Skip and continue
  • Halt site on first failure

With Halt site on first failure, the current site's remaining queue is cancelled if a charger on that site fails. Other sites continue.

Step 4: Update window

You can either:

  • Dispatch the rollout immediately
  • Restrict it to a update window

If you schedule a window, enter:

  • Window opens
  • Window closes

Times are evaluated in the company's timezone.

Update windows can also cross midnight, for example 22:00 to 05:00.

Chargers that are already updating when the window closes are allowed to finish. Chargers not yet reached remain queued for the next valid window.

Step 5: Review and confirm

Before the rollout is created, review:

  • Number of target chargers
  • Target firmware version
  • Rollout strategy
  • Failure handling
  • Update window
  • SHA-256 checksum

You must confirm that the firmware build is validated for the selected hardware model and region before creating the rollout.

Common questions

Can I push one firmware file to different charger models? No. Firmware files are stored per charger model, and a rollout can only use a firmware version belonging to the selected model.

Why can I not select some chargers in the rollout wizard? Chargers already in another active rollout for that model are locked and cannot be selected.

Can I schedule firmware updates at night? Yes. Use the Update window step in the rollout wizard to define a maintenance window.

Can a scheduled rollout cross midnight? Yes. A window such as 22:00 to 05:00 is supported.

What happens if a charger stops reporting update progress? If a charger stays too long in a non-final update state, it can end up marked as Unknown.

Can I remove a firmware version from the library? Yes, unless a rollout using that version is currently in progress.


Did this page help you?