When something looks wrong#
No engine data#
Check that the ignition is on and the adapter is in the port. Double-click BOOT to start a connection search now. The board also starts one by itself after a minute without engine data.
It found the wrong adapter#
Hold BOOT for 8 seconds, then tap BOOT to confirm. The board forgets the saved adapter and connects to the strongest nearby adapter again. Planned for a later S3 release, off in this source by default (CONFIG_OBD_BLE_PAIR_CONFIRM): it asks first (“Use <name>?”), and you tap BOOT within 5 seconds only for the right one.
A value shows “–”#
Either the car does not report it, or the drive has not started. The board shows a dash rather than guess.
The clock is wrong#
The clock needs a known Wi-Fi network within reach while parked, and it is exact to about one second. Check the time zone in the desktop app.
The board stays in download mode after flashing#
Reset it with this command.
python -m esptool --chip esp32s3 -p <port> --after watchdog-reset chip-id
Reporting a problem#
Note what you saw and when, with your car’s make, model and year. The field checks in the repository’s docs/FIELD_CHECKS.md have tables you can fill in.