Skip to main content

Home Assistant

Introduction

Your WARP Charger or WARP Energy Manager is compatible with Home Assistant. Home Assistant is an open-source home automation solution with broad device support.

For connecting WARP devices, Modbus and MQTT can be used. In this guide, we will use MQTT. Furthermore, it is assumed that Home Assistant is already installed and operational. Instructions for this can be found on the official website.

MQTT

Setting up MQTT in Home Assistant

First, MQTT must be activated in Home Assistant. Go to Settings -> Devices & Services -> Add Integration in the web interface. In the window that opens, search for "MQTT" and select it. Various MQTT integrations are available. We need the simple MQTT integration:

MQTT Integration Selection

You will then be asked about the MQTT broker. If you don't want to use your own MQTT broker, the easiest way is to use the official MQTT broker app. This is installed automatically.

MQTT Broker Selection

warning

If Home Assistant was installed as a Docker container, adding apps via the web interface is not possible. In this case, the MQTT broker must be installed and configured separately. Installation in a Docker container is therefore only recommended for advanced users.

MQTT Broker install success

Finally, go to Settings -> Apps -> Mosquitto broker -> Configuration and create a login there. Here you can also find the ports for the various MQTT protocols.

Don't forget to save!

MQTT Broker Login creation

Setting up MQTT in WARP Charger/WARP Energy Manager

The MQTT broker is configured in the MQTT settings according to the Introduction.

For automatic integration into Home Assistant, set the Discovery mode to "Home Assistant/openHAB/Domoticz/FHEM". HA Autodiscovery The discovery topic prefix defaults to homeassistant and must match the Home Assistant configuration. It must differ from the MQTT API topic prefix.

Discovery messages are sent when discovery starts and then every 15 minutes, and are retained by the broker. After each discovery round, the associated states are also resent so that Home Assistant evaluates the current values using the new sensor definitions.

MQTT Sensor Values in Home Assistant via Autodiscovery

Autodiscovery automatically adds various sensors and controls. Which ones are added depends on whether the device is a WARP Charger or WARP Energy Manager and which functions are activated (e.g. solar forecast).

Autodiscovery removes automatically added entities if the corresponding function is disabled or the configured meter no longer supports the measured value. Disabling discovery or changing the discovery topic prefix deletes the previous discovery messages.

When MQTT is configured for read-only access (read_only), controls are unavailable. To control the charging current limit, External control must also be enabled under Charger → Settings.

Automatically Added Entities

The following entities are provided via autodiscovery:

NameTypeDescriptionAvailable when
Charge stateSensorNumeric charge state: 0 = Not connected, 1 = Waiting for release, 2 = Ready to charge, 3 = Charging, 4 = ErrorEVSE present (WARP Charger)
Charge state (text)SensorThe same charge state as localized text (enum)EVSE present (WARP Charger)
Current charge mode EVSESensorCharger mode as localized text, including Default modeEVSE present (WARP Charger)
Charging current limitNumberMaximum charging current in A (0–32 A), controllableEVSE present (WARP Charger)
Allowed charging currentSensorCurrently allowed charging current in AEVSE present (WARP Charger)
Start chargingButtonStarts the charging processEVSE present (WARP Charger)
Stop chargingButtonStops the charging processEVSE present (WARP Charger)
Charging cable connectedBinary SensorIndicates whether a charging cable is connectedEVSE present (WARP Charger)
Charger ready to chargeBinary SensorIndicates whether the charger is ready to chargeEVSE present (WARP Charger)
Charger chargingBinary SensorIndicates whether charging is currently in progressEVSE present (WARP Charger)
Charger errorBinary SensorIndicates whether an error is presentEVSE present (WARP Charger)
Charger availableBinary SensorIndicates whether the charger is reachableEVSE present (WARP Charger)
Front button pressedBinary SensorIndicates whether the front button is pressedEVSE present (WARP Charger)
Limited according to §14a EnWGSensorIndicates whether a limitation according to §14a EnWG is active§14a EnWG activated in the configuration
Active charge modeSelectSelect charge mode; offers only the currently supported modes (see below)Charge management enabled and selectable charge modes available
Current charge modeSensorActive charge management mode as localized textCharge management enabled
Solar forecast tomorrowSensorForecasted PV yield for tomorrow in kWhSolar forecast activated
Solar forecast todaySensorForecasted PV yield for today in kWhSolar forecast activated
Solar forecast from nowSensorRemaining forecasted PV yield for today in kWhSolar forecast activated
Electricity market priceSensorCurrent spot market electricity price in ct/kWhDynamic electricity prices activated

