Tepto Avocado Pro (battery)
The Tepto Avocado Pro is a FoxESS-based all-in-one balcony solar storage system combining an integrated inverter with a modular lithium battery, designed for residential and small-scale self-consumption applications. This ModbusCloud template communicates over Modbus TCP and reads instantaneous battery power, cumulative energy throughput, and state of charge. It also exposes a set of write registers for battery mode selection and a signed power setpoint, enabling charge and discharge control from the portal. Use this template to monitor the Avocado, MQ2200, ONE, or Avocado Pro and verify that storage operation matches your self-consumption or dynamic-tariff strategy.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 8, read and write
- Brand
- Tepto
- Compatible models
- Avocado · MQ2200 · ONE · Avocado Pro
- Last updated
Registers (8)
3 read, 5 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| soc | % | Read | |||
| batterymode_a | Write | ||||
| batterymode_b | Write | ||||
| batterymode_c | Write | ||||
| batterymode_e | Write | ||||
| batterymode_f | W | Write |
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 battery state of charge continuously to detect gradual capacity fade across seasons.
- Track cumulative energy throughput to verify expected charge cycles against manufacturer specifications.
- Alert on sustained high or low power readings to identify inverter clipping or load imbalances.
- Verify that batterymode setpoints are applied correctly after remote mode changes from the portal.
- Report daily self-consumption shifts by comparing discharge power against household consumption periods.
Installation
Connect 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.
Connect the ModbusCloud Gateway to the same LAN segment as the Avocado Pro, ensuring both devices obtain IP addresses from the same router or switch.
In 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.
Spot-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
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.
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.
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.
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.
Want to see how it works?
