COMPANYSoftware and hardware for smart metering systems and energy assets in the German market — including the EnergyLink One gateway, which speaks EEBUS to heat pumps, PV, storage and wallboxes on site.
Read more →Open source EEBUS
enbility – The Open Source EEBUS Go Project
enbility maintains the Go implementations of SHIP and SPINE that let heat pumps, wallboxes, inverters and energy managers speak EEBUS — openly licensed, independently auditable, and in production today.
TERMINAL
$ go get github.com/enbility/eebus-go
$ go get github.com/enbility/ship-go
$ go get github.com/enbility/spine-go
import "github.com/enbility/eebus-go/service"
MIT licence · Go 1.21+
3Go libraries: SHIP, SPINE, use cases
SPSShip Pairng Service of the EEBUS specification implemented
6organisations and individuals in the consortium
265commits in the last 12 months
67pull requests merged in the last 12 months
22people have contributed on GitHub
93forks across the three libraries
22releases published since 2022
In short
01 / WHO
A consortium, not a single maintainer
Since December 2025 enbility is stewarded jointly by Andreas Linde, Coretech Innovations, EnQS, Kai Takac, Kontron eSystems and SPiNE — a carrier organisation committed to keeping the stack alive independently of any one company.
Meet the consortium →02 / WHY
Interoperability needs a readable reference
EEBUS is how German energy assets are meant to coordinate under §14a EnWG and §9 EEG. A closed stack makes that coordination unverifiable. enbility keeps one implementation that any manufacturer, grid operator or auditor can read, test and fix.
How EEBUS works →03 / HOW
Running in about twenty minutes
Add eebus-go to your project, generate a device certificate, register the use cases your product supports, and pair against a real controller. The examples in the repository cover both ends.
Getting started →The libraries
Three layers, each usable on its own. Most products only ever import the top one.
eebus-gov0.7.0
Use-case layer. Register what your device is — EV charger, heat pump, monitored grid connection point — and the library handles the SPINE conversation behind it.
- Commits
- 1,165
- Last commit
spine-gov0.7.0
The data model. SPINE 1.3 of the EEBUS specification: entities, features, function types and the subscription and binding machinery that moves values between them.
- Commits
- 322
- Last commit
ship-gov0.6.0
Transport and trust. Certificates, mDNS discovery, the WebSocket connection, pairing and the SHIP handshake that two devices complete before they exchange a single value.
- Commits
- 375
- Last commit
Who carries the project
Each partner builds products that depend on EEBUS working properly. That is the whole governance model: the people who need the stack maintain it.
COMPANY
COMPANYEmbedded Linux, IoT and EEBUS tooling from Munich and Cairo: EEBUS Hub for SiL/HiL device testing, Verify 360 for qualification readiness, and gateway stacks for D-Bus, REST and MQTT.
Read more →
COMPANYIndependent development and testing partner for connected energy management and IoT systems. Combines software engineering and interoperability expertise with hands-on testing of real devices and complete systems in the EnQS Testlab.
Read more →
COMPANYKontron eSystems GmbH, based in Wendlingen, develops and produces technologically leading AC charging solutions for intelligent and connected charging of electric cars. Core products are mobile and permanently installed AC charging systems, as well as modular system solutions for connection to smart homes and integration into the smart grid. The technologies of eSystems enable grid and user-friendly charging. eSystems is a certified automotive supplier. Our deep connectivity and cybersecurity expertise ensures secure, connected products. As a certified automotive supplier and experienced industrial partner, Kontron eSystems guarantees the highest quality standards and complete, efficient system integration from a single source. With approximately 7,000 employees worldwide, Kontron represents industrial strength and innovation leadership.Show more +Show less −
Individuals2 PEOPLE
Andreas Linde, who wrote the libraries and released them in December 2022, and Kai Takac — both members in a personal capacity rather than through a company.
Read more →Used in production byevcc— the open-source home energy manager, on enbility since 2022.[ERGÄNZEN: weitere Referenzen?]
Beyond code
The libraries are free, and nobody sells them. What the consortium members do sell are the products and services around them — certified hardware, test capacity and implementation work.
EnergyLink One
The first box officailly qualified with the enbility EEBUS stack: limitation of power consumption and production in both roles — as the controllable system (CS/HEMS) and as the energy guard (EG, the German Steuerbox) — plus power and grid connection point monitoring and SHIP pairing. It runs alongside a local HEMS such as evcc, connects to a cloud HEMS, or is extended with your own applications and connectors through the SDK.
- LPC
- LPP
- MPC
- MGCP
- SHIP pairing
- CS and EG roles
- HEMS and cloud HEMS
- SDK for own applications
EEBUS Hub and qualification
A simulation and test framework for EEBUS device development, a validation suite that reports what still stands between a device and certification readiness, and use case implementation for customers who need the protocol inside their own product.
- EEBUS Hub
- Qualification readiness
- Use case implementation
EEBUS Testlab
A lab wired with real PV systems, battery storage, wallboxes and test smart meter gateways, reachable over VPN — where an EEBUS implementation or integration meets hardware that behaves like hardware, not like a simulator.
- Implementation testing
- Integration testing
- Remote access
Hardware built on eebus-go
Wallboxes, charging cables, inverters and storage that speak EEBUS through the same stack — and the option to have the electronics developed and manufactured for the job, from prototype to series production.
- Charging hardware
- PV and storage
- Custom EMS electronics
How does EEBUS actually work?
Two layers. SHIP finds the other device on the local network, establishes a mutually authenticated TLS connection and completes a pairing the user confirms once. SPINE then describes what each device is and what it can do, so a wallbox and an energy manager negotiate a charging limit without either having been built for the other.
What does enbility give me that the specification does not?
A working implementation of the parts that are tedious to get right — certificate handling, discovery, the handshake state machine, the SPINE model — plus a set of ready use cases covering EV charging, self-consumption optimisation and power limitation. You implement your device’s behaviour, not the protocol.
From the blog
All posts →23 Dec 2025 · Thomas Müller
enbility is moving forward — together
Over the past months, some in the community have asked whether enbility and the go-eebus stack are still actively maintained and what its future looks like. We want to be very c…
04 Jul 2025 · Andreas LindeEEBUS Protocol Analysis: The Evidence is In
Following my previous post about EEBUS's fundamental flaws, I've created comprehensive technical analyses of the SHIP and SPINE protocol specifications and their implementations…
11 Mar 2025 · Andreas LindeThe road ahead
I spent the past 4 years on getting to know EEBUS and implementing it on all levels: SHIP, SPINE and multiple use cases. Because I was curious, interested, and needed it to char…
Building a device that has to speak EEBUS?
Start with the examples in the repository. If you get stuck, the consortium reads the issue tracker — and several partners offer commercial support around it.