Webasto Webasto Unite Modbus TCP template

Webasto Unite

The Webasto Unite is an AC EV wallbox delivering up to 22 kW over one or three phases, designed for residential, fleet, and commercial charging installations. This ModbusCloud template connects via Modbus TCP and reads charge point state, cable state, per-phase current and voltage, active power on all three phases, session energy, and session timestamps. Write registers let your energy management system set the charging current and keepalive in real time. The template gives installers and facility managers live visibility and dynamic load control without additional hardware.

Protocol
Modbus TCP
Connection
Ethernet, Modbus TCP
Registers
41, read and write
Brand
Webasto
Last updated

Registers (41)

37 read, 4 write

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
serial_numberRead
charge_point_idRead
brandRead
modelRead
firmware_versionRead
dateRead
timeRead
charge_point_powerWRead
number_of_phasescountRead
charge_point_stateRead
charging_stateRead
equipment_stateRead
cable_stateRead
evse_fault_codeRead
current_l1ARead
current_l2ARead
current_l3ARead
voltage_l1VRead
voltage_l2VRead
voltage_l3VRead
active_powerWRead
active_power_l1WRead
active_power_l2WRead
active_power_l3WRead
meter_readingkWhRead
session_max_currentARead
evse_min_currentARead
evse_max_currentARead
cable_max_currentARead
energy_sessionkWhRead
session_start_timeRead
session_durationsRead
session_end_timeRead
failsafe_current_aARead
failsafe_timeout_asRead
charging_current_aARead
alive_register_aRead
failsafe_current_bAWrite
failsafe_timeout_bsWrite
charging_current_bAWrite
alive_register_bWrite

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.

Number of installations (optional)

Use cases

  • Monitor per-phase current and voltage on the Webasto Unite to verify balanced three-phase load distribution across a site.
  • Track session energy and session duration per charge event to generate accurate cost-reimbursement reports for fleet drivers.
  • Alert on non-zero evse_fault_code values to detect wallbox faults before drivers report failed charging attempts.
  • Compare active_power against site capacity limits to verify the dynamic load management setpoint is respected.
  • Verify charge_point_state and cable_state transitions to confirm a vehicle has connected and charging has started correctly.

Installation

  1. Enable Modbus TCP on the Webasto Unite using the Webasto Charger Setup App or the built-in web configuration interface under the communication or Modbus section; confirm port 502 is active.

  2. Connect the wallbox to the same LAN segment as the ModbusCloud Gateway using a standard Ethernet cable, then assign the wallbox a static IP address or DHCP reservation.

  3. In your ModbusCloud portal, add the Gateway, then import the Webasto Unite template and assign the wallbox IP address, port 502, and unit ID 255.

  4. Spot-check live values by reading charge_point_state and active_power in the portal dashboard; both should update within one polling cycle when a vehicle is connected.

Things to watch for

All registers read zero even though the wallbox is powered.

Confirm Modbus TCP is explicitly enabled in the wallbox communication settings. The factory default may have Modbus disabled. Also verify unit ID is set to 255, which is the standard unit identifier for this device family. A mismatch will return no data.

The gateway connects but string registers show garbled characters.

String registers such as serial_number and firmware_version are encoded as multi-register ASCII blocks. Ensure the template is reading the correct number of consecutive registers for each string field and that your client is assembling them in big-endian byte order, as used by this device.

The wallbox drops to its failsafe current after a few minutes.

The Webasto Unite requires the Modbus master to periodically write to the alive_register_b (address 6000) to signal the connection is still live. If that keepalive write stops, the device falls back to the failsafe_current value after the failsafe_timeout expires. ModbusCloud writes registers at most once per minute, so control through ModbusCloud needs a failsafe_timeout well above one minute. With a shorter timeout it is not possible, while reading values works.

Is it safe to write any value to charging_current_b at any time?

No. Writing a charging current value outside the range bounded by evse_min_current and evse_max_current can cause the session to abort or the EVSE protection to trip. Always read the current limits first and clamp your setpoint within them. Uncontrolled writes may also affect warranty coverage, so test changes carefully in a controlled environment.

Want to see how it works?

Electrician working in an open distribution board