Back to siteGetting started and documentation center

Install HelioPulse your way.

Choose HelioPulse OS, Docker or Home Assistant, follow the steps and connect your first device. Then learn how drivers work to extend the platform.

Based on HelioPulse OS 1.23.24 Instructions aligned with the repository
Installation options

Choose how to run HelioPulse.

The same local panel, packaged three ways. Pick the one that fits the hardware you already have.

What do you have?

HelioPulse OS

Complete appliance for Raspberry Pi

Best for a dedicated installation: flash the image and finish setup from your phone.

Hardware
Raspberry Pi 4 or 5 · SSD or microSD
Setup
Guided captive portal, no SSH
Updates
Signed updates from the panel
View steps

Docker

Container for your server

For a mini-PC, NAS or server you already run. Same core, with data in a persistent volume.

Hardware
Linux amd64 or arm64 with Docker
Setup
One docker run or a Compose file
Updates
Pull the new image and recreate
View steps
Beta

Home Assistant

App inside Home Assistant OS

If your home already runs on Home Assistant: HelioPulse lives in the sidebar and publishes sensors over MQTT.

Hardware
Home Assistant OS · aarch64 or amd64
Setup
Home Assistant admin sign-in, no extra account
Updates
From the Home Assistant App store
View steps
Installation method

Only the steps for the method you choose are shown. You can switch at any time.

01
HelioPulse OS

Install HelioPulse OS on a Raspberry Pi.

HelioPulse OS is a ready-to-use Linux image for Raspberry Pi: system, panel and updates in a single installation designed for local energy monitoring.

Raspberry Pi 4 or 5

Pi 4 with 4 GB or Pi 5 with 4/8 GB.

Storage

128 GB USB 3.0 SSD recommended or High Endurance microSD.

Communication

USB–RS485 adapter with galvanic isolation.

  1. 1

    Download the stable release

    Get the image and review the release notes from the public releases repository.

  2. 2

    Flash the image

    Use Raspberry Pi Imager or an equivalent tool. Select the downloaded file and the destination SSD or microSD.

  3. 3

    Connect and power on

    Connect storage, network, USB–RS485 adapter and the official power supply suitable for your Raspberry Pi.

Work with the system powered down

Wire RS485 according to the manufacturer's manual. Do not handle energized inverter connections.

Next: first boot
02HelioPulse OS · first boot

Configure from your browser.

On first boot the appliance opens a captive portal from your browser: connect Wi-Fi, create your administrator and finish. No SSH, no cables to your computer.

Local networkLocate the Raspberry Pi
Initial accountCreate secure credentials
First deviceDriver, port and slave ID
  1. 1

    Insert the card and power on

    Put the flashed microSD into the Raspberry Pi and connect the power. The first boot expands the system and starts HelioPulse; give it a minute.

  2. 2

    Join the HelioPulse network

    From your phone or laptop, connect to the open HelioPulse-XXXX Wi-Fi network (no password) the device creates. Then open your browser and go to http://heliopulse.setup:8090 to reach the setup portal. On some phones the portal opens automatically; if not, just type that address.

  3. 3

    Connect to the Internet

    Pick your home Wi-Fi and enter its password, or choose to continue with a network cable. The signal strength helps you find the right network.

  4. 4

    Create your administrator

    Set the username and password (at least 8 characters) you will use to sign in to the panel. Keep them safe: this is your administrator account.

  5. 5

    Optional: enable remote access

    If your device supports it, pick a name to reach the panel securely over the Internet. Local access always keeps working, so you can skip this step.

  6. 6

    Ready to use

    The portal confirms setup is complete. The device is now on your Wi-Fi: reconnect to your usual network and open the panel at http://heliopulse.local:8080 with the account you created. The HelioPulse-XXXX network disappears since it is no longer needed.

1. Connect to the Internet

Pick your Wi-Fi network (or continue with a network cable).

2. Create your administrator

Set the credentials you will use to sign in to the panel.

3. Ready to use

Reconnect to your usual network and open the panel address shown.

Designed for phone and laptop

The portal is a responsive, guided flow with a progress bar and light/dark themes. To open it, join the HelioPulse-XXXX Wi-Fi and go to http://heliopulse.setup:8090 in your browser. No app, no SSH and no cables to your computer.

Compare installation methods
05How it works

A local, modular platform.

Each device has an independent collector. A failure or restart in one inverter does not interrupt telemetry from the others.

01

Device

The inverter or BMS exposes data through its protocol.

02

Driver

Describes protocol, registers, scales and metrics.

03

Collector

Reads each device in an isolated, controllable process.

04

Panel

Consolidates telemetry, history, alarms and forecast.

06Drivers

The translator between your device and HelioPulse.

A driver is a declarative JSON file. It defines how to communicate over Modbus RTU and convert manufacturer registers into common HelioPulse metrics.

No executable code

The package describes data; it does not install arbitrary binaries on the system.

Validation before saving

The backend checks structure, protocol and registers before accepting the file.

Reusable

The same driver can be used with several compatible devices.

07Create a driver

Start with the Modbus map.

You need the manufacturer's protocol manual and verified readings from a real device. The minimum schema requires an identifier, modbus_rtu protocol and at least one group with one register.

