Sigenergy and Home Assistant: Integration Guide (2026)

If you run Home Assistant, you probably want your battery in it: live energy flows on your own dashboard, automations that respond to a spot price, and control that does not depend on a manufacturer’s cloud. The Sigenergy SigenStor is a good candidate for this, because it exposes the two interfaces enthusiasts actually use. This guide covers the realistic integration paths, what each gets you, and the honest caveats before you start.

A note up front: none of this is officially supported by Sigenergy. It works, plenty of owners run it, but treat it as enthusiast territory rather than a guaranteed feature.

The two things you are integrating

A full Sigenergy setup has two parts that talk to Home Assistant differently, so it helps to separate them:

• The energy system (the SigenStor battery and its energy controller), which you mostly want to monitor and sometimes control, over Modbus.
• The EV charger, which you want to control and read, over OCPP.

They use different protocols, so treat them as two separate integration jobs.

The EV charger: OCPP, the easy win

Start here, because it is the straightforward part. As covered in our Sigenergy EV charger review, the charger speaks open OCPP 1.6 configurable to any backend. Home Assistant has an OCPP integration that acts as a central system, so you point the charger at your Home Assistant instance and it connects.

Once linked you can read charging power and session energy, start and stop charging, and drive it from automations, for example only charging when your battery is full and solar is surplus, or when the spot price is low. Open OCPP is a real advantage: chargers locked to a manufacturer cloud cannot do this. Define the term while we are here. OCPP (Open Charge Point Protocol) is the open standard that lets a charger talk to any compatible management backend rather than only its maker’s app.

The energy system: Modbus TCP, the local path

For the SigenStor battery and controller, the method most Home Assistant users reach for is Modbus TCP over the local network. Modbus is the long-standing industrial protocol that hybrid inverters commonly expose, and it lets Home Assistant poll the controller directly for values like solar generation, battery state of charge, charge and discharge power, grid import and export, and household load.

The high-level approach is the same as for other hybrid inverters:

1. Confirm with Sigenergy or your installer that local Modbus TCP access is available and how to enable it on your energy controller.
2. Note the controller’s fixed IP address on your home network.
3. Add the connection in Home Assistant (via the built-in Modbus integration, or a community integration if one is available for the SigenStor) and map the registers you want to sensors.

Because register maps and firmware behaviour can change, this is the part that most rewards checking the current Home Assistant community threads for the SigenStor before you begin, rather than following a static list of addresses that may be out of date.

Local Modbus vs the cloud API

You have a choice of where the data comes from, and it matters.

• Local Modbus TCP is the preference for most Home Assistant users. It is fast, keeps working when your internet is down, and has no external dependency. The trade-off is that it needs local access enabled and a little setup.
• Cloud path (reading via Sigenergy’s cloud) can be simpler to stand up, but it adds latency, depends on the internet and Sigenergy’s servers, and is generally less responsive for automations.

For a system you want to automate against a live electricity price, local polling is the better foundation.

What a good integration lets you do

Once both parts are in, the payoff is the kind of automation the stock app cannot do:

• A single dashboard showing solar, battery, grid and load in real time, alongside the rest of your smart home.
• Price-aware automations, for example pairing the battery and charger with an Amber-style spot-price feed to charge when power is cheapest and hold when it is dear.
• Cross-device logic: only start the EV charger when the battery is above a set reserve and solar is exporting.
• Long-term logging and custom reporting for your own ROI tracking, beyond what the mySigen app graphs.

The SigenStor’s own AI energy management already handles a lot of this well on its own, so the reason to integrate is control, unification with your other devices, and data ownership, rather than because the battery cannot optimise itself.

The honest caveats

Three things to go in with eyes open about:

• It is unofficial. Sigenergy does not publish a Home Assistant integration, so you are relying on Modbus, OCPP and community work. Support is the community, not the manufacturer.
• Firmware updates can break it. A controller firmware change can alter behaviour or register maps and break an automation until you adjust it. Keep notes on your setup.
• Do not compromise safety or warranty. Monitoring is low-risk; writing control commands to the battery is where care is needed. Nothing here should override the system’s own protections, and if in doubt, keep the integration read-only.

If you want the smart-home benefits without the tinkering, the built-in AI and mySigen app already deliver strong hands-off optimisation, covered in the full Sigenergy SigenStor review.

---

Common questions

Can you integrate Sigenergy with Home Assistant?

Yes, along two paths. The EV charger uses open OCPP 1.6, which connects to Home Assistant’s OCPP integration directly. The SigenStor energy system is typically read over Modbus TCP on your local network, the standard method for hybrid inverters. Both are unofficial, so confirm current firmware support with Sigenergy first.

Does the Sigenergy EV charger work with Home Assistant?

It does, and this is the easiest part. Because the Sigenergy charger speaks open OCPP 1.6 configurable to any backend, you can point it at Home Assistant’s OCPP server and control charging, read power and set schedules locally. This is a genuine advantage over closed chargers locked to a manufacturer cloud.

Is there an official Sigenergy Home Assistant integration?

Sigenergy does not publish an official Home Assistant integration. The practical routes are local Modbus TCP for the energy system and OCPP for the charger, sometimes helped by community integrations. Because these are unofficial, a firmware update can change behaviour, so treat the setup as enthusiast territory rather than a supported feature.

Should I use local Modbus or the cloud API for Sigenergy?

Local Modbus TCP is preferable for Home Assistant: it is faster, keeps working if your internet drops, and does not depend on Sigenergy’s cloud. A cloud path can be simpler to start with but adds latency and an external dependency. Most Home Assistant users choose local polling where the firmware allows it.

Will a Sigenergy firmware update break my Home Assistant setup?

It can. Because these integrations are unofficial, a firmware change can alter register maps or behaviour and break an automation until you adjust it. Keep notes on your configuration, follow the Home Assistant community threads for the SigenStor, and expect the occasional tweak after major updates.

---

Related reading: the full Sigenergy SigenStor review, the Sigenergy EV charger review, and the Sigenergy specs hub.