Repository navigation
Vehicle Features
BlueDeck tries to show only the remote controls that make sense for your vehicle. In practice, Hyundai and Kia APIs do not always report which options a specific car has, and that varies a lot by region. When the app cannot tell, it may still show a control that your trim does not support.
Note
Seeing a button in BlueDeck (heated seats, heated steering, defrost, digital key, and so on) does not guarantee your car has that hardware. If a command fails or does nothing, your vehicle or region may simply not support it.
When the account APIs expose option flags (especially seat climate configs from US enrollment / vehicle-info responses), BlueDeck uses them:
| Situation | App behavior |
|---|---|
| API says the option is supported | Show the control |
| API says the option is not supported | Hide the control |
| API does not report the option at all | Usually show it (optimistic), so supported cars are not missing controls |
Important exception — ventilated / cooled seats: if seat capability data is missing, BlueDeck does not assume cooling/ventilation exists. Many trims have heated seats without ventilated seats. Cooling controls appear only when the API clearly indicates support.
These are commonly shown even when BlueDeck cannot confirm your model has them:
- Heated seats — especially when the vehicle list returns no seat configuration (common outside the US)
- Heated steering wheel — there is usually no dedicated “has heated steering” flag; the app may infer or default to showing it
- Defrost — offered with climate / remote start without a per-vehicle capability check
- Climate start / remote start — always available in the UI; success depends on the connected-car service and your vehicle
- Digital key and similar tiles — may appear when the capability field is blank
- EV charging controls — driven largely by model/fuel heuristics unless the API explicitly marks energy controls unsupported
Hyundai/Kia use different backends per market. Capability detail is not equal everywhere:
- USA (especially Hyundai): more likely to include seat and option details BlueDeck can use to hide unsupported controls
- Canada, Europe, Australia/NZ, and some USA Kia paths: vehicle lists often omit seat/option configs, so BlueDeck cannot reasonably detect every missing feature and will show more controls “just in case”
There is no reliable public VIN-options API BlueDeck can call in those regions to learn your exact trim package. Guessing from model name alone would hide real features for many owners, so the app prefers showing a control over hiding one that works.
- Ignore unused controls — they do not change your vehicle by themselves until you tap them
- If a command errors or is rejected by Bluelink / Kia Connect, that usually means the service or vehicle does not support it
- File an issue if a region/API clearly reports “not supported” but BlueDeck still shows the control (or the reverse) — include region, brand, model, and app version