EEBUS Gateway
Add EEBUS to any product — fast, modular, and API‑first. Containerized delivery and developer‑friendly APIs let you integrate standardized EEBUS communication in days, not months.
- SPINE/SHIP‑compliant
- enbility‑go stack
- Docker‑ready
EEBUS Gateway is a modular communication component that adds turnkey EEBUS protocol capabilities to your products via clean, developer‑friendly APIs. Built on the enbility‑go stack, it bundles core service modules, standardized use cases, a flexible use‑case handler, and an interface handler — packaged with all supporting components for reliable operation. Delivered as a lightweight container, it enables immediate interoperability with other EEBUS‑compliant systems while minimizing integration effort and accelerating time‑to‑market.
Why EEBUS Gateway
Modular & Extensible
Compose EEBUS functionality using service modules and a flexible use‑case handler framework.
Developer‑First APIs
Expose measurements, use‑case state, and controls through clean REST endpoints.
Pre‑Integrated Use Cases
Ship with Limitation of Power Consumption (LPC); extend to MGCP/MPC and more.
Container‑Ready Delivery
Deploy as a Docker image, embed as a service, or run in your gateway/edge environment.
Interoperability by Design
Speak EEBUS SPINE/SHIP to connect HEMS, control boxes, SMGW‑based setups, EVSE, PV, HP, and batteries.
Standards Aligned
Designed to align with VDE‑AR‑E 2829‑6 and BSI TR‑03109 communication requirements.
Modular Layer Architecture
The EEBUS Gateway provides turnkey EEBUS capabilities through clean, developer-friendly APIs. Built on the enbility-go stack
How It Works
- 1
Deploy the container
Run the Docker image on your gateway, edge device, or server.
- 2
Configure use cases
Enable LPC and other EEBUS use cases; connect to your devices or HEMS.
- 3
Integrate via REST
Use our REST APIs to monitor, control, and orchestrate EEBUS flows.
Technical Overview
- Core Stack
- enbility‑go EEBUS implementation
- Protocols
- EEBUS SPINE/SHIP
- APIs
- RESTful JSON interface
- Use Cases
- LPC included; extensible to MGCP/MPC
- Deployment
- Docker container or embedded service
- Targets
- HEMS, Controlbox, SMGW environments, EVSE, PV, HP, Battery
- Security
- TLS for local interfaces; alignment with VDE/BSI communication requirements