my-inverter-modbus.json
{
  "id": "my-inverter-modbus",
  "name": "My inverter",
  "manufacturer": "Manufacturer",
  "models": ["Model A"],
  "protocol": {
    "type": "modbus_rtu",
    "baud_rate": 9600,
    "slave_id": 1
  },
  "register_groups": [{
    "name": "battery",
    "interval": "5s",
    "registers": [{
      "address": 256,
      "name": "battery_soc",
      "metric": "battery.soc_pct",
      "unit": "%",
      "scale": 1,
      "signed": false
    }]
  }]
}

Before publishing

  • Use a stable, safe id for the file name.
  • Confirm baud rate, parity, stop bits and slave ID.
  • Verify address, sign, scale and unit for every register.
  • Compare power and energy with the device's physical panel.
  • Test disconnections and out-of-range values.
08Load and connect

Activate it without SSH.

Step 1

Upload the JSON

In Equipment → Drivers, select the file. HelioPulse validates the schema before saving it.

Step 2

Register the device

Set a device ID, driver, persistent by-id port and a slave ID between 1 and 247.

Step 3

Start the collector

Start or restart only that device and confirm that telemetry becomes active.

Controlled replacement

Uploading another file with the same ID updates the driver. Restart associated devices to apply the new definition.

09What HelioPulse has today

A local energy platform you can use now.

The current product combines live monitoring, local history, device management and safe operations on the Raspberry Pi.

Available today

Local-first monitoring

Keep telemetry and history on the appliance and continue operating on your local network without Internet.

Live telemetry with quality

See solar, consumption, battery, grid and device connection state through live WebSocket updates.

Historical analysis

Explore production, consumption, SOC, temperatures and phases from today to a custom range or one year.

Validated JSON drivers

Load, create and reuse declarative Modbus drivers without rewriting the panel.

Multi-device operations

Manage independent local and wireless ESP32 collectors, stable serial ports, device state and start/stop/restart actions.

Visual flow automation

A node editor for automations: device sources, conditions/decisions/switch, timed and sustained waits, and safe actions. Simulate before publishing; versions are immutable.

Live execution log

See recent runs of each flow, per-node states and a console of events scoped to the selected run — without opening the editor.

Alarms and event timeline

Follow alarm transitions and open an alarm to see what triggered it (metric, value and threshold); audit connectivity, configuration and collector events.

Daily and weekly reports

Daily and weekly reports lead with metrics and findings; optional local AI adds analysis, clearly labelled and never mixed with the measured data.

Health, backups and recovery

Inspect Raspberry resources, connectivity and diagnosis, then create backups and recover locally.

Guided onboarding

A first-run walkthrough spotlights each section, plus a getting-started guide to register your first driver and device.

Responsive, multilingual UI

Use the panel on desktop or mobile with nine languages and light/dark themes.

Optional and advanced

Solar forecast

Compare expected and produced solar energy after configuring the PV array.

BMS over Modbus RTU

Register a compatible BMS as its own device and inspect cells, balancing, SOC, SOH, temperatures and cycles.

Mock mode

Generate synthetic telemetry from a driver to validate the UI without hardware.

Local AI for reports

Optionally download and activate a local model; deterministic reports remain available without it.

Connected-home integrations

MQTT/Home Assistant, SmartThings and Kasa actions are available under their configuration and compatibility requirements.

Remote access and app OTA

Optional outbound tunnel access and signed application updates depend on configuration and connectivity.

Roadmap

Cloud sync

Not part of the current local workflow.

Driver marketplace

Manual driver loading exists today; a public marketplace remains future work.

Broader hardware coverage

Native JK RS485 support is already available; more CAN/BLE models and real EV charger mappings still require development and testing.

Unattended energy control

Manual device settings and energy-control bindings exist; unattended execution still requires safe policies and further validation.

Full OS A/B rollback

Application OTA is available separately; full operating-system A/B rollback remains future work.

10Published releases and next steps

What we shipped. What remains.

Browse the published stable versions and the work still being considered. Each release links to its official notes; pending work has no promised release date.

Published stable versions 104

Application releases (OTA). Bootable OS images and Docker images are published separately; an app version does not imply that an OS image exists for it.

  1. v1.18.3

    Growatt telemetry corrections and translated system output.

    Official release notes
  2. v1.18.2

    Kasa Cloud integration: encrypted credentials, discovery and verified on/off actions in flows.

    Official release notes
  3. v1.18.1

    Translation improvements across the panel, reports, events and energy-plan explanations.

    Official release notes
  4. v1.18.0

    Docker runtime, host hardware view and history aligned with the site's local midnight.

    Official release notes
  5. v1.17.72

    Security and dependency updates for the application and build tools.

    Official release notes
  6. v1.17.71

    Translation improvements across the panel, reports, events and energy-plan explanations.

    Official release notes
  7. v1.17.70

    Additional Growatt drivers and compatibility metadata.

    Official release notes
  8. v1.17.69

    Corrections to solar-forecast time buckets and batch readings.

    Official release notes

Work still to consider

These are remaining directions and validation tasks, not features assigned to a future version.

  • Public driver marketplace with compatibility checks and a publishing workflow
  • iPhone and Android tablet apps, and centralized management of multiple installations
  • Ready-to-use Grafana dashboards and metrics integration
  • More real-device drivers and model-specific CAN/BLE support
  • Unattended energy execution with safe limits and field validation
  • Physical validation of integrations, fan profiles and collector hardware

Ready to install?

Pick the installation method that fits your hardware and follow its steps; the release history stays available above.

Choose a method
Contribute