SolarEdge Meter via Inverter Modbus register map
Also searched as: SolarEdge Energy Meter · SolarEdge meter 1
37 Modbus registers of the SolarEdge Meter via Inverter, with the address on the wire, the 30001-style reference, data type, byte order, unit and scale. Transcribed from Technical Note: SolarEdge Inverters - SunSpec Logging (3.3 (October 2026)).
First energy meter connected to a SolarEdge inverter, served by the inverter as SunSpec meter model 201-204.
- Device type
- Energy meter
- Registers
- 37
- Interfaces
- Modbus TCP, Modbus RTU
- Byte order (multi-register values)
- ABCD
Hardware verification
Not yet verified on hardware. The map is transcribed from the vendor document and checked against it by script; check the first readings against the device display.
Connection notes
- Read from the inverter's unit ID with function 03. Registers are big-endian; 32-bit values are high word first.
- Addresses are for meter 1 on a single inverter. Add 50 for 2-unit and 70 for 3-unit Synergy inverters; meter 2 starts 174 registers later (base 40295).
- Only enabled meters are readable. Single phase meters serve only the total and phase A values.
- Value = raw x 10^scale_factor.
Registers
Grouped as in the vendor document.
Current 5 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
AC current (sum of active phases)ac_current | 440191 | 0x9CFE | int16 | A | SF: ac_current_sf | |
Phase A currentac_current_a | 440192 | 0x9CFF | int16 | A | SF: ac_current_sf | |
Phase B currentac_current_b | 440193 | 0x9D00 | int16 | A | SF: ac_current_sf | |
Phase C currentac_current_c | 440194 | 0x9D01 | int16 | A | SF: ac_current_sf | |
Current scale factorac_current_sf | 440195 | 0x9D02 | int16 |
Voltage 9 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Line to neutral voltage (average)voltage_ln | 440196 | 0x9D03 | int16 | V | SF: voltage_sf | |
Phase A to neutral voltagevoltage_an | 440197 | 0x9D04 | int16 | V | SF: voltage_sf | |
Phase B to neutral voltagevoltage_bn | 440198 | 0x9D05 | int16 | V | SF: voltage_sf | |
Phase C to neutral voltagevoltage_cn | 440199 | 0x9D06 | int16 | V | SF: voltage_sf | |
Line to line voltage (average)voltage_ll | 440200 | 0x9D07 | int16 | V | SF: voltage_sf | |
Phase A to B voltagevoltage_ab | 440201 | 0x9D08 | int16 | V | SF: voltage_sf | |
Phase B to C voltagevoltage_bc | 440202 | 0x9D09 | int16 | V | SF: voltage_sf | |
Phase C to A voltagevoltage_ca | 440203 | 0x9D0A | int16 | V | SF: voltage_sf | |
Voltage scale factorvoltage_sf | 440204 | 0x9D0B | int16 |
Frequency 2 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Frequencyfrequency | 440205 | 0x9D0C | int16 | Hz | SF: frequency_sf | |
Frequency scale factorfrequency_sf | 440206 | 0x9D0D | int16 |
Power 9 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Total real poweractive_power | 440207 | 0x9D0E | int16 | W | SF: active_power_sf | |
Phase A real poweractive_power_a | 440208 | 0x9D0F | int16 | W | SF: active_power_sf | |
Phase B real poweractive_power_b | 440209 | 0x9D10 | int16 | W | SF: active_power_sf | |
Phase C real poweractive_power_c | 440210 | 0x9D11 | int16 | W | SF: active_power_sf | |
Real power scale factoractive_power_sf | 440211 | 0x9D12 | int16 | |||
Total apparent powerapparent_power | 440212 | 0x9D13 | int16 | VA | SF: apparent_power_sf | |
Apparent power scale factorapparent_power_sf | 440216 | 0x9D17 | int16 | |||
Total reactive powerreactive_power | 440217 | 0x9D18 | int16 | var | SF: reactive_power_sf | |
Reactive power scale factorreactive_power_sf | 440221 | 0x9D1C | int16 |
Energy 3 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Total exported real energyexported_energy | 440227 | 0x9D22 | uint32 | ABCD | Wh | SF: energy_sf |
Total imported real energyimported_energy | 440235 | 0x9D2A | uint32 | ABCD | Wh | SF: energy_sf |
Real energy scale factorenergy_sf | 440243 | 0x9D32 | int16 |
Common 6 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Meter manufacturermeter_manufacturer | 440124 | 0x9CBB | string | |||
Meter modelmeter_model | 440140 | 0x9CCB | string | |||
Meter optionmeter_option | 440156 | 0x9CDB | string | |||
Meter versionmeter_version | 440164 | 0x9CE3 | string | |||
Meter serial numbermeter_serial_number | 440172 | 0x9CEB | string | |||
Inverter Modbus IDmeter_device_address | 440188 | 0x9CFB | uint16 |
Meter 1 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Meter model IDmeter_model_id | 440189 | 0x9CFC | uint16 |
Power factor 2 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Average power factorpower_factor | 440222 | 0x9D1D | int16 | % | SF: power_factor_sf | |
Power factor scale factorpower_factor_sf | 440226 | 0x9D21 | int16 |
Source documents
- Technical Note: SolarEdge Inverters - SunSpec Logging , SolarEdge Technologies, 3.3 (October 2026) (accessed 2026-11-09) Register tables with base-0 addresses. The site sits behind a browser check, so a plain command-line download may get an HTML page instead.
- SunSpec information model 203 (json/model_203.json) , SunSpec Alliance, github.com/sunspec/models master @ 90b4a331dcca1d6eac69c1bead952fddcc5852e0 (accessed 2026-11-09) Point types (scale factors are sunssf, int16) for the model the technical note references.
Read it by name
Read the Meter via Inverter with an AI assistant
The Proxus Industrial MCP Server includes this map. Set it on the device, and Claude, Cursor or VS Code reads registers by key with the right type, byte order, scale and unit. It only reads.
proxus-mcp.json
{
"devices": {
"meter-1": {
"protocol": "modbus-tcp",
"host": "192.168.10.40",
"unit_id": 1,
"map": "solaredge/meter-via-inverter"
}
}
} Ask your assistant
Read ac_current, ac_current_a, ac_current_b from meter-1.
The tool call it makes
read_named(device: "meter-1", keys: ["ac_current", "ac_current_a", "ac_current_b"]) Have this device? Verify the map.
Ask your assistant to run verify_device_map. It reads every register once, read-only, checks that the values are plausible and asks you to compare two values with the display. You get a report and a prefilled GitHub issue to submit; your name goes on this map’s verified list.
Collecting from many devices?
Proxus reads Modbus TCP and RTU devices next to the machines, keeps the history and delivers the values to dashboards, databases and AI.