Sigenergy Solar System

Adapter for Sigenergy solar energy systems via Modbus TCP/RTU

Supports the Sigenergy Modbus Protocol V2.9 (released 2026-05-13).

Features

• 📡 Modbus TCP (Ethernet / WLAN / Optical fiber / 4G) — Port 502
• 🔗 Modbus RTU (RS485 Serial)
• ⚡ Full register support — All plant, inverter, PSS and PID registers per V2.9 spec
• 🔋 Battery statistics — Time to full, time remaining, daily coverage
• ☀️ PV statistics — Self-consumption rate, autarky rate
• 🔌 AC Charger (Sigen EVAC) — Optional
• ⚡ DC Charger — Optional
• 🏗️ PSS (Power Station Switch) — Optional, MV/LV switchgear and distribution cabinet monitoring
• 🔍 PID (PV Insulation Detection) — Optional
• 🌡️ ESS Preheating — TOU schedule, 30 configurable time windows (M1-HYA/HYB)
• 📈 Extended registers — Smart loads 1–24, cumulative energy, grid code parameters
• ☀️ SigenMicro — Micro-inverter support (auto-scan)
• 📊 Calculated values — Derived statistics updated each poll cycle
• 🖥️ VIS Widgets — Energy flow, battery status, statistics panels

Supported Hardware

Requirements

Default Modbus Addresses

Device Types

Since v2.4.0 every adapter instance handles exactly one Sigenergy system type (strict either/or). Select the type in the Components tab — or use Auto-detect from device to read it from the hardware. Register sets are gated per the model footnotes of the official Modbus Protocol V2.9:

One Modbus endpoint (IP/bus) = one instance. A SigenStor with additional SigenMicro micro-inverters belongs in a single instance — the micros are an additive component, not a separate type. Existing pre-2.4.0 configurations are migrated automatically (derived type is logged on startup — please review the Components tab once).

Configuration

Connection Tab

• Connection Type: TCP (Ethernet) or Serial (RS485)
• TCP Host: IP address of your inverter
• TCP Port: 502 (default)
• Plant Modbus ID: 247 (default)
• Inverter Modbus ID: 1 (default)

Components Tab

Select which devices are installed:

• Battery / ESS
• PV Panels
• AC Charger (EVAC)
• DC Charger
• PSS (Power Station Switch)
• PID (PV Insulation Detection)
• ESS Preheating (M1-HYA/HYB only)
• SigenMicro (micro-inverters)

Statistics Tab

Choose which statistical values to calculate:

• Battery time to full
• Battery time remaining
• Daily charge time
• Battery coverage time
• Self-consumption rate
• Autarky rate

Data Objects

Plant (plant.*)

Inverter (inverter.*)

Statistics (statistics.*)

Emergency Switching — Protecting External PV Systems

Background

Sigenergy hybrid inverters include an optional emergency power gateway that automatically switches to off-grid / island mode when the utility grid fails. In this mode, the Sigenergy system creates its own local AC grid powered by the battery.

If a second PV system — such as a balcony power plant, a micro-inverter, or a third-party string inverter — is connected to the same household circuit, it will continue feeding power into this isolated local grid. Most grid-tied inverters are not designed for this situation and may:

• overload the Sigenergy battery management
• cause voltage or frequency instability on the island grid
• be damaged by the unusual operating conditions

The only safe solution is to immediately disconnect the external system when Sigenergy enters off-grid mode.

How the adapter handles this

The adapter monitors the plant.onOffGridStatus state every poll cycle.

On grid failure (onOffGridStatus = 1 or 2):

• All configured emergency devices are switched instantly
• A Telegram notification is sent (optional)

On grid return (onOffGridStatus = 0):

• A configurable stability timer starts (default: 10 minutes)
• If the grid remains stable for the full duration, devices are restored
• If the grid fails again during the timer, the timer is discarded and devices remain off
• A Telegram notification is sent on successful restoration (optional)

Enabling the feature

Step 1 — Components tab
Check Emergency Gateway (off-grid switching).
The Emergency Switching tab becomes visible.

Step 2 — Emergency Switching tab

Devices

Telegram notifications (optional)

Example — Balcony power plant

