Code & releases

Three Go modules, versioned independently, released together when the layers below change. Everything is on GitHub — issues, discussions and pull requests included.

GitHub organisation Contributing guide

How the layers stack

eebus-goUse cases — EV charging, self-consumption optimisation, power limitation. This is the import most products need.

spine-goData model — SPINE 1.3: entities, features, function types, subscriptions and bindings.

ship-goTransport & trust — certificates, mDNS discovery, WebSocket, pairing, SHIP handshake.

Current versions

live from GitHub releases

Module	Version	Released	Licence	Highlights	Notes
eebus-go	v0.7.0	21 Sept 2024	MIT	Use-case API reshaped, monitoring and limitation of power consumption	Changelog
spine-go	v0.7.0	21 Sept 2024	MIT	SPINE 1.3 coverage, binding and subscription handling	Changelog
ship-go	v0.6.0	21 Sept 2024	MIT	mDNS provider rework, connection lifecycle fixes	Changelog

Versions and dates above are pulled directly from the GitHub releases of each module. The licence link points to the file in the respective repository.

Supporting repositories

The discovery layer underneath SHIP. Neither is EEBUS code, and neither is tagged — go.mod pins them by commit rather than by version.

zeroconf

mDNS and DNS-SD service discovery in pure Go

Commits: 254
Last commit: 10 Apr 2026

github.com/enbility/zeroconf →

go-avahi

Bindings for the Avahi daemon, where the port is already taken

Commits: 50
Last commit: 17 Sept 2026

github.com/enbility/go-avahi →

Implemented use cases

EVSECCEVSE commissioning and configuration

EVCCEV commissioning and configuration

EVCEMEV charging electricity measurement

EVSOCEV state of charge

OSCEVSelf-consumption optimisation during EV charging

OPEVOverload protection by charging current curtailment

DBEVCBidirectional-charging use case

LPCLimitation of power consumption — §14a EnWG

LPPLimitation of power production — §9 EEG

MGCPMonitoring of grid connection point

Report a problem

Interoperability bugs are the most valuable issues we get. Include the device, the firmware version and a SHIP/SPINE trace if you have one.

Open an issue →

Contribute code

New use cases, test coverage and device quirk handling are all welcome. Read the contributing guide first — the SPINE model has conventions worth following.

Contributing guide →How decisions are made →

Commercial support

Several consortium partners offer integration work, test-lab access and certification support around the stack on commercial terms.

Find a partner →