GoodWe ET/EH/BT/BH hybrid inverter

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	unit
vpv1	35103	U16	0.1	V
ipv1	35104	U16	0.1	A
ppv1	35105	U32BE	0.1	W
vpv2	35107	U16	0.1	V
ipv2	35108	U16	0.1	A
ppv2	35109	U32BE	0.1	W
vgrid_r	35121	U16	0.1	V
igrid_r	35122	U16	0.1	A
fgrid_r	35123	U16	0.01	Hz
pgrid_r	35125	I16	1	W
vgrid_s	35126	U16	0.1	V
igrid_s	35127	U16	0.1	A
fgrid_s	35128	U16	0.01	Hz
pgrid_s	35130	I16	1	W
vgrid_t	35131	U16	0.1	V
igrid_t	35132	U16	0.1	A
fgrid_t	35133	U16	0.01	Hz
pgrid_t	35135	I16	1	W
total_inv_power	35138	I16	1	W
ac_active_power	35140	I16	1	W
ac_reactive_power	35142	I16	1	Var
ac_apparent_power	35144	I16	1	VA
backup_vload_r	35145	U16	0.1	V
backup_iload_r	35146	U16	0.1	A
backup_fload_r	35147	U16	0.01	Hz
backup_pload_r	35150	I16	1	W
pload_r	35164	I16	1	W
pload_s	35166	I16	1	W
pload_t	35168	I16	1	W
total_backup_load	35170	I16	1	W
total_load_power	35172	I16	1	W
ups_load_percent	35173	U16	0.01	%
air_temperature	35174	I16	0.1	C
module_temperature	35175	I16	0.1	C
radiator_temperature	35176	I16	0.1	C
bus_voltage	35178	U16	0.1	V
nbus_voltage	35179	U16	0.1	V
vbattery1	35180	U16	0.1	V
ibattery1	35181	I16	0.1	V
pbattery1	35183	I16	1	W
pv_e_total	35191	U32BE	0.1	kWh
pv_e_day	35193	U32BE	0.1	kWh
e_total	35195	U32BE	0.1	kWh
e_day_sell	35199	U16	0.1	kWh
e_total_buy	35200	U32BE	0.1	kWh
e_day_buy	35202	U16	0.1	kWh
e_total_load	35203	U32BE	0.1	kWh
e_load_day	35205	U16	0.1	kWh
e_battery_charge	35206	U32BE	0.1	kWh
e_charge_day	35208	U16	0.1	kWh
e_battery_discharge	35209	U32BE	0.1	kWh
e_discharge_day	35211	U16	0.1	kWh
bms_pack_temperature	37003	U16	0.1
bms_charge_imax	37004	U16	1
bms_discharge_imax	37005	U16	1
bms_soc	37007	U16	1	%
bms_soh	37008	U16	1	%
bms_max_cell_temp	37020	U16	0.1	°C
bms_min_cell_temp	37021	U16	0.1	°C
bms_max_cell_volt	37022	U16	1	mV
bms_min_cell_volt	37023	U16	1	mV

link settings as documented (unverified): RTU; default 9600 8N1; unit ID 247; FC 03,06,16; EMS port on inverter.

bench facts as documented (unverified)

terminals	EMS port
connector	RJ45
wiring notes	RJ45 pinout: 1: 485_A, 2: 485_B, 3: 485_A, 6: 485_B, others NC
protocol notes	Error codes: 02H (Register address fault or overflow), 03H (Data error), 04H (Built-in verification code error), 05H (Communication time-out)
model register	35011
serial register	35003
firmware register	35016
identification notes	Other firmware registers: 35017 (DSP2 software version), 35019 (ARM software version), 35021 (DSP Internal Firmware Ver.), 35027 (ARM Internal Firmware Ver.)
power	Solar inverter must be powered up by DC or AC power before it can communicate successfully.
doc revision	1.7

⚠ disputed: pbattery1 @ 35183 — disputed by newer firmware versions and integration guides where the battery power register shifted to 35182 or is represented as a 32-bit signed integer starting at 35182

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

The battery power register (Pbattery1) is wrongly documented in official Modbus protocol v1.9 as being Unsigned, but it is actually Signed. [source]
In newer firmware versions, the battery power register (Pbattery1) shifted from 35183 to 35182 (or is a 32-bit signed integer starting at 35182), causing incorrect readings if read as a 16-bit register at 35183. [source]
confirmed: Default unit ID is 247, default baud rate is 9600, framing is RTU — confirmed by GoodWe EMS Protocol Overview and multiple integration guides
confirmed: RJ45 pinout: 1: 485_A, 2: 485_B, 3: 485_A, 6: 485_B — confirmed by Sunergy Partners integration documentation
confirmed: Error codes: 02H (Register address fault), 03H (Data error), 04H (Built-in verification code error), 05H (Communication time-out) — confirmed by GoodWe EMS Protocol Overview

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.