A Shelly Plus 1 relay is wired in series with the balcony power plant's supply cable. Its ioBroker state ID is shelly.0.SHPLUS1-ABC123.Relay0.Switch.

Configuration:

• Device 1: shelly.0.SHPLUS1-ABC123.Relay0.Switch
  → Relay opens (false) on grid failure, closes (true) after stable recovery

The balcony power plant is now automatically protected.

VIS Widgets

Note: All 7 widgets are provided by the separate ioBroker.vis-2-widgets-sigenergy adapter. Install it alongside this adapter to use the widgets in VIS-2.

Energy Flow Widget

Shows animated energy flow between PV → Battery ↔ Grid → House.

Battery Status Widget

Displays SOC bar, SOH badge, time to full/empty, current power.

Power Overview Widget

Live reading of all four power flows.

Statistics Widget

Today's autarky, self-consumption, SOC min/max, battery coverage time.

Inverter Widget

Live inverter data: PV power, grid frequency, phase voltages, temperature.

AC Charger Widget (EVAC)

Status and power readings for the Sigen EVAC charging station.

DC Charger Widget

Status and power readings for the DC charger.

Communication Protocol

• Modbus TCP: TCP mode, full duplex, port 502 (slave)
• Modbus RTU: Half duplex, 9600 bps, 8N1
• Min poll interval: 1000 ms (1 second) per Sigenergy spec
• Timeout: 1000 ms per Sigenergy spec

Changelog

3.3.3 (2026-09-12)

• (ssbingo) fix: io-package.json names ssbingo <s.sternitzke@online.de> as maintainer instead of the placeholder "ioBroker Community", which carried no contact address — reported as [E4048] by the ioBroker repository checker. The entry now matches author in package.json
• (ssbingo) fix: common.news trimmed to the seven most recent versions ([W1032]); the ioBroker repository builder truncates there anyway. The full history stays in this changelog

3.3.2 (2026-09-12)

• (ioBroker-Bot) chore: the CI test matrix now also covers Node.js 26 (22/24/26 on ubuntu, windows and macOS) — all three run green, so the adapter is ready for the October 2026 LTS
• (ssbingo) chore: @iobroker/testing updated from 5.3.0 to 6.2.1
• (ssbingo) chore: raised the deepl-node override to 1.28.0 and adm-zip to 0.6.1. 1.28.0 no longer depends on js-yaml and accepts the patched adm-zip, which clears the two advisories the updated tooling pulled in — npm audit is back to 0. Development tooling only; npm audit --omit=dev was 0 throughout

3.3.1 (2026-09-07)

• (ssbingo) fix: registers the device marks as not valid are no longer turned into plausible looking measurements. The protocol signals this by setting all bits ("Range:[0, 0xFFFFFFFE]. With value 0xFFFFFFFF, register is not valid.") and a device answers that way for a register that does not currently apply or that its firmware does not implement. The raw sentinel was scaled by the register gain, so it arrived as a reading that looks real: observed on a SigenStor EC 10.0 TP with a DC charger installed, dcCharger.runningState = 65535 (Appendix 14 only defines 0x00-0x0A), dcCharger.dischargingCurrent = 6553.5 A, dcCharger.currentDischargingCapacity = 42949672.95 kWh and dcCharger.currentDischargingDuration = 4294967295 s, while the neighbouring DC charger registers (rated power, PV generation, totals) returned real values. The same pattern appears outside the DC charger, e.g. plant.currentCtrlCmdValue = 655.35 %, plant.mergedAlarm7 = 65535, inverter.essMaxBatteryCellVoltage = 65.535 V and the ESS/PCS/grid limit registers as 4294967.295 kW. Such registers now report no value instead
• (ssbingo) fix: a register that reports no value no longer feeds the statistics calculation, which keeps the last known good reading instead

3.3.0 (2026-09-07)

