FoxESS Avocado (grid)
The FoxESS Avocado is a compact all-in-one hybrid battery storage and inverter system sold under several names, including the MQ2200 and ONE. This template targets the grid metering registers exposed over Modbus TCP on port 502, covering combined grid active power, cumulative energy, and per-phase voltages and currents for all three phases. With the ModbusCloud Gateway connected to the same LAN, your portal shows live import and export power, phase-level voltage balance, and a running energy total, giving installers the data needed to verify grid interaction at a glance.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 8, read only
- Brand
- FoxESS
- Compatible models
- Avocado · MQ2200 · ONE · Avocado Pro
- Last updated
Registers (8)
8 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| voltages_a | V | Read | |||
| voltages_b | V | Read | |||
| voltages_c | V | Read | |||
| currents_a | A | Read | |||
| currents_b | A | Read | |||
| currents_c | A | 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 real-time grid import and export power to verify self-consumption performance against design targets.
- Track cumulative grid energy over time to detect unexpected consumption increases across billing periods.
- Alert on per-phase voltage deviation to identify grid imbalance or supply quality issues early.
- Compare phase currents across A, B, and C to spot unbalanced load distribution in three-phase installations.
- Verify that grid active power reads negative during peak PV generation to confirm correct export operation.
Installation
Ensure the FoxESS Avocado, MQ2200, ONE, or Avocado Pro is connected to your local network via its built-in LAN or WLAN interface; Modbus TCP is active on port 502 by default with no additional configuration required.
Connect the ModbusCloud Gateway to the same LAN segment as the device, confirm it has IP connectivity, and note the inverter IP address assigned by your router via DHCP, as no static IP setting is available in the device web UI.
In the ModbusCloud portal, add a new device, select the FoxESS Avocado (grid) template, enter the inverter IP address, set port to 502, and set the Modbus unit ID to 1.
After saving, open the live register view and spot-check the power register (address 39168): a negative value indicates active export, a positive value indicates grid import; if the value reads zero with no other activity, verify no other Modbus client is connected simultaneously.
Things to watch for
The gateway connects but the power register always reads zero. Why?
Some FoxESS firmware versions respond with unit ID 0 instead of the requested unit ID 1, which causes clients to discard the response. Try setting the Modbus unit ID in the portal to 0 instead of 1. If a second Modbus client such as Home Assistant or openHAB is polling the device at the same time, disconnect it during testing, as the device only handles one TCP connection at a time.
Phase voltage values look ten times too high. What is wrong?
The FoxESS Modbus protocol applies a gain of 10 to the voltage registers at addresses 39123 to 39125. If your integration or display layer does not apply this scaling, readings will appear inflated by a factor of ten. Confirm that the template's scaling factor is set to divide by 10 before displaying or alerting on voltage values.
Current registers return implausible values despite correct addressing. What now?
The phase current registers are 32-bit signed integers with a documented gain of 1000, meaning raw values represent milliamps. Some FoxESS models shift the useful data to the second word of the 32-bit pair, making the first word read as zero. If values are implausible, verify that your Modbus client reads both words and assembles them as a big-endian int32.
The energy register shows a lower number than the FoxESS app. Is the data wrong?
The energy register at address 39625 is a raw unsigned 32-bit counter internal to the inverter register map. It may represent a different energy accumulation boundary, such as a subset of grid energy, compared to what the FoxESS cloud app derives from additional registers. Use the value for trend monitoring and relative comparisons rather than as an absolute billing figure.
Want to see how it works?
