Hey everyone
Sharing a Home Assistant add-on I've been working on: **EEBUS Bridge**.
## The problem
EEBUS (SHIP/SPINE) is the standard that's starting to show up on more and
more energy-related devices — heat pumps, EV chargers, inverters, energy
managers — but there wasn't a generic HA add-on to talk to it without
writing a vendor-specific integration for each brand.
## What the add-on does
- Connects to **any EEBUS-capable device** on your local network — no
vendor-specific code, no hardcoded device IDs.
- Automatically exposes the device's measurements as native HA entities
via **MQTT discovery**.
- One EEBUS device = one HA device, with one sensor per measurement
(power, energy, current, voltage, etc.).
Tested with a **Saunier Duval / Vaillant VR920** heat pump, and should
work with any device implementing the EEBUS SHIP/SPINE standard.
## Controlling devices (optional)
Beyond reading data, the add-on can also **control** the device when you
enable `write.enable`:
- **OHPCF** (compressor flexibility): a `climate` entity shows up on
compatible heat pumps (auto/off modes, pause/resume presets).
- **LPC** (power consumption limitation): a `number` entity lets you cap
consumption on any device that exposes this feature (heat pumps, EV
chargers, inverters, batteries...).
More use cases are planned (LPP for inverters, OPEV/OSCEV for EV
chargers).
## Security
- No secrets baked into the image; everything is injected by HA at
runtime.
- The service runs as a dedicated non-root user.
- Custom, tailored AppArmor profile, minimal permissions.
- Container images are signed with Cosign.
## Installation
Add the repository under **Settings → Add-ons → Add-on Store → ⋯ →
Repositories**:
Then find **EEBUS Bridge** in the store.
## Current status
There's a **dev** channel (`eebus_bridge_dev`) to preview upcoming
changes, and the regular production add-on. The two are mutually
exclusive (they share the same MQTT topics/ports), so only run one at a
time.
Happy to hear feedback, especially reports of other EEBUS devices you've
tested it with successfully (or not!). Feel free to open an issue on the
repo if you run into problems.
Repo: https://github.com/tbazire/homeassistant-addons
Thanks for this. I have it working. What do the sensors “power (acPowerTotal) entity 3” and “power (acPowerTotal) entity 3.1” relate to as I am a bit confused.
Entity 3 corresponds to the total instantaneous power consumption, while entity 3.1 represents the instantaneous power consumption of the outdoor unit only.
So, for example, when the outdoor unit starts running, you should see a value on 3.1 and a value on 3, where 3 is the sum of 3.1 plus the rest of the system’s consumption.
To get the energy consumption in kWh, you need to add the integration called “Integral Sensor” and apply it to entity 3.
They were designed a few weeks apart (I was not aware of that project at the time). From what I can see, we have taken different approaches.
My goal was to create a less intrusive application. They chose an addon + integration approach, with gRPC communication between the two, whereas my solution consists of a single addon that publishes data via MQTT. Home Assistant then determines the sensor type based on the entity provided by the addon.
They also seem to expose more information than my solution does, but mine is still under development. Ultimately, it is up to each user to decide which approach best suits their needs by conducting their own evaluation and analysis.
Thanks for the quick response