• (ssbingo) fix: when the device rejects a grouped register read with a Modbus exception, the registers of that group are now read one by one and only the register(s) the device does not implement are excluded from further polling. Previously a single unsupported register silently disabled its whole group for the rest of the adapter runtime, e.g. dcCharger.runningState (31513) never received a value when the discharging registers 31514–31518 of the same group were rejected
• (ssbingo) feat: new state info.protocolVersion (number, e.g. 2.9) next to the textual info.protocolLevel, so widgets and scripts can adapt to the detected protocol version without parsing strings
• (ssbingo) feat: DC charger registers carry the protocol version that introduced them (since, from the V2.9 revision history: 31509–31511 V2.6, 31513 V2.8, 31514–31525 V2.9); registers newer than the detected protocol level are not requested, so a V2.8 device no longer gets its DC charger group rejected because of the V2.9 discharging registers
• (ssbingo) chore: grouped register reading moved to lib/readGroups.js and covered by unit tests
• (ssbingo) feat: all registers dated by the V2.9 revision history now carry since via a central PROTOCOL_SINCE table in lib/registers.js (plant 30088–30192 V2.6, 30194–30268 V2.7, 30276–30285 V2.8, 30272/30274/30286 V2.9, 40046–40048 V2.6, 40049–40068 V2.8, 40157–40159 V2.9, ESS preheating 50000–50183 V2.9; inverter 30613–30619 V2.6, 31066–31105 V2.8; DC charger 41002/41004 V2.9; all PSS and PID registers V2.9) and are skipped on devices with an older protocol level
• (ssbingo) fix: the one-time control register read (FC03) and the SigenMicro reader use the same per-register fallback as the input register readers; the control registers are read after the protocol detection so the version gating applies to them as well; ESS preheating polling is skipped below protocol V2.9
• (ssbingo) fix: corrected the protocol version marker in the names of the eleven cumulative energy states 30228-30268 from (V2.8) to (V2.7); the revision history of the V2.9 protocol document lists the cumulative energy interface 30196-30268 under V2.7

3.2.0 (2026-09-04)

• (MMeinhardt1) feat: new state statistics.emsWorkMode exposing the EMS work mode as plain text, so consumers do not need the common.states lookup table
• (MMeinhardt1) feat: added EMS work mode 6 (Virtual Power Plant) to the register description and the mode map
• (MMeinhardt1) change: the *HM duration states now hold a bare H:MM value with unit h, instead of embedding an h suffix in the value itself
• (MMeinhardt1) fix: statistics objects are created with extendObjectAsync, so corrected units and roles reach installations where the object already exists
• (ssbingo) chore: admin minimum requirement lowered back to >= 7.8.23 to keep serving admin 7.x installations
• (ssbingo) fix: restored the JSDoc parameter descriptions on _formatMinutesAsHM to keep npm run lint warning-free
• (ssbingo) chore: repository checker findings — track .vscode/settings.json deliberately, bump @alcalzone/release-script-plugin-license to 5.2.2, pin testing-action-deploy to the major version again

3.1.2 (2026-08-06)

• (ssbingo) chore: resolved all 28 npm audit findings (3 critical, 11 high) — development tooling only, the published adapter is unchanged
• (ssbingo) chore: removed @iobroker/dev-server; it was the sole source of the critical findings via the deprecated request and xmldom packages, for which no fixed release exists. This also removes the npm start / npm run watch scripts
• (ssbingo) chore: added overrides lifting transitive dev dependencies onto patched versions
• (ssbingo) chore: removed main.test.js, an unused create-adapter template stub

3.1.1 (2026-08-05)

• (ssbingo) chore: security updates for transitive dependencies (brace-expansion 1.1.18, axios 1.19.0, fast-uri 3.1.5, socket.io-parser 4.2.7)

3.1.0 (2026-08-05)

• (MMeinhardt1) feat: statistics module improvements — new states pvToBatteryPower, batteryToHousePower, gridImportToday, gridExportToday, currentSoc, currentPvPower and h:mm formatted durations for all time statistics
• (MMeinhardt1) feat: daily statistics (SOC min/max, coverage time, grid energy, charging time) are restored from persisted states and now survive an adapter restart mid-day
• (MMeinhardt1) change: batteryDailyChargeTime now reports the cumulative time spent charging today instead of the time until the battery was first full
• (MMeinhardt1) fix: battery coverage time is accumulated incrementally instead of being derived from the capped history buffer, which only spanned ~1 hour
• (ssbingo) chore: minimum requirements raised — js-controller >= 6.0.11, admin >= 8.0.0, Node.js >= 22
• (ssbingo) fix: add missing admin i18n translations for the new battery flow power option across all 11 languages
• (ssbingo) chore: update dependencies (@iobroker/adapter-core 3.4.3, @iobroker/testing 5.3.0, @types/node 22.20.1, ws 8.21.1, actions/setup-node v7, testing-action-deploy 1.5.2)

