GoodWe Grid-Meter
The GoodWe Grid-Meter is a virtual metering component embedded in GoodWe ET and EH series hybrid inverters, exposing grid-side measurements through the inverter's Modbus TCP interface. This template reads the meter communication status flag, per-phase grid frequencies for all three phases (R, S, T), and the total active grid power. A negative value on total active power indicates import from the grid; a positive value indicates export. Using the ModbusCloud Gateway, installers can log these values continuously and trigger alerts when frequency or power deviates from expected limits.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 5, read only
- Brand
- GoodWe
- Last updated
Registers (5)
5 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| has_no_meter | Read | ||||
| f_grid_r | Hz | Read | |||
| f_grid_s | Hz | Read | |||
| f_grid_t | Hz | Read | |||
| p_grid_t | W | Read |
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 total active grid power to verify that the inverter is neither importing nor exporting beyond contracted limits.
- Track per-phase grid frequencies across R, S, and T to detect grid instability or asymmetric supply conditions.
- Alert on the meter communication status flag dropping to zero, indicating a lost connection between inverter and smart meter.
- Compare phase frequencies over time to identify recurring grid disturbances at a specific site or time of day.
- Report continuous grid power readings to a building owner for monthly energy balance reconciliation.
Installation
Enable Modbus TCP on the GoodWe inverter by navigating to the communication or network settings in the SolarGo app or the inverter web interface, and confirm the ARM firmware is version 13 or higher.
Connect the GoodWe inverter's LAN port to the same local network as the ModbusCloud Gateway using a standard Ethernet cable, and note the inverter's IP address.
In the ModbusCloud portal, add a new device, select the Modbus TCP protocol, enter the inverter's IP address and port 502, then import the GoodWe Grid-Meter template and assign the correct unit ID (default 247 for GoodWe inverters).
Verify the setup by reading the has_no_meter register (address 36004): a value of 1 confirms the smart meter is communicating correctly with the inverter before relying on power readings.
Things to watch for
Why does has_no_meter always return 0?
A value of 0 means the inverter reports the meter as not communicating. Check the physical RS-485 wiring between the GoodWe smart meter and the inverter's meter port, confirm the meter's Modbus address matches the inverter's meter configuration, and ensure no address conflict exists on the RS-485 bus.
Frequency registers return values that seem 100 times too high. Why?
The GoodWe ET protocol applies a scaling factor of 100 to frequency registers. A raw value of 5000 represents 50.00 Hz. If your portal or SCADA system is displaying raw counts, apply a divisor of 100 to convert to Hz. Confirm this in your channel scaling configuration.
The gateway connects on port 502 but all registers return errors. What now?
GoodWe Modbus TCP requires a LAN module fitted to the inverter and ARM firmware version 13 or higher. Verify the firmware version in the SolarGo app. Also confirm the unit ID is set to 247 (the GoodWe default) and that no firewall rule on the local network is blocking port 502.
p_grid_t reads a large positive number unexpectedly at night. Is this correct?
A large positive value at night, when no PV generation is active, is plausible and indicates the site is exporting stored battery energy to the grid. If the value seems physically implausible (outside the inverter's rated power), check for byte-order mismatch: the register is int32 and requires big-endian word order, which is the GoodWe default.
Want to see how it works?
