Tepto Avocado Pro (pv)

Installation

1. 1Ensure the Avocado Pro is connected to your local network via its RJ45 Ethernet port, then verify Modbus TCP is active on port 502 with Unit-ID 1 under the device web interface or FoxESS app communication settings.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the Avocado Pro so it can reach the device at its assigned IP address on port 502.
3. 3In the ModbusCloud portal, add a new device, import the Tepto Avocado Pro (pv) template, and set the Unit ID to 1 and the target IP to the Avocado Pro's local address.
4. 4After saving, open the live register view and confirm that address 39118 returns a plausible watt value during daylight; if the field reads zero at night, that is expected normal behaviour.

Things to watch for

01

The gateway connects but both registers return zero. Why?

At night or when PV input is absent the power register legitimately reads zero. Confirm by checking the value during daylight. If it remains zero in full sun, verify the Unit-ID is set to 1 and that the Avocado Pro's Modbus TCP service is enabled in the communication section of its web interface.

02

I get an 'illegal function' exception on function code 3. What now?

This error is reported by some Avocado Pro firmware versions when Modbus TCP access has not yet been unlocked. Check that the device firmware is up to date and that no access restriction is active in the FoxESS app or device web interface. Some units require the local API to be explicitly enabled.

03

The energy register value looks unexpectedly large. Is the scaling correct?

The energy register at address 39149 is a uint32 with no unit field defined in this template. Cross-check the raw value against the reading shown in the FoxESS app. If the magnitude is off by a factor of 10 or 100, a scaling divisor may apply specific to your firmware version; consult the register documentation available under NDA from Tepto or FoxESS.

04

The ModbusCloud Gateway cannot reach the device on port 502. What should I check?

Confirm the Avocado Pro and the Gateway are on the same LAN or VLAN and that no firewall blocks port 502. The device communicates over Modbus TCP with Unit-ID 1, so also verify the IP address has not changed due to DHCP reassignment. Assigning a static IP or DHCP reservation to the Avocado Pro avoids this recurring issue.

Registers (2)

2 read / 0 write

More Tepto templates

Tepto Avocado Pro (battery)

Tepto

Modbus TCP

8 registers

Tepto Avocado Pro (grid)

Tepto

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

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers