Kostal Plenticore Hybrid (battery)
The Kostal Plenticore Hybrid is a three-phase hybrid PV inverter with an integrated battery interface, used in residential and small-commercial solar-plus-storage installations. This template targets the external battery management feature of the Kostal Plenticore Hybrid over Modbus TCP. It exposes the minimum SoC setpoint (register 1042), which lets your ModbusCloud Gateway instruct the inverter how far the battery is permitted to discharge. Setting this limit correctly protects battery longevity and supports dynamic control strategies such as time-of-use charging.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 1, read and write
- Brand
- Kostal
- Last updated
Registers (1)
0 read, 1 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| limitsoc | % | Write |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Set a minimum SoC floor to prevent the battery from discharging below a safe threshold on cold winter nights.
- Raise the minimum SoC limit dynamically before a forecast period of low PV yield to reserve backup capacity.
- Alert on unexpected changes to the minimum SoC setpoint that may indicate unauthorized external control.
- Track scheduled SoC limit writes in the ModbusCloud portal to verify automation rules executed correctly.
- Compare the configured minimum SoC across multiple Plenticore sites to enforce a consistent discharge policy.
Installation
Log in to the Plenticore web interface as an installer, navigate to Service > Battery settings, set Battery control to 'External via protocol (Modbus TCP)', and save.
Connect the ModbusCloud Gateway to the same LAN as the Plenticore inverter. The Plenticore uses Modbus TCP port 1502, not the standard port 502.
In your ModbusCloud portal, add the Gateway, import the Kostal Plenticore Hybrid (battery) template, and assign unit ID 71 (the Plenticore default) to the device.
Write a test value to register 1042 from the portal and confirm the Plenticore web interface reflects the updated minimum SoC limit.
Things to watch for
Why does the Plenticore ignore writes to register 1042?
External battery control must be explicitly enabled in the inverter web interface under Service > Battery settings. Without switching Battery control to 'External via protocol (Modbus TCP)', the inverter rejects all write commands to the battery management registers regardless of whether the Modbus TCP connection is established.
The gateway connects on port 502 but returns errors. What is wrong?
The Kostal Plenticore uses a non-standard Modbus TCP port of 1502, not 502. Update your ModbusCloud Gateway device configuration to target port 1502. Connections to port 502 will be refused or return no valid data.
Register 1042 reads back garbled float values after a firmware update.
The Plenticore interprets float32 registers using Big-Endian (ABCD) byte order. Verify the byte order setting in the inverter's communication configuration. If the inverter is set to Little-Endian, float values across all registers will appear corrupted. Set it to Big-Endian and re-test.
Is it safe to write any percentage to the minimum SoC setpoint?
Use caution when writing to register 1042. Setting the minimum SoC to 100 effectively locks the battery against all discharge. The inverter also applies a watchdog: if writes stop for longer than the configured timeout (typically 60 seconds), it reverts to internal control. ModbusCloud writes registers at most once per minute, so keeping this 60-second window is borderline and not guaranteed. Write-register settings are not stored in non-volatile memory and are lost on inverter restart, so automation must re-apply them after any power cycle.
Want to see how it works?
