SMA Sunny Tripower STP (Modbus)

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire. Word order and scaling are confirmed at the hardware-verified rung and at no rung below it.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale
device_class	30050	U32BE	1
device_type	30052	U32BE	1
serial_number	30056	U32BE	1
condition	30200	U32BE	1
nominal_power_ok	30202	U32BE	1
insulation_resistance	30224	U32BE	1
max_active_power	30230	U32BE	1
total_yield_wh	30528	U32BE	1
total_yield_kwh	30530	U32BE	1
daily_yield_wh	30534	U32BE	1
daily_yield_kwh	30536	U32BE	1
operating_time	30540	U32BE	1
feed_in_time	30542	U32BE	1
dc_current_input_1	30768	U32BE	0.001
dc_voltage_input_1	30770	U32BE	0.01
dc_power_input_1	30772	U32BE	1
power	30774	U32BE	1
power_l1	30776	U32BE	1
power_l2	30778	U32BE	1
power_l3	30780	U32BE	1
grid_voltage_l1	30782	U32BE	0.01
grid_voltage_l2	30784	U32BE	0.01
grid_voltage_l3	30786	U32BE	0.01
grid_current	30794	U32BE	0.001
grid_frequency	30802	U32BE	0.01
reactive_power	30804	U32BE	1
apparent_power	30812	U32BE	1
displacement_power_factor	30948	U32BE	0.001
internal_temperature	30952	U32BE	0.1
dc_current_input_2	30956	U32BE	0.001
dc_voltage_input_2	30958	U32BE	0.01
dc_power_input_2	30960	U32BE	1
intermediate_circuit_voltage	30974	U32BE	0.01
grid_current_l1	30976	U32BE	0.001
grid_current_l2	30978	U32BE	0.001
grid_current_l3	30980	U32BE	0.001
residual_current	31246	U32BE	0.001
operating_condition	40008	U32BE	1
operating_status	40028	U32BE	1
max_apparent_power	40184	U32BE	1

bench facts as documented (unverified)

model register	30053
serial register	30057
firmware register	30059
firmware applicability	Starting with software package: 2.55.03.R

field reports — community-sourced, unverified (checked 2026-06-11)

On certain firmware versions or specific inverter models (such as STP 5.0-3AV-40), the daily yield registers (30535 / 30537) return 4294967295 (0xFFFFFFFF), which represents 'NaN' or 'not available' in SMA's data format, rather than the actual daily yield. [source]
When the inverter goes to sleep at night, measurement registers (such as AC power, grid voltage, etc.) return maximum allowable values of the data type (e.g., 4294967295 for U32 or -2147483648 for S32) representing 'not available', causing spikes in monitoring systems if not filtered. [source]
Users report having to add 1 to all register numbers (e.g., using 30002 instead of 30001) because of the difference between 0-based and 1-based addressing in different Modbus clients/interfacers. [source]
The Sunny Tripower series (especially those co-developed with Sungrow, like the Smart Energy series) is highly sensitive to multiple concurrent Modbus TCP clients, which can cause overlapping requests, connection drops, or communication failures, requiring a Modbus proxy to serialize requests. [source]
confirmed: firmware_applicability: Starting with software package: 2.55.03.R — confirmed by SMA Modbus Profile documentation for Sunny Tripower (STP 5000TL-20 to STP 12000TL-20) which explicitly lists this starting software package version [1.1.3].
confirmed: identification: firmware_register: 30059, model_register: 30053, serial_register: 30057 — confirmed by SMA Modbus Profile documentation and community integration scripts (e.g., solariot) which map Software package to 30059, Device type to 30053, and Serial number to 30057.

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.