Strong Energy Alfred 10 (battery)
The Strong Energy Alfred 10 is an all-in-one residential and commercial battery storage system combining a 10 kW hybrid inverter with a lithium iron phosphate battery in capacities from 12 kWh to 24 kWh. This ModbusCloud template communicates over Modbus TCP and reads battery state of charge (register 8192), instantaneous power (register 8201), and cumulative energy throughput (register 8209). Five write registers (8448 to 8451, 8524) expose the battery operating mode, enabling charge and discharge control from your portal. Together these registers give installers and asset managers a complete picture of storage behaviour and direct control over operating modes without accessing the Alfred 10 locally.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 8, read and write
- Brand
- Strong Energy
- Compatible models
- Hybrid Inverter · Alfred 10
- Last updated
Registers (8)
3 read, 5 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| soc | % | Read | |||
| batterymode_a | Write | ||||
| batterymode_b | Write | ||||
| batterymode_e | Write | ||||
| batterymode_f | Write | ||||
| batterymode_g | 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
- Monitor battery state of charge continuously to detect abnormal self-discharge between charge cycles.
- Track cumulative energy throughput over time to assess battery ageing and plan preventive maintenance.
- Alert on sudden power sign reversals to catch unexpected discharge events during low-tariff periods.
- Verify that battery mode setpoints written via the portal are correctly accepted by the Alfred 10.
- Report daily charge and discharge cycles to building owners as part of a monthly energy performance summary.
Installation
Enable Modbus TCP on the Alfred 10 through the Strong Energy app or the inverter web interface under the communication or Modbus section, and note the assigned IP address.
Connect the Alfred 10 to the same local network as the ModbusCloud Gateway using a standard Ethernet cable, ensuring both devices are on the same subnet.
In the ModbusCloud portal, add the Gateway, import the Strong Energy Alfred 10 (battery) template, and set the unit ID to match the value configured on the inverter (commonly 1).
Spot-check register 8192 (soc) in the portal live data view and confirm the reading matches the state of charge shown on the Alfred 10 display or app before going live.
Things to watch for
Why does the soc register always read zero or a fixed value?
The Alfred 10 may report zero on register 8192 if the battery management system has not completed its initialisation cycle. Allow the system to complete one full charge-discharge cycle after commissioning. Also confirm the unit ID in the portal matches the inverter's configured Modbus slave ID.
The Gateway connects but power and energy registers return no data. What now?
Registers 8201 and 8209 are 32-bit values spanning two consecutive 16-bit holding registers. Confirm your portal template is reading them as int32 and uint32 respectively. A word-order mismatch (big-endian vs. little-endian) will produce garbage or zero values. Check that the Alfred 10 IP is reachable from the Gateway subnet and that no firewall blocks TCP port 502.
I wrote a battery mode value but the Alfred 10 ignores it. Why?
Multiple mode registers (8448, 8449, 8450, 8451, 8524) may need to be written in a specific combination or sequence to activate a mode change. Consult the Alfred 10 Modbus documentation for valid mode word values. Writing an unsupported value is silently ignored by the inverter firmware.
Is it safe to write to the battery mode registers remotely via ModbusCloud?
Use caution when writing to registers 8448 to 8451 and 8524. An incorrect mode command can force the battery into a state that conflicts with grid-export limits or protection thresholds set by the installer. Always test mode writes during commissioning under supervision and confirm the new mode on the Alfred 10 display before enabling automated writes in production.
More Strong Energy templates
Want to see how it works?
