Home

Welcome to the esp-ebus wiki!

Warning: Do not power your adapter from a power supply on eBus terminals - you will burn the transmit circuit (receive may still work)!

For quick setup see the 1. Quickstart

Firmware modes

The adapter supports two firmware modes:

• Bridge (esp32-c3) — an external client such as ebusd owns bus participation; see 5. Bridge mode.
• INTERNAL (esp32-c3-internal*) — the adapter participates on the bus itself; an external controller is not required. See 6. INTERNAL firmware (current).

Both modes accept external eBUS clients over TCP. In INTERNAL mode, these connections are served by the eBUS library's built-in client manager while the adapter continues its own bus participation.

Port	Client type	Use
3333	Regular	Raw byte bridge (read/write), e.g. ebusd.
3334	Read-only	Passive tap; transmitted data is discarded. Bridge mode forwards every byte unfiltered; INTERNAL firmware serves the framed event stream.
3335	Enhanced	Enhanced eBUS client protocol, e.g. ebusd.

These TCP ports carry eBUS traffic. The web UI/HTTP and MQTT are separate interfaces for device configuration, decoded values, and monitoring.

Pages

• 1. Quickstart
• 2. Configuration (both firmwares)
• 3. Troubleshooting
• 4. Upgrading
• 5. Bridge mode
• 6. INTERNAL firmware (current)
  • 6.1 eBUS configuration
  • 6.2 Command definition
  • 6.3 HTTP & web UI
  • 6.4 MQTT
  • 6.5 Home Assistant
  • 6.6 First boot & troubleshooting
• A. Hardware revisions
• B. INTERNAL firmware (legacy)
  • B.1 MQTT
  • B.2 HTTP
  • B.3 Home Assistant
  • B.4 Command definition
  • B.5 Bus ISR Settings