SolarEdge SunSpec Inverter Modbus register map
Also searched as: SolarEdge inverter · SE3000 · SE5000 · SE10K · SolarEdge Home Wave
41 Modbus registers of the SolarEdge SunSpec 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)).
SolarEdge single, split and three phase inverters through their SunSpec Modbus interface (models 1 and 101/102/103).
- Device type
- Solar inverter
- Registers
- 41
- Interfaces
- Modbus TCP, Modbus RTU
- Byte order (multi-register values)
- ABCD
- Serial settings
- 115200 baud, 8 data bits, no parity, 1 stop bit
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 with function 03. Registers are big-endian; 32-bit values are high word first.
- Value = raw x 10^scale_factor; the scale factors can change, so read them with the value.
- Inverters set up with SetApp/SolarEdge Go support SunSpec; LCD models need firmware 3.xxxx or later.
- Modbus TCP works over LAN only (not Wi-Fi); the TCP server closes idle connections after two minutes.
- Unsupported values read as the SunSpec NOT_IMPLEMENTED value.
Registers
Grouped as in the vendor document.
Inverter 35 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
Inverter model IDinverter_model_id | 440070 | 0x9C85 | uint16 | |||
AC total currentac_current | 440072 | 0x9C87 | uint16 | A | SF: ac_current_sf | |
AC phase A currentac_current_a | 440073 | 0x9C88 | uint16 | A | SF: ac_current_sf | |
AC phase B currentac_current_b | 440074 | 0x9C89 | uint16 | A | SF: ac_current_sf | |
AC phase C currentac_current_c | 440075 | 0x9C8A | uint16 | A | SF: ac_current_sf | |
AC current scale factorac_current_sf | 440076 | 0x9C8B | int16 | |||
AC voltage phase ABac_voltage_ab | 440077 | 0x9C8C | uint16 | V | SF: ac_voltage_sf | |
AC voltage phase BCac_voltage_bc | 440078 | 0x9C8D | uint16 | V | SF: ac_voltage_sf | |
AC voltage phase CAac_voltage_ca | 440079 | 0x9C8E | uint16 | V | SF: ac_voltage_sf | |
AC voltage phase A to Nac_voltage_an | 440080 | 0x9C8F | uint16 | V | SF: ac_voltage_sf | |
AC voltage phase B to Nac_voltage_bn | 440081 | 0x9C90 | uint16 | V | SF: ac_voltage_sf | |
AC voltage phase C to Nac_voltage_cn | 440082 | 0x9C91 | uint16 | V | SF: ac_voltage_sf | |
AC voltage scale factorac_voltage_sf | 440083 | 0x9C92 | int16 | |||
AC powerac_power | 440084 | 0x9C93 | int16 | W | SF: ac_power_sf | |
AC power scale factorac_power_sf | 440085 | 0x9C94 | int16 | |||
AC frequencyac_frequency | 440086 | 0x9C95 | uint16 | Hz | SF: ac_frequency_sf | |
AC frequency scale factorac_frequency_sf | 440087 | 0x9C96 | int16 | |||
Apparent powerac_va | 440088 | 0x9C97 | int16 | VA | SF: ac_va_sf | |
Apparent power scale factorac_va_sf | 440089 | 0x9C98 | int16 | |||
Reactive powerac_var | 440090 | 0x9C99 | int16 | var | SF: ac_var_sf | |
Reactive power scale factorac_var_sf | 440091 | 0x9C9A | int16 | |||
Power factorac_pf | 440092 | 0x9C9B | int16 | % | SF: ac_pf_sf | |
Power factor scale factorac_pf_sf | 440093 | 0x9C9C | int16 | |||
AC lifetime energy productionac_energy_wh | 440094 | 0x9C9D | uint32 | ABCD | Wh | SF: ac_energy_wh_sf |
AC energy scale factorac_energy_wh_sf | 440096 | 0x9C9F | int16 | |||
DC currentdc_current | 440097 | 0x9CA0 | uint16 | A | SF: dc_current_sf | |
DC current scale factordc_current_sf | 440098 | 0x9CA1 | int16 | |||
DC voltagedc_voltage | 440099 | 0x9CA2 | uint16 | V | SF: dc_voltage_sf | |
DC voltage scale factordc_voltage_sf | 440100 | 0x9CA3 | int16 | |||
DC powerdc_power | 440101 | 0x9CA4 | int16 | W | SF: dc_power_sf | |
DC power scale factordc_power_sf | 440102 | 0x9CA5 | int16 | |||
Heat sink temperatureheat_sink_temperature | 440104 | 0x9CA7 | int16 | °C | SF: temperature_sf | |
Temperature scale factortemperature_sf | 440107 | 0x9CAA | int16 | |||
Operating statestatus | 440108 | 0x9CAB | uint16 | |||
Vendor operating statestatus_vendor | 440109 | 0x9CAC | uint16 |
Common 6 registers
| Name and key | Reference | Address | Type | Byte order | Unit | Scale |
|---|---|---|---|---|---|---|
SunSpec ID ("SunS")sunspec_id | 440001 | 0x9C40 | uint32 | ABCD | ||
Manufacturermanufacturer | 440005 | 0x9C44 | string | |||
Modelmodel | 440021 | 0x9C54 | string | |||
CPU software versionversion | 440045 | 0x9C6C | string | |||
Serial numberserial_number | 440053 | 0x9C74 | string | |||
Modbus unit IDdevice_address | 440069 | 0x9C84 | uint16 |
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 103 (json/model_103.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 SunSpec 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": {
"sunspec-1": {
"protocol": "modbus-tcp",
"host": "192.168.10.40",
"unit_id": 1,
"map": "solaredge/sunspec-inverter"
}
}
} Ask your assistant
Read ac_current, ac_current_a, ac_current_b from sunspec-1.
The tool call it makes
read_named(device: "sunspec-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.