Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
/ openwbmqtt Public archive

Custom component for home assistant supporting openWB wallbox

Notifications You must be signed in to change notification settings

a529987659852/openwbmqtt

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Since openWB2 is out for some time, I archive this repo. Feel free to fork if you still need it.

If you're on openWB2, look here --> https://github.com/a529987659852/openwb2mqtt

openwbmqtt

Note: I provide this custom integration without any warranty. It lies in the responsability of each user to validate the functionality with his/her own openWB!

Custom component for home assistant supporting openWB wallbox wallbox for charging electric vehicles. The integration subscribes to MQTT topics prefix/<various values> which are used by openwb to broadcast information and displays this informations as sensor entities. In addition, the integration provides services that execute actions on the openwb (for example enable/disable a charge point).

If you need help, also have a look here: http://tech-engineering.de/home-assistant-und-openwb/

How to add this custom component to home assistant

Step 1: Deploy the Integration Coding to HA

Option 1: Via HACS

Make sure you have HACS installed. Under HACS, choose Integrations. Add this repository as a user-defined repository.

Option 2: Manually

Step 1: Clone component

Clone the custom component to your custom components folder.

Step 2: Restart HA

Restart your HA instance as usual.

Step 3: Add the Integration

In HA, choose Settings -> Integrations -> Add Integration to add the integration. HA will display a configuration window. For details, see next section. If the integration is not displayed, it may help to refresh your browser cache.

Configuration of the Integration and Additional Information

The integration subscribes to MQTT topics prefix/<various values> which are used by openwb to broadcast information.

The first parameter, mqttroot, defines the prefix that shall be applied to all MQTT topics. By default, openWB publishes data to the MQTT topic openWB/# (for example openWB/lp/1/%Soc). In this case, set the prefix to openWB and the integration will subscribe to MQTT data coming from openWB, for example openWB/lp/1/%Soc, or openWB/global/chargeMode, and so on.

The second parameter, chargepoints, is the number of configured charge points. For each charge point, the integration will set up one set of sensors.

Mosquitto Configuration in an Internal Network

If you're in an internal network, for example your home network, you can simply subscribe the openWB mosquitto server with the mosquitto server you're using with home assistant. No bridge settings in Home Assistant are required. Instead, add the following to the configuration (for example in /etc/mosquitto/conf.d/openwb.conf or /share/mosquitto/mosquitto.conf):

#
# bridge to openWB Wallbox
#
connection openwb
address openwb.fritz.box:1883
start_type automatic
topic openWB/# in 2
topic openWB/set/ChargeMode both 2
topic openWB/config/set/pv/minCurrentMinPv
topic openWB/set/lp/1/ChargePointEnabled both 2
topic openWB/set/lp/2/ChargePointEnabled both 2
topic openWB/config/set/sofort/lp/1/chargeLimitation both 2
topic openWB/config/set/sofort/lp/2/chargeLimitation both 2
topic openWB/config/set/sofort/lp/1/current both 2
topic openWB/config/set/sofort/lp/2/current both 2
topic openWB/config/set/sofort/lp/1/energyToCharge both 2
topic openWB/config/set/sofort/lp/2/energyToCharge both 2
topic openWB/config/set/sofort/lp/1/socToChargeTo both 2
topic openWB/config/set/sofort/lp/2/socToChargeTo both 2
topic openWB/set/lp/1/%Soc both 2
topic openWB/set/lp/2/%Soc both 2
local_clientid openwb.mosquitto
try_private false
cleansession true

If using the mqtt configuration above, mqttroot is openWB (this is the default value). Don't add a '/'.

If your're publishing the data from the openWB mosquitto server to another MQTT server via a bridge, the topics on the other MQTT server are usually prepended with a prefix. If this is the case, also include this prefix into the first configuration parameter, for example somePrefix/openWB. Then, the integration coding will subscribe to MQTT data comfing from MQTT, for example somePrefix/openWB/global/chargeMode, or somePrefix/openWB/lp/1/%Soc, and so on.