The numeric Charge state sensor retains its original discovery ID chargerstate. The additional text sensor uses chargerstate_text.

Charge Modes

The Active charge mode selector follows the supported modes reported by charge management and matches the available modes in the web interface:

Enabled functionsSelectable charge modes
Neither PV excess charging nor EcoFast, Off
PV excess chargingFast, Off, PV, Min + PV
EcoFast, Off, Eco, Eco + Min
PV excess charging and EcoFast, Off, PV, Eco + PV

Discovery is resent when the list of supported modes changes. The Current charge mode and Current charge mode EVSE sensors can additionally display Min, Eco + Min + PV, and Default mode. Default mode is not a selectable mode.

Vehicle Data (WARP4)

WARP4 additionally provides the following sensors:

NameDescriptionUnit
Vehicle nameName of the recognized vehicle-
Vehicle MAC AddressMAC address of the recognized vehicle-
Vehicle State of ChargeState of charge of the vehicle battery%
Vehicle Battery CapacityCapacity of the vehicle batterykWh

Vehicle sensors are only available when a vehicle MAC address has been detected. Missing state of charge or battery capacity values are shown as unknown. Vehicle name and MAC address are read-only sensors.

Meter Values

The legacy meter sensors retain their original discovery IDs when the device provides the corresponding meter features:

NameDiscovery IDDescriptionUnit
Power drawpowernowCurrent power from meter/valuesW
Energy consumption (absolute)energyabsAbsolute energy reading from meter/valueskWh
Energy consumption (relative)energyrelEnergy reading since the last reset from meter/valueskWh
Current L1 / L2 / L3current_l1 / current_l2 / current_l3Phase currents from meter/all_values, if availableA

Additionally, the following measured values are provided for each configured meter slot if supported by that meter. Entity names include the configured meter name. The value ID identifies the measurement in the meter API:

NameValue IDDescriptionUnit
Voltage (L1-N / L2-N / L3-N)1 / 2 / 3Voltage of each phase against neutralV
Current (draw minus feed) (L1 / L2 / L3)14 / 18 / 22Signed current per phaseA
Active power (draw minus feed) (Σ L1, L2, L3)74Total active powerW
Active energy (draw) (Σ L1, L2, L3; since manufacturing)209Absolute imported active energy readingkWh
Active energy (feed) (Σ L1, L2, L3; since manufacturing)211Absolute exported active energy readingkWh
DC voltage10DC voltageV
DC current35DC currentA
DC power160DC powerW
DC energy (draw) (since manufacturing)405Absolute DC energy importkWh
DC energy (feed) (since manufacturing)407Absolute DC energy exportkWh
DC voltage (⌀ PV)430Average PV DC voltageV
DC current (feed) (Σ PV)441Total PV DC currentA
DC power (draw minus feed) (Σ PV)453Total PV DC powerW
DC energy (feed) (Σ PV; since manufacturing)472Absolute PV energy yieldkWh
State of charge387Battery state of charge%
Capacity475Battery capacitykWh
Frequency (⌀ L1, L2, L3)364Grid frequencyHz
note

The localization of the entities depends on the language of the web interface of the WARP Charger/WARP Energy Manager.