Setup
Pick LX or Commander. Or skip hardware and use Demo.
HardwareCables and adapters · we don’t take a cut
SupportedOBDLink LXBluetooth
SupportedCommanderWi‑Fi · internet stays up
DemoNo dongle
It’s not connectingThe usual suspects
Park first. Kill the car the way the cable instructions say before you unplug anything under the dash.
OBDLink LX
- Right cable for this exact car. Follow their pictures.
- Plug in the LX. Pair it in Android → Connected devices. Use their PIN if it asks.
- Wake the car, open TeslaSleuth, pick the vehicle + OBDLink, allow Nearby devices.
- Connection screen: tap the paired LX. If it fails, the message usually says which step died (permission, pairing, init, no bus).
- “Stay connected when you leave briefly” is on by default. Quiet park will drop Live when you’re just sitting there.
Demo
First launch, or Settings later. It’s a short real drive loop with VIN and location stripped. Fine for showing a friend the UI.
Commander
- S3XY app: ScanMyTesla support on. Commander Wi‑Fi on.
- VPN? Exclude TeslaSleuth (Blokada: same idea) or pause it.
- TeslaSleuth → Commander Wi‑Fi → name + password → Connect.
- Say yes to Android’s local-only Wi‑Fi prompt. That’s how Maps keeps working.
- Only one telemetry app. Fully quit Scan My Tesla first.
Factory SSID/password are public. Change both in S3XY, make them different from each other, type the same pair into TeslaSleuth. We’ll nag you if you leave the factory values. Same name and password gets blocked.
It’s not connecting
- LX missing: pair in Android first, Bluetooth on, then refresh.
- Busy: another OBD app or another phone is sitting on it.
- Waiting for bus: wake the car. Check the cable is the right generation and actually seated.
- No Commander: ScanMyTesla support on, SSID/password match S3XY.
- Connected, no data: something else is still on Commander. One client.
- VPN: exclude TeslaSleuth.
- Drops in Maps: leave “stay connected” on and allow the notification so Android doesn’t kill it.