Skip to content

EdiabasX 0.6.0 adds relay-mediated remote diagnostics through Bimmerz Connect. Run ediabasx serve --connect, share the link, and the remote user connects through the browser — no port forwarding, no VPN.


Client / server modeediabasx serve exposes a JSON-RPC server over WebSocket. Any EdiabasX client (CLI, web app, or custom integration via EdiabasClient) can connect and run jobs, browse SGBDs, and stream logs remotely. The server handles interface access, locking, and multiplexing — multiple clients can observe the same session.

Bimmerz Connect — the server operator adds --connect and authenticates via device flow. The relay at connect.bimmerz.app brokers the connection: the operator gets a deep link they can share over any channel. The remote user clicks it (or pastes the session token in Settings → Client → Bimmerz Connect) and the web app connects through the relay. Traffic is opaque to the relay — the same JSON-RPC protocol runs end-to-end, just tunnelled through WebSocket frames.

How it works:

sh
# server side (the machine with the cable + ECUs)
ediabasx serve start --connect --sgbd-path ~/ECU --interface serial

# prints:
#   Session:  abc123
#   Link:     https://ediabasx.bimmerz.app?connect=abc123.tok_xxx

The remote user opens the link → web app auto-connects → full diagnostics access: browse SGBDs, run jobs, view results, stream logs.

Also in this releaseEdiabasServer.attachStandardWebSocket() and EdiabasClient's new socket option for pre-connected WebSockets, making it straightforward to integrate relay or custom transport layers.

Full changelog

Most projects are PolyForm Noncommercial; some are MIT — see each repo for the canonical licence.