> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/downloads/en/powerio-downloads/h1.m300-firmware.md).

# H1.M300

Firmware updates for H1.M300

<figure><img src="https://1006137389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0iNqm20Eubny3McJVgbJ%2Fuploads%2FoWorEnu3ZnS03eDbWlZW%2Fimage.png?alt=media&amp;token=2041ac4c-bb1f-4ae1-841d-6312f83d07f6" alt="H1.M300" width="375"><figcaption><p>H1.M300 Device</p></figcaption></figure>

### Current Version - Firmware

<details>

<summary>5.2 - Firmware - <a href="https://dl.powerio.com/downloads/powerIO-h1m300-firmware-5.2.piop" class="button primary" data-icon="arrow-down-to-line">Download</a></summary>

Release Date 18.08.2026

**Bug fixes and improvements**

* General stability improvements
* **Fix for startup after FW update**

</details>

***

### Older versions - Firmware

<details>

<summary>5.1 - Firmware</summary>

Release Date 06.08.2026

**New features and changes**

* **powerIO Orbit**: The web interface consistently uses the term powerIO Orbit instead of powerIO Portal.
* **Serial interfaces in the dashboard**: The serial interfaces are labeled Serial Port in the dashboard instead of M12 Port.

**Bug fixes**

* **Manual time setting**: Manually setting the time and adopting the browser time are now reliably written to the hardware clock. Previously, this failed without feedback.

</details>

<details>

<summary>5.0 - Firmware - <a href="https://dl.powerio.com/downloads/powerIO-h1m300-firmware-5.0.piop">Download</a></summary>

Release Date 22.07.2026

{% hint style="info" %}
First official firmware version for the H1.M300.
{% endhint %}

**New features and changes**

#### **Security**

* **Signed firmware packages**: Firmware updates (PIOP) are signed from version 5.0 and are checked on the device before installation. Packages without a valid signature are rejected.
* **HTTPS encryption**: Can be optionally enabled with automatic certificates and custom certificates.
* **Flexible access control**: HTTP, HTTPS and SSH can be configured individually.
* **API keys for external systems**: Access to the device API via individually assignable and revocable API keys, without passwords in scripts or configuration files.

#### **System**

* **64-bit platform**: Fully 64-bit (arm64) system designed for the Raspberry Pi Compute Module 5.
* **Wi-Fi dongle support**: USB Wi-Fi adapters are detected immediately and can be used to securely access the device via the mobile app or web interface. Configuration is done via the network settings in the web interface.
* **Automatic recovery**: Crashed services restart automatically, and the system continues running without intervention.

#### **Serial communication and Modbus**

* **4x RS485 usable out of the box**: Modbus and Transparent Mode are available on all four serial interfaces.
* **Optimized Modbus communication**: Interframe timing according to the Modbus specification and improved stability with parallel queries.
* **Transparent Mode**: Use serial interfaces (Serial/TCP) directly over the network.
* **Status display for serial ports**: The status of the serial interfaces is displayed in the web interface.

#### **powerIO Orbit connection (optional)**

* **powerIO Orbit connection**: Connection to powerIO Orbit with encrypted transmission.
* **powerIO Orbit device registration**: Registration of powerIO devices.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.powerio.com/hub/downloads/en/powerio-downloads/h1.m300-firmware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.