FoxESS Avocado (battery)

Installation

1. 1Enable Modbus TCP on the Avocado by connecting it to your local network via LAN or WLAN and confirming the device is reachable on port 502; verify connectivity with a telnet or TCP probe to port 502 before proceeding.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the Avocado, ensuring no firewall or VLAN blocks port 502 between the Gateway and the storage unit.
3. 3In the ModbusCloud portal, add a new device, import the FoxESS Avocado (battery) template, and assign Unit ID 1 (the factory default for this device).
4. 4Spot-check the soc register at address 39424 in the live register view to confirm a plausible 0 to 100 value is being returned before enabling any write registers.

Things to watch for

01

Why do the power or energy registers return zero or garbage?

The power register at address 39237 is typed as int32 and spans two consecutive 16-bit holding registers. If your polling tool requests only one register or decodes it as int16, the result will be zero or nonsense. Ensure the template uses a two-register int32 read for that address. Firmware version also affects register availability, so update to the latest Master and Manager firmware before troubleshooting further.

02

The Gateway connects on port 502 but no values appear. What now?

The Avocado obtains its IP address via DHCP, so the address may have changed after a router restart. Confirm the current IP in your router's DHCP lease table, update the device address in the ModbusCloud portal, and retry. If the TCP connection is refused, check that no other Modbus master (such as a home-automation controller) is holding an exclusive connection to port 502, as the device may reject additional clients.

03

Register 46001 was written but the battery mode did not change.

Register 46001 is a bitfield where bit 0 must be set to 1 to enable remote control, bit 1 sets the power direction, and bit 2 selects the controlled target. Writing only a partial value without asserting the enable bit has no effect. Also confirm that register 46002 (timeout) is set to a nonzero value, otherwise the command expires immediately.

04

Is it safe to write power setpoints via batterymode_f during normal operation?

Use write registers with caution. Sending an active power command via batterymode_f (address 46003, int32, watts) overrides the device's built-in charge and discharge logic. Commands outside the battery's rated power range may trigger protection responses or thermal limits. Always test with small incremental values, ensure the timeout in batterymode_e is set appropriately so the device reverts automatically, and review your warranty terms before enabling continuous remote control.

Registers (8)

3 read / 5 write

More FoxESS templates

FOXESS

FoxESS

Modbus RTU

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

15 registers64

FoxESS H1 Series Hybrid Inverter (battery)

FoxESS

Modbus RTU

2 registers

FoxESS H3 Series Hybrid Inverter (grid)

FoxESS

Modbus RTU

4 registers

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

FoxESS

Modbus RTU

6 registers

FoxESS Avocado (pv)

FoxESS

Modbus TCP

2 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers

More TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

Atmoce MG100 M-gateway (battery)

Atmoce

Modbus TCP

6 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers