Tepto Avocado Pro (battery)

Installation

1. 1Connect the Tepto Avocado Pro to your local network via its built-in Wi-Fi or Ethernet port, then confirm that Modbus TCP is active on port 502 by verifying the device appears on your network and port 502 is reachable.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the Avocado Pro, ensuring both devices obtain IP addresses from the same router or switch.
3. 3In the ModbusCloud portal, add a new device, import the Tepto Avocado Pro (battery) template, and set the unit ID to 1, which is the default for this device.
4. 4Spot-check the soc register in the live data view: the value should read a plausible percentage; if it remains zero or shows an error, verify the IP address, port 502 accessibility, and unit ID.

Things to watch for

01

The gateway connects but soc and power always show zero.

This device is known to respond with unit ID 0 instead of the configured ID 1 in some firmware versions, causing a unit ID mismatch error. Try setting the unit ID in the ModbusCloud portal to 0 and retry. If the error changes to a successful read, keep ID 0 as the working value.

02

I get an 'illegal function' error when reading the energy register.

Some Avocado Pro firmware versions do not expose all holding registers on every firmware build. Confirm your device firmware is up to date via the FoxESS app or web interface. The energy register at address 39609 requires function code 3; if this address returns exception 1, the register may not be active in your firmware version.

03

Why is the power register showing unexpected negative values?

The power register is a signed int32. Negative values indicate the battery is actively charging, while positive values indicate discharge. This is expected behaviour. Check that your dashboard formula treats negative power as charge and positive as discharge when calculating self-consumption.

04

Is it safe to write batterymode registers remotely during operation?

Use caution when writing to batterymode registers (addresses 46001, 46002, 46003, 46609, 46610) during active charge or discharge cycles. Sending unsupported mode values or out-of-range power setpoints via batterymode_f can interrupt operation or trigger protection faults. Always test mode changes during low-load periods and confirm behaviour with the device's own app before automating writes.

Registers (8)

3 read / 5 write

More Tepto templates

Tepto Avocado Pro (grid)

Tepto

Modbus TCP

8 registers

Tepto Avocado Pro (pv)

Tepto

Modbus TCP

2 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

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers