Firmware changelog and release policy

Firmware changelog and release policy#

Distribution channels:#

When updating many chargers, ensure you use an adequate risk-mitigation strategy to prevent large-scale issues and downtime. See Risk mitigation strategy.

  1. Updates and release notes are published to the public changelog, from where you can download the firmware.

    • Additionally, if a OTA download certificate for azure blob store has been provisioned, or the charger is running plain http, links are provided that may be given directly to the charger to update it.

    • Firmware updates files are considered public information, feel free to re-host them.

For critical security fixes, amina will make best-effort contact with affected customers to ensure they are informed of the security issue and fix.

Risk mitigation strategy#

amina performs best-effort testing on all firmware before release, focusing especially on ensuring chargers do not go permanently offline, or become “un-updatable” (bricked). But in practice it is difficult to test all possible combinations of settings, with all combinations of back-ends. Therefore, we urge you to employ an adequate risk-mitigation strategy when deploying updates to fleets of chargers. An example of this is performing staggered rollouts.

(firmware-changelog=)

Firmware Changelog#

This lists all the public releases of the FW for amina OCPP charging stations.

  • All public releases are avaliable as OTA updates and follows the semantic versioning scheme (releases including minor and patch increases are always backwards compatible)

  • Only the latest firmware version is available for download

Latest FW OTA Update#

Instructions#

  1. Send an UpdateFirmare.req OCPP message to the charge point with the appropriate link in the location field

    1. Charge points configured for LTE or Ethernet only support OTA updates over HTTPS, and the update file must therefore be provided through an HTTPS link

    2. Charge points configured for Wi-Fi support OTA updates over either HTTP or HTTPS depending on whether the configured CSMS endpoint is using TLS or not. The update file must be provided using the same security as the CSMS endpoint, i.e. if the CSMS endpoint starts with wss:// an HTTPS link must be used, and if the CSMS endpoint starts with ws:// an HTTP link must be used

    3. We recommend using the links we provide below directly. However, it’s also possible to download the files and host them elsewhere. In the case where the update file is hosted elsewhere and the charge point is provisioned for LTE, Ethernet or Wi-Fi TLS (i.e. OTA updates are downloaded over HTTPS) the charge point must also have the appropriate certificate provisioned to be able to download the file

  2. We recommend updating charge points to the latest firmware version provided in the link below to ensure that they benefit from the most recent features, stability enhancements, security updates, and bug fixes. We also recommend deploying updates using a “rolling update” approach. This allows issues to be identified early before impacting a large number of chargers

Limitations#

  1. Chargers running FW with a major versions of 3 cannot be updated to FW with major version 4 (a migration is planned)

amina C#

4.x.x#

3.x.x#

amina M#

C 4.2.106 and M 4.2.106 (2026-03-25)#

Features#

Improvements#

  • Grid detection.

C 4.2.85, C 3.5.54, and M 4.2.86 (2026-02-27)#

Features#

Improvements#

  • Fix WiFi potentially not connecting if eSIM is blocked or LTE signal is poor

  • Fix bug keeping charger in preparing even when no car is connected, untill a hard reset.

  • Filesystem stability improvements

4.2.61 and 4.2.63 (2026-01-23)#

Features#

  • Wi-Fi TLS

  • Add support for permanently switching from LTE to Wi-Fi TLS

  • StatusNotification can now report the invalid grid type error

Improvements#

  • Wi-Fi reliability

4.2.34 (2025-12-05)#

Features#

Improvements#

  • NFC reliability and detection

  • OCPP transaction handling

4.2.17 (2025-11-17)#

Features#

  • amina M release

  • Support OCPP-J 1.6 AuthorizationKey

Improvements#

  • Wi-Fi OTA download stability

4.0.17 and 4.0.19 (2025-10-08)#

Features#

  • Compliant with EN18031-1

Improvements#

  • Improve network stability

  • Fix OCPP connection issues when using LTE in certain geographical areas

  • Fix incorrect reporting of InstallationFailed instead of DownloadFailed in FirmwareStatusNotification when a OTA update download fails

3.5.2 (2025-12-09)#

Features#

  • Support OCPP-J 1.6 AuthorizationKey

Improvements#

  • NFC reliability and detection

  • OCPP transaction handling

  • Wi-Fi OTA download stability

  • Improve network stability

  • Fix OCPP connection issues when using LTE in certain geographical areas

  • Fix incorrect reporting of InstallationFailed instead of DownloadFailed in FirmwareStatusNotification when a OTA update download fails

Additional Comments#

  • Not yet recommended for use on charge points configured with Wi-Fi

3.3.1 (2025-07-02)#

Features#

Improvements#

  • Improve network stability

  • Fix OCPP connection issue with some Azure based CSMS endpoints

3.0.96 (2025-05-16)#

Features#

  • Set CSMS endpoint URL remotely

Improvements#

  • Improve overall stability

  • Improve reading of NFC tags

3.0.82 (2025-04-29)#

Features#

  • Add OCPP 1.6j over Wi-Fi support (only over HTTP)

Improvements#

  • Improve overall stability

3.0.35 (2025-02-19)#

Features#

  • Add OCPP 1.6j support over LTE (only over HTTPS)

Improvements#

Contents