Screenshots From the README of MarkBovee/vaillant-ebus.
About
Home Assistant integration for Vaillant heat pumps via direct ebusd TCP — no MQTT, no cloud
Description from MarkBovee/vaillant-ebus
Shows in Vulpo
Quick Toggle card, Climate card, Select card, Calendar card, Apple Watch, Control Center, Climate Live Activity.Supports
- Works locallyTalks to your devices on your own network. No vendor cloud in between.
- From the MarketplaceInstalled through the Marketplace, formerly HACS.
- Actively maintainedIts author released or pushed a change in the last six months.
Provides
- Climate
- Water heaters
- Switches
- Sensors
- Calendars
Setting it up
Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.
Vaillant eBUS (ebusd)
- Host
- Port
- Update interval (seconds)
After setup
- ebusd host
- ebusd port
- Poll interval (seconds)
- Default away duration (days)
- Default quick veto duration (hours)
- Default quick veto temperature
- Manual cooling duration (days)
- Energy counter scale (divisor)
- Raw traffic capture (seconds)
- I understand that these entity registry entries will be removed
- I understand that eBUS discovery will run again
Texts from the code of MarkBovee/vaillant-ebus.
Troubleshooting
- DiagnosticsDownloads a diagnostics file to attach to a bug report.
- Repair noticesNotices it can show in Settings, Repairs:ebusd is unreachable, Stale Vaillant eBUS entities
From the README
Disclaimer: This project is an independent third-party integration and is not affiliated with, endorsed by, or connected to Vaillant GmbH in any way. All trademarks belong to their respective owners.
Home Assistant integration for Vaillant heat pumps via direct ebusd TCP — no MQTT, no cloud.
- Drop-in replacement for mypyllant API integration — same entities, no cloud
- Direct TCP connection to ebusd — zero MQTT setup required
- Dynamically discovers available circuits and registers on connect
- Generates native Home Assistant entities for sensors, controls, climate, water heating, calendars, and dates
- Climate entities with quick veto and away mode (calendar-based scheduling) — one thermostat and flow-temperature-range per discovered heating zone on multi-zone systems
- Cooling control — read and write the manual cooling period ("cool until [date]") via the climate COOL mode and dedicated datetime entities
- Water heater entities with DHW boost and temperature control
- Read & write any register via HA services (vaillant_ebus.read_parameter, vaillant_ebus.write_parameter)
- Custom registers via --enabledefine (e.g. room humidity, manual cooling dates)
- YAML overrides for entity metadata (names, icons, units)
Information
- Installs
- 51 sharing analytics
- GitHub stars
- 54
- Connection
- Works locally
- Upkeep
- Updated in the last 6 months
- Version
- v1.14.0,
- Category
- Climate, Thermostats and heating
- Kind
- Marketplace integration
- Brand
- Vaillant
- Needs
- Needs the Marketplace (HACS on 2026.10 and older)
- Domain
vaillant_ebus- Issues
- Report an issue

















