Sign in with Tesla
OAuth in Zepp app settings. Scopes include vehicle commands and charging. Tokens are stored on your phone.
Amazla routes commands through the internet (Tesla Fleet API). Amazla Key sends daily commands directly over Bluetooth (VCSEC).
Every command goes from watch → phone → internet → Tesla Fleet API → your car. Your phone must have internet for each action.
OAuth in Zepp app settings. Scopes include vehicle commands and charging. Tokens are stored on your phone.
One-time step: authorize your vehicle to accept commands from the Fleet API proxy. Requires car online and phone nearby via Bluetooth.
Watch sends a request to the phone app-side service, which calls Tesla Fleet API (lock, climate, frunk, charge port, etc.). Auto wake-up if the car is asleep.
Vehicle data is fetched and cached. Battery, doors, climate temps, and charging state refresh on the watch.
Works anywhere your phone has internet — not limited to BLE range. Best for climate, defrost, charge port, and remote access.
Daily commands (lock, unlock, frunk, trunk) go directly from watch to car over Bluetooth. No server in the middle.
The watch scans for your Tesla over BLE, connects, and can remember the MAC for faster reconnects.
Secure session via ECDH key exchange and derived session keys, with epoch/counters for replay protection.
Lock/unlock and frunk/trunk are packaged as VCSEC actions, authenticated (HMAC) and encrypted (AES-GCM) on the watch.
After BLE actions, vehicle status refreshes. Live sync for battery and climate uses Fleet API when online.
BLE pairing whitelists your watch as a Tesla key (tap keycard on center console). Session key pools are generated on the phone and synced to the watch for fast reconnects.
Lock, unlock, frunk, and trunk run on the watch via BLE + VCSEC — no server control in the middle. Climate and live status still need internet when used.
Compare both apps and pick the one that fits your driving routine.