OBD data
OBD data · our own work, not from GAC's manuals

OBD data: logging set-up

How the readings get from the car into Home Assistant. A thin logger in the car, and the thinking done at home: the ESP32 only reads and stores, a small server decodes. Everything stays on your own network unless you add the 4G path.

CARADAPTERESP32COLLECTORHOME normal OBD portgatewayread-only Bluetooth ELM327,USB ELM327or a CAN chip reads and logsexplores new itemsguided tests home server, Dockerdatabase · tripsreplay · charts ASSISTANTsensorsdashboards plug-inBLE / USBhome Wi-FiMQTT optional: 4G, HTTPS, from anywhere
In the car: the ESP32
At home: the collector
Home Assistant

The collector publishes 46 sensors to Home Assistant over MQTT with automatic discovery, so they appear on their own: each door and the boot, locked or unlocked, four windows, four tyre pressures and temperatures, battery charge, health and voltage, highest / lowest / average cell and the spread, battery temperatures, energy in and out, speed, gear, brake pedal, motor temperature, A/C, 12 V, an estimated odometer and the last trip. Raw readings stay in the collector's database, so Home Assistant's own database doesn't fill up.

On the road: 4G

With the ESP32-S3 + A7670E board the logger can send its files over HTTPS from anywhere, to an upload address on the home server reached through a secure tunnel (for example Cloudflare Tunnel or WireGuard). The home Wi-Fi path stays as it is. Parts and SIM notes: build your own logger.