Question 1

Where can I download Eziwan OTA files (.ota / .bin)?

Accepted Answer

Eziwan firmware images are available in the secure customer portal (portail.eziwan.com) after logging in. Each release includes a changelog, a SHA-256 sum, and a signature certificate. For automatic OTA deployment, upload the image directly from the Eziwan Fleet console—the distribution server handles the rollout to your devices.

Question 2

How does Eziwan's Zero-Touch Provisioning work?

Accepted Answer

When powered on, the Gateway automatically contacts the Eziwan bootstrap server (HTTPS/TLS 1.3) using its unique X.509 certificate, which is pre-programmed at the factory. The server identifies the device, sends it its encrypted configuration (network, VPN, Modbus polling, etc.), and the device applies the configuration and reboots. Within 5–8 minutes, the device is operational without any manual intervention on site.

Question 3

What happens if an OTA update fails?

Accepted Answer

Thanks to A/B partitioning, the old firmware remains intact on partition B throughout the update. In the event of a flashing failure, a signature verification error, or a crash during the first boot (watchdog triggered), the bootloader automatically switches to partition B (the old version). A failure notification is immediately sent to the console, via email, and via webhook. No data is lost, and the device remains operational.

Question 4

Does OTA deployment work on a limited 4G connection (< 1 Mbps)?

Accepted Answer

Yes. Delta updates (bsdiff between two versions) typically reduce the image size by 60 to 90%. A full 40 MB update becomes a 4–8 MB delta. The transfer is resumable (chunked HTTP with Range requests): if the 4G connection is lost, the download resumes where it left off. There is no minimum bandwidth requirement—the download adapts to the available speed.

Question 5

Can we schedule updates to avoid production hours?

Accepted Answer

Yes, the Eziwan Fleet console offers a cron-style scheduler: you define a maintenance window (e.g., "Saturday and Sunday between 2:00 a.m. and 4:00 a.m., local time on the device"). Deployment will only begin within this window. If the window is missed (device offline), the update will be attempted the next time the window occurs. You can also stop an update in progress in case of an emergency.

Question 6

How do I integrate OTA management into my CI/CD system?

Accepted Answer

The Eziwan Fleet REST API allows you to upload an OTA image, create a deployment, and track progress programmatically. Example: POST /api/v1/ota/images to upload, POST /api/v1/deployments to launch. Compatible with GitHub Actions, GitLab CI, and Jenkins. Integration examples are available in the developer documentation.

Question 7

Is Zero-Touch Provisioning compatible with private networks (without direct Internet access)?

Accepted Answer

Yes, for isolated environments, Eziwan offers an on-premises (private) bootstrap server: a Docker container deployed within your internal infrastructure handles provisioning without going through the Internet. The Gateway only needs to reach this internal server during its first boot. Compatible with HTTP proxies, managed VLANs, and air-gapped networks with relay.

Question 8

How many devices can be managed simultaneously using the Eziwan Fleet console?

Accepted Answer

The Fleet Eziwan console is designed to manage anywhere from a few dozen to several thousand devices. OTA deployments are distributed via a high-availability CDN to support simultaneous updates without overloading the devices. The service tiers (Starter, Pro, Enterprise) define the maximum number of managed devices—contact us for plans covering several thousand devices.

Question 9

How should we handle a rollback if an OTA update causes problems in the field?

Accepted Answer

The Eziwan OTA system includes a two-level automatic rollback mechanism. (1) Local rollback on the gateway: After each firmware update, the gateway performs a series of boot tests (5-minute watchdog). If the new version does not boot correctly or fails to establish a connection to the cloud, the previous firmware is automatically restored from the backup partition (dual-bank A/B). (2) Rollback orchestrated from the Fleet console: if you detect an issue on the first gateways in a canary deployment, you can halt the ongoing deployment and trigger a rollback to the previous version on all gateways that have already been updated. The orchestrated rollback is executed via the same secure OTA channel, without any on-site intervention. All firmware versions are retained on the platform for 12 months to allow a rollback to any previous version.

Feature	Eziwan Fleet	Traditional Solutions
Automatic rollback	Included	Manual (SSH)
A/B partitioning	Included	Often absent
Delta Update	Included	Full image only
ZTP (Zero-Touch)	Included	Manual configuration required
Phased rollout	Included	Not available
Cryptographic signature	Included	Often absent
Scheduling	Included	Often absent
REST API for Management	Included	Rare, often owned by the owner
Narrowband 4G operation	Included	Issues
Sovereign Hosting in France	Included	Cloud (U.S./Ireland)

Firmware Updates Secure OTA Updates and hands-off deployments

From power-on to operational in less than 8 minutes

Eziwan Zero-Touch Provisioning: Step by Step

Step 1 : Fabrication

4 Steps for a Secure and Reliable Firmware Update

OTA Firmware Release

Targeted Deployment by Group

Secure Download and Verification

Deployment and Automatic Rollback

Everything You Need to Manage an Industrial Park

A/B Partitioning

Delta Updates

RSA Signature + SHA-256

Maintenance Windows

Phased rollout

Comprehensive observability

Eziwan Fleet vs. Traditional OTA Solutions

Integrate OTA deployment into your CI/CD pipeline

Frequently Asked Questions About OTA Updates and ZTP

Ready to deploy your gateway fleet without manual intervention?