3.0.10 (2026-06-29)

• (ssbingo) chore: bump js-yaml from 4.1.1 to 4.3.0

3.0.9 (2026-06-29)

• (ssbingo) chore: pin CI actions to major version (@v1) instead of patch version

3.0.8 (2026-06-29)

• (ssbingo) fix: add missing i18n translations for SigenMicro scan UI strings (es, fr, it, nl, pl, pt, uk, zh-cn)

3.0.7 (2026-06-28)

• (ssbingo) chore: update dependencies (@iobroker/adapter-core 3.4.1, @types/node 22.20.0, testing-action-adapter 1.1.1, testing-action-deploy 1.5.0, http-proxy-middleware 3.0.7)

3.0.6 (2026-06-14)

• (ssbingo) fix: remove duplicate common.license field — licenseInformation already present

3.0.5 (2026-06-14)

• (ssbingo) fix: add missing license field to io-package.json common block

3.0.4 (2026-06-14)

• (ssbingo) fix: emergency Telegram notification now sent only once per grid-failure event (not repeated every poll); device switching limited to 3 attempts max (initial + 2 retries) while off-grid

3.0.3 (2026-06-13)

• (ssbingo) fix: remove non-functional welcomeText from io-package.json; add visible warning staticText in Emergency Switching config tab (yellow box, i18n in all 11 languages)

3.0.2 (2026-06-13)

• (ssbingo) fix: ESLint/Prettier errors in emergency switching methods — remove unused variable, fix indentation, add JSDoc @param types

3.0.1 (2026-06-13)

• (ssbingo) feat: add welcomeText to io-package.json — multilingual notice about emergency gateway switching feature

3.0.0 (2026-06-13)

• (ssbingo) feat: emergency gateway switching — automatic disconnection of external PV systems (balcony power plants, micro-inverters) on grid failure; configurable stability timer on grid return; optional Telegram notifications
• (ssbingo) docs: emergency switching documentation added in all 11 languages

2.5.2 (2026-06-12)

• (ssbingo) fix: URL-encode spaces in Buy Me a Coffee button src — image was not rendering on GitHub

2.5.1 (2026-06-12)

• (ssbingo) fix: correct instanceObject role for info.modelType from 'info.name' to 'text' (W1133/W1135 adapter-checker warnings)

2.5.0 (2026-06-12)

• (ssbingo) Architectural write safety: Modbus writes are rejected in the write dispatcher itself when the target register is not valid for the configured device type (models gating in onStateChange, plant guard for SigenMicro-only)
• (ssbingo) TypeScript type check fixed — new lib/adapter-config.d.ts with full AdapterConfig declaration, typed modbus-serial constructor, ioBroker.CommonType/SettableObject annotations; new npm run check script passes with 0 errors
• (ssbingo) ESLint configuration allows JSDoc @type tags in this checked-JavaScript project (jsdoc/check-tag-names with typed:false)

2.4.0 (2026-06-12)

• (ssbingo) Device type architecture: mandatory selector (SigenStor / Sigen Hybrid / Sigen PV M1-HYB / PV-only inverter / SigenMicro-only) with strict either/or register gating per protocol V2.9 model footnotes
• (ssbingo) Sigen Hybrid and PV-only inverters (Sigen PV / PV Max) officially supported
• (ssbingo) Auto-detect device type from hardware in the admin UI (registers 30500 / 31024)
• (ssbingo) Model verification on startup — warns when configuration and detected hardware mismatch (new state info.modelType)
• (ssbingo) Dynamic PV string registers: PV5-PV16 voltage/current enabled by the string count reported in register 31025
• (ssbingo) PCC power factor controls (40157/40158) gated to Sigen PV M1-HYB; ESS preheating gated to M1-HYB; DC charger and grid code gated to SigenStor/Sigen Hybrid
• (ssbingo) Automatic migration of pre-2.4.0 configurations and cleanup of channels that are invalid for the selected device type

