5. Bridge mode

5. Bridge mode (ebusd)

Use this when control software like ebusd on another host owns the bus. The adapter is a transparent bus interface: no autonomous participation, no command store, no MQTT — all intelligence lives in ebusd. Flash the esp32-c3 environment.

ebusd device strings

Port	String	Use
3333	-d <device-ip>:3333	Raw byte bridge, read + write.
3334	-d <device-ip>:3334	Listen-only byte pipe (everything sent here is discarded). Bridge mode forwards every received byte unfiltered — no framing, no drop accounting.
3335	-d enh:<device-ip>:3335	Enhanced (binary) protocol.
3335	-d ens:<device-ip>:3335	Enhanced send path (as tested).

Timing over WiFi (important)

Verified working:

ebusd -d ens:<device-ip>:3335 \
  --acquiretimeout=100 \
  --latency=200 \
  --receivetimeout=50 \
  --configpath <ebusd-configuration>/en \
  --scanconfig=08

The timing flags are the point: WLAN adds ~12–18 ms per symbol and ~90 ms QQ-to-grant, so ebusd's LAN defaults time out early. These values give it room (acquire 100 ms, latency 200 ms, receive 50 ms) without masking real failures. All three are milliseconds (verified against ebusd source, main_args.cpp).

When not to use it

For standalone operation without ebusd, see 6. INTERNAL firmware (current).