Observed 15 Sep 2026 on Vadelma: @eclass posted the identical line "OBD: adapter/link present but no engine data yet - adapter asleep or car off ..." at 12:58Z and 13:06Z, once per boot/rfcomm rebind while the car was off at home. obdwatch posts when the ELM327 appears at /dev/rfcomm0 and the handshake fails ({"ok": false, "trace": [{"stage": "handshake", ...}]}). Proposal: post only on a state CHANGE (link open -> engine data, or data -> lost), and never the "asleep/car off" line on boot; keep the fact in the presence/preflight tiles instead. Zero-touch behaviour stays for the interesting transitions.
Observed 15 Sep 2026 on Vadelma: @eclass posted the identical line "OBD: adapter/link present but no engine data yet - adapter asleep or car off ..." at 12:58Z and 13:06Z, once per boot/rfcomm rebind while the car was off at home.
obdwatchposts when the ELM327 appears at /dev/rfcomm0 and the handshake fails ({"ok": false, "trace": [{"stage": "handshake", ...}]}). Proposal: post only on a state CHANGE (link open -> engine data, or data -> lost), and never the "asleep/car off" line on boot; keep the fact in the presence/preflight tiles instead. Zero-touch behaviour stays for the interesting transitions.