Webasto Next Wallbox

Use cases

• Monitor real-time charging power and per-phase currents on a live dashboard for each customer site.
• Create an alert when the EVSE state indicates a fault or unexpected disconnection.
• Remotely start or cancel a charging session without physical access to the wallbox.
• Set dynamic current limits based on available grid capacity to support simple load management.
• Track total energy consumption per charging session for billing or reporting purposes.
• Verify that the LifeBit is being sent correctly by monitoring communication timeout status.

Installation

1. 1Connect the Webasto Next Wallbox to the same local network as your ModbusCloud gateway (MCG or MLP series) via Ethernet.
2. 2Open the Webasto Next WebUI, activate the expert view, and enable Modbus TCP communication under the HEMS settings.
3. 3Note the IP address of the wallbox and confirm it is reachable from the gateway using a ping test.
4. 4In the ModbusCloud portal, assign the Webasto Next template to your gateway and enter the wallbox IP address and Modbus TCP port (default 502).
5. 5Configure the comTimeout (register 2002) and safeCurrent (register 2000) values to match your site requirements.
6. 6Verify that live data appears on the ModbusCloud dashboard and test a charging session start and stop from the control interface.

Things to watch for

01

Why does the wallbox revert to safeCurrent and stop responding to my commands?

The LifeBit (register 6000) must be written at least every half of the comTimeout interval. If it is missed, the wallbox falls back to safeCurrent. Check your gateway connection stability and ensure the write interval is correctly configured.

02

Why does the Charged Energy register always show zero during charging?

Register 1502 only returns a value after the charging session is fully completed. During an active session it reads zero. Use the Energy Meter register for real-time consumption data.

03

I set a power value in registers 5000 and 5001 but the wallbox ignores it. Why?

Register 5004 (Current) is dominant. If it contains a non-zero value, registers 5000 and 5001 are ignored. Clear register 5004 first if you want to control by power.

04

Register 5000 returns incorrect values. What could be wrong?

Register 5000 is a uint32 that requires swapped register order as of firmware v1.0.4. Verify your firmware version and confirm the byte or word swap setting in the template matches.

Registers (21)

20 read / 5 write

More Webasto templates

Webasto Live Wallbox

Webasto

Modbus TCP

Controls and monitors Webasto Live EV wallbox charging via Modbus TCP.

30 registers75

Webasto Unite 11kW

Webasto

Modbus TCP

Controls and monitors Webasto Unite 11kW wallbox charging via Modbus TCP.

6 registers1

Webasto Next

Webasto

Modbus TCP

29 registers

Webasto Unite

Webasto

Modbus TCP

41 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