FoxESS Avocado (pv)

Installation

1. 1Connect the Avocado to your local network via its LAN port or Wi-Fi, then confirm Modbus TCP is active by opening a TCP connection to the device's IP address on port 502. No separate Modbus enable step is required on most firmware versions.
2. 2Connect the ModbusCloud Gateway to the same network segment as the Avocado, ensuring no firewall rules block port 502 between the Gateway and the inverter IP address.
3. 3In the ModbusCloud portal, add a new device, import the FoxESS Avocado (pv) template, and set the unit ID to 1. Assign the Avocado's LAN IP address as the target host.
4. 4Trigger a manual poll in the portal and spot-check register 39118 against the live PV output shown on the Avocado's LED display or app to confirm correct data flow.

Things to watch for

01

The gateway connects but both registers read zero at midday.

Register 39118 reports total PV input power as a signed 32-bit integer scaled by 1000 (value in milliwatts divided by 1000 gives watts). If the raw value looks correct but the displayed figure is zero or implausibly small, verify that the portal template is decoding the register as int32 and not int16. Reading only the lower word of a 32-bit pair will return zero when the upper word is non-zero.

02

Modbus poll returns exception code 1 (illegal function) on register 39118.

The Avocado firmware on some variants restricts which register ranges respond to function code 3. Confirm you are using FC3 (holding registers) and that the unit ID is set to 1. Some firmware versions do not expose the full register map without a prior authentication or specific firmware update. Check the FoxESS Modbus protocol document version against your device firmware.

03

The gateway receives a response but the unit ID in the reply is 0, not 1.

A known behavior on certain Avocado firmware builds is that the device responds with unit ID 0 regardless of the requested ID. In the ModbusCloud Gateway configuration, enable the option to accept responses with unit ID 0, or set the configured unit ID to 0 and verify that readings then appear correctly.

04

Cumulative energy at register 39149 seems too low or resets unexpectedly.

Register 39149 stores cumulative generation as a uint32 value scaled by 100 (the raw value divided by 100 gives kWh). Ensure the template applies the correct scaling. A value that resets may indicate a firmware update that cleared non-volatile counters. Cross-check against the FoxESS app total generation figure to confirm baseline.

Registers (2)

2 read / 0 write

More FoxESS templates

FOXESS

FoxESS

Modbus RTU

Monitors a FoxESS 3-phase hybrid inverter with battery storage via Modbus RTU

15 registers64

FoxESS H3-Pro/Smart Series Hybrid Inverter (pv)

FoxESS

Modbus RTU

6 registers

FoxESS H1 Series Hybrid Inverter (battery)

FoxESS

Modbus RTU

2 registers

FoxESS Avocado (battery)

FoxESS

8 registers

FoxESS MQ2200 (battery)

FoxESS

8 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers

More TCP templates

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

SunSpec Model 135 — LFRT

SunSpec

Modbus TCP

11 registers

SunSpec Model 139 — LVRTX

SunSpec

Modbus TCP

12 registers

SMA StpSe Battery

SMA

Modbus TCP

16 registers

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers