OAuth with PKCE
Tesla account linking uses a secure OAuth flow with PKCE through a backend-initialized connect flow and callback exchange.
Tesla connection
Tesla-aware navigation without becoming only a Tesla app.
Orontes Drive connects Tesla account data, vehicle selection, live telemetry, route context, and in-app actions into one EV navigation workflow. The goal is not to mirror every Tesla screen. The goal is to make the vehicle more useful while planning and driving.
SoC
74%
Source
OBD
Arrival
21%
Profile
VIN
Secure setup
Tesla account linking is a context layer for better trips.
Scopes
The app requests Tesla scopes for identity, offline access, vehicle device data, vehicle location, vehicle commands, and charging commands.
Linked inventory
Linked vehicles can be surfaced, switched, and distinguished from imported vehicle setup inside the settings experience.
VIN decoding
Backend-owned VIN decoding can infer model, year, plant, battery chemistry, drive-unit hints, and EV catalog suggestions.
Route-aware battery
Tesla context can improve route and vehicle awareness by connecting battery state, vehicle profile, and planned charging behavior.
Ghost control
Ghost can route supported Tesla command requests through the app, keeping confirmation and driving context in the same surface.
Command surface
Connected actions where they help the drive.
The product models a broad Tesla command surface. Website copy should stay practical: supported commands live inside route and vehicle workflows, not as a claim that every Tesla path is fully public-smoke validated yet.
Access
Lock, unlock, horn, flash lights, valet mode, sentry mode.
Climate
Climate, climate keeper, seat and climate controls, preconditioning.
Charging
Charge-port actions, charge start and stop, charge limit, and charging command seams.
Navigation
Route and navigation requests stay connected to charging-aware planning.
OBD-first philosophy
Bluetooth OBD is the premium live telemetry layer.
The deeper story is not only Tesla account connection. Orontes Drive treats live vehicle awareness as source-aware: Bluetooth OBD is preferred when active and valid, while Tesla cloud telemetry can act as a rate-aware fallback.
Stable real-session model
The OBD path follows a validated push-enhapi subscription flow rather than aggressive command probing, and the old short push-silence disconnect behavior has been removed.
Mapped and recovered values
Mapped live values include speed, range, SoC, gear, indicators, braking signals, and additional recovered vehicle-state fields.
Cloud cost awareness
Tesla telemetry is rate-aware and cached, with a one-minute backend fetch gate per vehicle. Routine refreshes deliberately avoid treating Tesla wake-up as the normal path.
Not Tesla-only
Tesla is deep. Orontes is still an EV navigation platform first.
Route planning, charging intelligence, Ghost, trip history, radar context, notifications, favorites, and replay are broader than Tesla alone.