2.3.4 (2026-06-12)

• (ssbingo) fix: correct protocol level detection — use proper register quantities for probes, descend from V2.9 to V2.6, distinguish transport errors from device exceptions to avoid false pre-V2.6 report

2.3.3 (2026-06-11)

• (ssbingo) fix: suppress repeated register read warnings after first occurrence for plant/inverter/acCharger/dcCharger/pss/pid; subsequent failures log at debug level only

2.3.2 (2026-06-10)

• (ssbingo) fix: show 'pre-V2.6' instead of 'unknown' when device responds but has no extended plant registers; add per-probe debug log with Modbus exception message

2.3.1 (2026-06-10)

• (ssbingo) feat: detect Modbus protocol level on startup by probing registers 30088/30200/30228/30286; read firmware version (30525); log result and store as info.protocolLevel state

2.3.0 (2026-06-10)

• (ssbingo) feat: add common.states enum maps for emsWorkMode/runningState/remoteEmsMode/dcCharger.runningState; wire PSS/PID/AC Charger write registers (FC06/FC10) with subscribe and onStateChange handlers

2.2.7 (2026-06-10)

• (ssbingo) fix: add missing native defaults enableSmartLoads/enableCumulativeEnergy/enableGridCode to io-package.json
• (ssbingo) fix: update register 30003 desc with V2.7 EMS modes 5 (FullFeedIn) and 9 (Custom)

2.2.6 (2026-06-10)

• (ssbingo) feat: V2.9 register audit — add missing register 30279 (current control command value), move DC Charger PV registers 31509/31511 to dcCharger namespace, fix ESS Preheating TOU time gain (null→1)
• (ssbingo) feat: implement control write-back for plant.control., plant.gridCode., inverter.control., dcCharger.control. (FC06/FC10); read RW holding registers on startup
• (ssbingo) fix: suppress repeated ESS Preheating warn after device reports unsupported registers; downgrade control register startup read errors to debug

2.2.4 (2026-06-10)

• (ssbingo) fix: implement ESS Preheating TOU polling (FC03, 50000–50183, 94 registers) and write-back via onStateChange; add encodeValue to ModbusConnection

2.2.3 (2026-06-10)

• (ssbingo) fix: add 25 missing admin i18n keys for PSS, PID, ESS Preheating, Extended Registers across all 11 languages

2.2.2 (2026-06-09)

• (ssbingo) docs: update all READMEs to Modbus Protocol V2.9 — add PSS, PID, ESS Preheating, Extended Registers, SigenMicro; correct protocol version reference

2.2.1 (2026-06-09)

• (ssbingo) fix: correct PSS register table to 122 entries per official spec V2.9 (addresses, gains, types); fix PSS write registers to 6 WO entries; fix PID registers 33055-33060 (types, gains, 2 missing entries)

2.2.0 (2026-06-09)

• (ssbingo) feat: PSS (Power Station Switch) and PID (PV Insulation Detection) support; ESS Preheating TOU schedule registers; new admin options for PSS/PID slave IDs

2.1.1 (2026-06-09)

• (ssbingo) fix: wire feature flags (enableSmartLoads, enableCumulativeEnergy, enableGridCode) into polling and object creation; add Extended Registers admin tab

2.1.0 (2026-06-09)

• (ssbingo) feat: extended statistics — plant statistics (30088–30097), smart loads 1–24 (30098–30193), cumulative energy (30194–30271), adjustment feedback (30613–30619), grid code parameters (40049–40068)

2.0.0 (2026-06-09)

• (ssbingo) feat: Modbus Protocol V2.9 — new plant/inverter/DC charger registers, remove deprecated registers, extend enums

Documentation

• 🇩🇪 Deutsche Dokumentation
• 🇷🇺 Документация на русском
• 🇳🇱 Nederlandse documentatie
• 🇫🇷 Documentation française
• 🇮🇹 Documentazione italiana
• 🇪🇸 Documentación en español
• 🇵🇱 Dokumentacja polska
• 🇵🇹 Documentação portuguesa
• 🇺🇦 Документація українською
• 🇨🇳 简体中文文档

License

MIT License

Copyright (c) 2026 ssbingo s.sternitzke@online.de

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.