An unofficial, open-source Android app for controlling Hyundai and Kia vehicles via the Bluelink / UVO / Kia Connect API — inspired by the iOS app BetterBlue.
- 🔒 Lock & Unlock doors remotely
- 🚗 Remote Start / Stop engine with full climate pre-configuration
- ❄️ Climate Control — temperature, defrost, heated steering wheel, seat heat levels
- 🔋 EV Support — battery status, start/stop charging, set AC & DC charge targets
- 📍 Vehicle Status — doors, hood, trunk, tires, ignition, odometer
- 🖼️ Dashboard vehicle images — automatic supported Hyundai/Kia images plus an optional custom uploaded dashboard image
- 🔔 Horn & Lights — panic button, flash lights only
- 🌍 Multi-region — USA Hyundai, USA Kia, Canada, Europe, Australia/NZ
- 🌑 Dark-first Material 3 UI
- 🏠 Home screen widgets — full, battery, lock, unlock, climate, refresh, and compact controls widgets
- 🔐 Biometric lock option
- 🔑 Secure token storage via DataStore
- 📏 Unit preferences — switch temperature between °F/°C and distance between miles/kilometers
- Android Studio Hedgehog (2023.1.1) or newer
- Android SDK 26+ (Android 8.0+)
- A Hyundai Bluelink or Kia Connect account (existing — same login as the official app)
- Clone or unzip this project
- Open the
BlueBridgeAndroid/folder in Android Studio - Wait for Gradle to sync and download dependencies (~2–3 min first time)
- Connect an Android device or start an emulator
- Click Run ▶
- Select your Region & Brand on the login screen
- Sign in with your existing Bluelink / Kia Connect email and password
The dashboard automatically selects a vehicle image for supported Hyundai and Kia models. You can also tap Custom image on the dashboard vehicle image card to choose your own image from the device. BlueBridge stores the selected image URI locally and asks Android for persistable read access when the image provider supports it. Use Reset on the same card to return to the automatic model image.
In Settings → Preferences, BlueBridge supports:
- Temperature Unit: Fahrenheit or Celsius
- Distance Unit: miles or kilometers
- Time Zone: device time zone by default, with manual overrides for UTC and common North American zones
Distance preference affects dashboard range cards, EV charging range, vehicle status range, odometer display, widgets, and Android Auto read-only status views. Vehicle API data is still cached internally in miles where the source API reports miles, then converted only for display.
The time zone preference is used for vehicle-reported timestamps such as tire-pressure reading times. BlueBridge defaults to the device time zone. If the vehicle/API reports tire timestamps in a different zone, choose an override in Settings → Preferences → Time Zone.
BlueBridge includes several Android home-screen widgets backed by VehicleWidgetProvider and small provider subclasses. Each widget reads the cached selected-vehicle snapshot from DataStore. Refresh and command widgets call the same VehicleRepository used by the main app, then refresh and cache the latest battery, range, charging, and lock-state data.
Available widget entries:
| Widget | Default size | Purpose |
|---|---|---|
| BlueBridge Full | 4×2 | Battery, range, lock state, refresh, lock, unlock, and climate |
| BlueBridge Battery | 2×1 | Compact battery, range, and refresh |
| BlueBridge Battery Wide | 3×2 | Larger battery/range view with lock state and refresh |
| BlueBridge Lock | 1×1 | One-tap lock |
| BlueBridge Unlock | 1×1 | One-tap unlock |
| BlueBridge Climate | 1×1 | One-tap cabin climate using the app default temperature |
| BlueBridge Refresh | 1×1 | One-tap status refresh |
| BlueBridge Lock Controls | 2×1 | Compact lock and unlock buttons |
Most launchers also allow these widgets to be resized after placement, within Android launcher constraints.
- Widgets use the currently selected vehicle from the main app.
- Battery and lock-state information is cached so widgets can render quickly without opening the app.
- Refresh updates the cached vehicle snapshot.
- Command widgets execute immediately through the same repository layer used by the in-app controls.
- After a command completes, widgets request a status refresh so the displayed state can catch up with the vehicle.
- Vehicle API status updates may be delayed by Hyundai/Kia servers, so lock, climate, and charging state can briefly lag behind the command result.
The home-screen widgets use only Android RemoteViews-compatible view classes. Earlier widget layouts used Space separators, which some launchers reject while inflating widgets and display as a generic “Problem loading widget” or error tile. Separators are now implemented as empty TextView elements, and widget provider metadata no longer marks widgets as reconfigurable because no configuration activity is supplied.
BlueBridge registers multiple widget entries so the launcher can offer separate battery, refresh, lock, unlock, climate, compact controls, and full-size widgets.
- The single-action widgets — Lock, Unlock, Climate, and Refresh — advertise Android's legacy 1×1 widget footprint using 40dp minimum width/height plus
targetCellWidth="1"andtargetCellHeight="1". - The compact Battery widget advertises a 2×1 footprint.
- The wide Battery widget remains a larger 3×2 option.
- Battery widgets use a dashboard-inspired dark blue gradient card, rounded inner status panel, large battery percentage typography, and a blue/green rounded progress bar matching the dashboard battery panel style.
Some Hyundai/Bluelink remote climate endpoints can return HTTP success with an empty response body. BlueBridge treats successful empty responses as successful commands instead of letting Retrofit/Gson try to parse an empty body as JSON, which previously produced End of input at line 1 column 1 path $ after climate start/stop succeeded.
Widget refresh buttons send a background status-refresh command through VehicleWidgetProvider. The widgets now show transient messages such as Refreshing… or Sending lock… immediately after a tap so it is clearer that the button press was received. Full-size widget controls also use larger touch targets for easier tapping.
BlueBridge lets users choose their Region & Brand directly on the login screen before authentication. This is important because Hyundai/Kia accounts are region-specific and use different services in the USA, Canada, Europe, and Australia/NZ. The selected region is saved locally and is also available later under Settings → Region & Brand.
European Hyundai/Kia/Genesis support uses the EU CCSP API (prd.eu-ccapi.*) rather than the USA or Canada API paths. Because the EU login pages currently rely on browser/reCAPTCHA authentication, BlueBridge's EU login expects a valid 48-character EU refresh token in the password field instead of the normal account password.
Implemented EU features are experimental and include:
- Refresh-token based sign-in
- Vehicle list
- Cached and live status refresh
- Lock / unlock through the EU control-token flow when a PIN is stored
- Climate start / stop for supported vehicles
- EV charge start / stop for supported vehicles
Known EU limitations:
- The app does not yet generate the EU refresh token internally.
- Horn/lights and charge-target editing are not mapped yet.
- Location parsing is not surfaced in the BlueBridge UI model yet.
- Endpoint behavior can vary between Hyundai, Kia, Genesis, and CCS2-capable vehicles.
BlueBridge lets you choose Fahrenheit/Celsius, miles/kilometers, a display time zone, and 12-hour or 24-hour timestamp formatting. Vehicle-reported tire and odometer reading times use the selected time-zone and time-format preferences for consistent display.
In the app go to Settings → Region & Brand and select:
| Option | Use for |
|---|---|
| USA — Hyundai | US Bluelink accounts |
| USA — Kia | US Kia Connect / UVO accounts |
| Canada — Hyundai | Canadian Bluelink via mybluelink.ca TODS API |
| Canada — Kia | Canadian Kia Connect via kiaconnect.ca TODS API |
| Canada — Genesis | Canadian Genesis Connect via genesisconnect.ca TODS API |
| Europe — Hyundai | EU Hyundai Bluelink accounts. Uses EU CCSP refresh-token login. |
| Europe — Kia | EU Kia Connect accounts. Uses EU CCSP refresh-token login. |
| Europe — Genesis | EU Genesis accounts. Uses EU CCSP refresh-token login. |
| Australia — Hyundai | Australian Hyundai Bluelink accounts |
| Australia — Kia | Australian Kia Connect accounts |
| New Zealand — Kia | New Zealand Kia Connect accounts |
| Australia / NZ | Legacy/default Australian Hyundai selection |
- BlueBridge is a client app for your existing Hyundai Bluelink or Kia Connect account.
- Credentials and tokens are stored locally using the app's DataStore-backed storage layer.
- Biometric lock can be enabled to add an extra local access gate before using the app.
- Vehicle commands are sensitive actions. Treat any device with BlueBridge installed as capable of sending remote vehicle commands.
- This app is not intended for shared or unattended devices unless Android device-level security is enabled.
| Issue | What to try |
|---|---|
| Login fails | Confirm the same credentials work in the official Hyundai/Kia app, then verify the selected region and brand. |
| Vehicle list is empty | Refresh after login and confirm the account has an active enrolled vehicle in the official app. |
| Commands work but status looks stale | Use Refresh. Server-side status can lag behind successful commands. |
| Widget shows no vehicle | Open the app once, sign in, select a vehicle, then add or refresh the widget. |
| Widget command appears delayed | The command may have been accepted while the vehicle status endpoint has not updated yet. Refresh again after a short interval. |
| Climate start/stop shows success but status lags | The remote command and the vehicle status update are separate API flows; status may trail the accepted command. |
| Region-specific features are missing | Some endpoints and features vary by Hyundai/Kia region, vehicle model, account type, and EV vs ICE platform. |
Canada uses the Hyundai/Kia TODS web API rather than the USA mobile API. BlueBridge includes a separate Canadian API path for:
- Canadian Hyundai:
https://mybluelink.ca/tods/api/ - Canadian Kia:
https://kiaconnect.ca/tods/api/ - Canadian Genesis:
https://genesisconnect.ca/tods/api/
Implemented Canadian flows:
- login through
/v2/login - stable generated
Deviceidstorage to reduce repeat MFA prompts - vehicle list through
/vhcllst - cached and live status through
/lstvhclstsand/rltmvhclsts - PIN verification through
/vrfypinbefore protected commands - lock and unlock through
/drlckand/drulck - cabin climate start/stop through
/rmtstrt,/rmtstp,/evc/rfon, and/evc/rfoff - EV charge start/stop through
/evc/rcstrtand/evc/rcstp
Canadian OTP/MFA endpoints are present in the API layer, but the login screen does not yet expose an OTP entry flow. If the server returns an OTP-required response for a new device, BlueBridge shows a clear message asking the user to authenticate once in the official Canadian app or web portal before trying again.
Currently not mapped for Canada: horn/lights, vehicle location, and charge-target editing.
Australia/New Zealand support is experimental and uses the regional CCSP API hosts documented by the public Hyundai-Kia-Connect API work:
- Hyundai Australia:
au-apigw.ccs.hyundai.com.au:8080 - Kia Australia:
au-apigw.ccs.kia.com.au:8082 - Kia New Zealand:
au-apigw.ccs.kia.com.au:8082with the New Zealand Kia service identifiers
Mapped features include login, vehicle list, cached/live vehicle status, lock/unlock attempts, climate start/stop attempts, and EV charge start/stop attempts. Status reads are the most likely to work consistently. Command support can vary by vehicle, account, market, and API permission state, so treat Australian/NZ commands as experimental until verified on real vehicles.
app/
└── java/com/bluebridge/android/
├── data/
│ ├── api/ # Retrofit API service + constants
│ ├── models/ # All data classes (Vehicle, Status, etc.)
│ └── repository/ # VehicleRepository + PreferencesManager
├── di/ # Hilt dependency injection
├── ui/
│ ├── components/ # Reusable Compose components
│ ├── navigation/ # NavHost / Screen routes
│ ├── screens/ # Login, Dashboard, Controls, Status,
│ │ # RemoteStart, EVCharging, Settings
│ └── theme/ # Colors, Typography, Theme
├── viewmodel/ # AuthViewModel, VehicleViewModel, SettingsViewModel
└── widget/ # Home screen widget providers and RemoteViews layouts
Stack: Kotlin · Jetpack Compose · Hilt · Retrofit · OkHttp · DataStore · Navigation Compose · Android App Widgets
- Open the project root in Android Studio before building.
- Let Android Studio sync Gradle dependencies before running the app.
- Use a physical device for best testing of widgets, biometrics, and background command behavior.
- Some emulators do not fully match real launcher widget sizing behavior.
- Hyundai/Kia APIs are unofficial and may change without notice.
- API availability varies by region, brand, vehicle model, and account state.
- Widgets depend on cached app state and Android launcher behavior.
- Android launchers may render widget spacing and exact grid size differently.
- Remote command status can be delayed even when a command was accepted successfully.
- Vehicle wake-up, network coverage, subscription status, and server-side throttling can affect command reliability.
- Push notifications for status changes
- Trip history parsing
- Scheduled remote start timer
- Android Auto companion experience
- Wear OS companion app
- More per-widget configuration options
- Optional custom widget themes
- Vehicle nickname and multi-vehicle widget selection
See PRIVACY.md for details about local storage, connected-car API communication, and what to remove before sharing logs or screenshots.
Licensed under the Apache License, Version 2.0. See LICENSE.
This app is not affiliated with Hyundai Motor Company or Kia Corporation. It communicates with the same API endpoints used by the official apps. Use at your own risk. The authors take no responsibility for any unintended vehicle actions.
When biometric lock is enabled, BlueBridge now keeps the current unlock session active during brief app switches or accidental minimizes. The app only requires biometric re-authentication after it has been in the background for more than about five minutes, or after the app process/session is otherwise reset.
When biometric lock is enabled, BlueBridge keeps a short unlock grace period after a successful biometric check. Opening the app from a home-screen widget during that grace period should return to the dashboard without asking for fingerprint again. After the grace period expires, widget-launched app opens require biometric unlock again.