EEBUS Hub is a testing and simulation framework for validating device integration over an EEBUS network. It builds on the eebus-go library for core EEBUS interactions and adds practical tooling to streamline real-world testing.

EEBUS Hub exposes APIs to control and orchestrate multiple EEBUS actors that participate in typical energy scenarios such as EV, EVSE, HEMS, Controlbox, Heatpump, Inverters and SMGW. You can run full simulations using built-in virtual devices, or plug in real hardware alongside simulated participants to accelerate integration, troubleshooting, and regression testing.

This repository includes examples that show how to use EEBUS Hub programmatically to automate your EEBUS testing procedures—ideal for CI pipelines and repeatable test suites.

Compliance support: EEBUS Hub helps manufacturers validate S14a compliance (and beyond) by enabling controlled, reproducible test scenarios and automated verification workflows.

Licensing: To obtain an EEBUS Hub license, contact us at eebus.hub@coretech-innovations.com

For researchers, academics, and early-stage startups you can obtain a non-commercial licence by joining our Coretech EEBUS Innovation Program. Contact us for more details.

"✅" - Supported

"-" - Not Supported yet

git clone https://github.com/Coretech-Innovations/EEBus-Hub.git

This is a simple API calls for adding EVSE and EV and connecting them with the CEM in the system

# adding new EVSE
curl -X POST http://localhost:8080/api/v1/evse/add  -H 'Content-Type: application/json'  -d '{"deviceName":"Coretech EVSE WLBX", "deviceCode":"0002","deviceModel":"Charging Station","brandName":"Coretech Innovations","vendor":{"name":"Coretech Innovations","code":"60745"},"serialNumber":"SN7640"}'

# Trusting the created EVSE from the CEM side
curl -X POST http://localhost:8080/api/v1/cem/trust -H 'Content-Type: application/json' -d '{"remoteSki": <EVSE Ski>}'

# Get the SKI of the CEM
curl -X GET http://localhost:8080/api/v1/cem 

# Pairing the EVSE with the CEM
curl -X POST http://localhost:8080/api/v1/evse/<EVSE ID>/cem -H 'Content-Type: application/json' -d '{"remoteski": <CEM Ski>}'

# adding new EV
curl -X POST http://localhost:8080/api/v1/ev/add -H 'Content-Type: application/json' -d '{"device": {"name": "Taycan", "code": "0003", "serialNumber": "SN1235"},"currentLimits": {"min": 5, "max": 10}, "asymmetricCharging": false}'

# adding the created EV to the EVSE we created before
curl -X POST http://localhost:8080/api/v1/ev/<EV ID>/evse/<EVSE ID>

# starting the simulation
curl -X POST http://localhost:8080/api/v1/sim -H 'Content-Type: application/json' -d '{"action": "start","tickRate": 1000,"simTimePerTick": 10}'

EVSE Ski: The Ski returned from creating the EVSE
EVSE ID: The id returned from creating the EVSE
CEM Ski: The Ski returned from calling the GET request on the CEM
EV ID: The id returned from creating the EV

docker load < docker-eebus-hub-vx.y.z.tar.xz

• using bridged networking mode:

docker run -p $PORT:8080 eebus-hub:vx.y.z

where $PORT is the desired published port.

• using host networking mode:

docker run --network=host eebus-hub:vx.y.z