< scroll down for English version and additional information >
wbec
WLAN-Anbindung der Heidelberg WallBox Energy Control über ESP8266
Die Heidelberg Wallbox Energy Control ist eine hochwertige Ladestation, bietet aber nur Modbus RTU als Schnittstelle.
Ziel des Projekts ist es, eine WLAN-Schnittstelle zu entwickeln, die gleichzeitig die Modbus-Leader-Funktion übernimmt.
Funktionen (bisher)
- Anbindung an openWB, EVCC, Solaranzeige (per tlw. Emulation der go-eCharger API)
- MQTT-Kommunikation mit openWB
- Steuerbar per Android App Wallbox Steuerung
- PV-Überschussladen, Zielladen, etc. mit den o.g. Steuerungen
- Ansteuerung aller verbundenen Ladestationen (bis zu 16 Follower am Modbus, bis zu 8 openWB-Ladepunkte)
- Lesen/Schreiben der Modbus-Register über ein JSON-Web-Interface
- Standby-Funktion der Ladestation einstellbar
- Einfacher Prototyp einer Webseite zur Steuerung
- Einfacher Prototyp eines lokalen Lastmanagements
- Softwareupdate per WLAN (Over The Air), z.B. mit PlatformIO oder einfach per Browser (s. Wiki)
- Access-Point-Modus zur initialen Einstellung des WLANs (SSID/Passwort, s. Wiki)
- Weniger als 1W Strombedarf (trotz Ansteuerung von bis zu 16 Ladestationen)
Kontakt
Bei Fragen gerne einfach eine Mail schicken ([email protected]) oder einen Issue eröffnen ;-)
Bei Interesse an einer fertig gelöteten/programmierten "ready-to-use" Black-Box bitte ebenfalls eine Mail schicken.
Bitte schaut auch ins Wiki.
wbec
Wifi interface to Heidelberg WallBox Energy Control using ESP8266
The Heidelberg Wallbox Energy Control is a high quality wallbox, but it offers only a Modbus RTU interface. Goal of this project is to establish an Wifi interface, which also acts as Modbus master.
Features (as of now)
- Works with openWB, EVCC, Solaranzeige (by emulation of parts of the go-eCharger API)
- Support of MQTT communication to openWB
- Support of Android App Wallbox Steuerung
- Prepared for supporting up to all 16 connected boxes (up to 8 openWB load points)
- Modbus registers can be read/written via JSON web interface
- Standby of Wallbox can be configured
- Simple prototype of a web interface
- Simple prototype of a local load management
- Update via WiFi (OTA), e.g. with PlatformIO or simply via Web browser (s. Wiki)
- Access point mode, to configure your WiFi network/password (s. Wiki)
- < 1W power consumption (for controlling up to 16 boxes)
Contact
In case of any questions, feel free to send a mail ([email protected]) or open an issue ;-)
When you're interested in a ready-to-use black-box, then please send a mail.
Please also take a look to the Wiki.
Pictures
Switch configuration of wallbox
S1 > 5 (16A max)
S2 = 0000
S3 = 0 (6A min)
S4 = 0001 (slave address, Bus-ID)
S5 = 0000
S6 = 0100 (terminator 120 Ohm, only on last box)
Examples
First simple web interface (might be removed again in future, as there are better alternatives with openWB, EVCC, ...):
Get current status (here for 2 configured wallboxes, but only 1 connected):
http://192.168.xx.yy/json
{
"wbec": {
"version": "v0.3.0" // wbec version
"bldDate": "2021-06-10" // wbec build date
},
"box": [
{ // s. also https://wallbox.heidelberg.com/wp-content/uploads/2021/04/EC_ModBus_register_table_20210222.pdf
"busId": 1, // Modbus bus id (as configured by DIP switches)
"version": "108", // Modbus Register-Layouts Version, e.g. 1.0.8
"chgStat": 2, // Charging State
"currL1": 0, // L1 - Current RMS (in 0.1A)
"currL2": 0, // L2 - Current RMS (in 0.1A)
"currL3": 0, // L3 - Current RMS (in 0.1A)
"pcbTemp": 333, // PCB-Temperatur (in 0.1°C)
"voltL1": 232, // Voltage L1 - N rms in Volt
"voltL2": 9, // Voltage L2 - N rms in Volt
"voltL3": 9, // Voltage L3 - N rms in Volt
"extLock": 1, // extern lock state
"power": 0, // Power (L1+L2+L3) in VA
"energyP": 0, // Energy since PowerOn (in kWh)
"energyI": 0.003, // Energy since Installation (in kWh)
"currMax": 16, // Hardware configuration maximal current (in 0.1A)
"currMin": 6, // Hardware configuration minimal current (in 0.1A)
"logStr": "<item no> <mfgDate> <serial>",
"wdTmOut": 15000, // ModBus-Master WatchDog Timeout (in ms)
"standby": 4, // Standby Function Control
"remLock": 1, // Remote lock (only if extern lock unlocked)
"currLim": 130, // Maximal current command
"currFs": 0, // FailSafe Current configuration
"load": 0, // wbec load management
"resCode": "0" // Result code of last Modbus message (0 = ok)
},
{ // Values of 2nd box ...
"busId": 2,
"version": "0",
"chgStat": 0,
...
"load": 0,
"resCode": "e4"
}
],
"modbus": {
"state": {
"lastTm": 2852819, // Timestamp of last Modbus message (in ms)
"millis": 2855489 // Time since start of wbec (in ms)
}
},
"wifi": {
"mac": "00:1F:3F:15:29:7E", // wbec MAC address
"rssi": -76, // WiFi signal
"signal": 48, // WiFi signal quality (in %)
"channel": 11 // WiFi channel
}
}
Set allowed current:
http://192.168.xx.yy/json?currLim=120 --> set current limit to 12A (on the box with id=0, i.e. ModBus Bus-ID=1)
http://192.168.xx.yy/json?currLim=60&id=2 --> set current limit to 6A on the box with id=2 (i.e. ModBus Bus-ID=3)
Set Watchdog timeout:
http://192.168.xx.yy/json?wdTmOut=20000
go-eCharger API
wbec can partly emulate the API of Go-eCharger (https://github.com/goecharger/go-eCharger-API-v1) via the following HTTP commands:
Read:
http://x.x.x.x/status
{"car":"1","alw":"1","amp":"6","err":"0","stp":"0","tmp":"307","dws":"5955","ubi":"0","eto":"59","nrg":[231,232,234,0,0,0,0,0,0,0,0,0,0,0,0,0],"fwv":"40"}
{"version":"B","car":"1","err":"0","alw":"1","amp":"6","amx":"6","stp":"0","pha":"63","tmp":"307","dws":"0","dwo":"0","uby":"0","eto":"59","nrg":[233,234,233,0,0,0,0,0,0,0,0,0,0,0,0,0],"fwv":"40","sse":"123456","ama":"16","ust":"2"}
Write:
http://x.x.x.x/mqtt?payload=...
This offers a simple way to integrate wbec into Energy Management Systems, which support go-eCharger, but not the Heidelberg Energy Control, such as EVCC or Solaranzeige.
Support the project
You like wbec? Please star this project on GitHub!
What? You don't like it but you love it? When wbec helps you in using your wallbox more efficiently, you can also
