Please create a GitHub issue so we can fix it in the integration, thanks for sharing updates
My vehicle is different (Kia Telluride) but I see the same as you. I don’t see individual values in the Data attribute so those values may not be available for all vehicles.
Yes, I suppose there would be different sensors for different vehicles, but in this case my vehicle is the same model Kona EV, although I am in North America and judging by the picture @Doublet 's car is Euro of some sort.
Yes mine is a European Kona build in Czech republic.
From the integration perspective, we fully rely on incoming data from kia servers and try to create all possible sensors, as much as possible 
if data exists there, sensor will be created. We noticed that different responses based on production years etc, so slight differences are possible.
After updating to 1.30 integration is failing to load. Reverting to 1.27 now.
Received the same issue from another user on GitHub, he reverted to 1.2.7 and installed 1.3.0 and all worked fine. This is strange. After update: Setup failed for kia_uvo: Integration not found. · Issue #238 · fuatakgun/kia_uvo · GitHub
1 Like
Same here, after reverting en updating again it’s working fine.
Weird, strange and have no clue
Edit: it is an issue coming from HACS and seems to be resolved.
I have this integration install and working but I have a couple questions.
It automatically loaded a few binary sensors, a lock entity and a device tracker. Does the integration know what options are available and automatically create them? I see in some of the screen shots options that I don’t have. For example I only have Tire Pressure - All and not one for each tire. Can I add that somehow or is that not available with my vehicle?
Next question is are these only informational or can I interact? I’d like to be able to remote start, set temp, etc. Is that possible?
All these entities are created based on output of kia api responses. Check your data sensor entity using developer tools page and if you find something useful but missing, create a request, we can add it.
Main power of integration is about services for remote start/stop and lock/unlock, if your car supports them
My car supports remote start/stop and lock/unlock through the Kia Access app. Here is what the data sensor has:
vehicle_data:
vehicleStatus:
climate:
airCtrl: false
defrost: false
airTemp:
value: '72'
unit: 1
heatingAccessory:
steeringWheel: 0
sideMirror: 0
rearWindow: 0
heatVentSeat:
driverSeat:
heatVentType: 0
heatVentLevel: 1
passengerSeat:
heatVentType: 0
heatVentLevel: 1
rearLeftSeat:
heatVentType: 0
heatVentLevel: 1
rearRightSeat:
heatVentType: 0
heatVentLevel: 1
engine: false
doorLock: true
doorStatus:
frontLeft: 0
frontRight: 0
backLeft: 0
backRight: 0
trunk: 0
hood: 0
lowFuelLight: false
ign3: false
transCond: true
distanceToEmpty:
value: 25
unit: 3
tirePressure:
all: 1
dateTime:
utc: '20220121035954'
offset: -8
syncDate:
utc: '20220121035947'
offset: -8
batteryStatus:
stateOfCharge: 76
deliveryMode: 1
sleepMode: false
lampWireStatus:
headLamp: {}
stopLamp: {}
turnSignalLamp: {}
windowStatus: {}
engineRuntime: {}
valetParkingMode: 0
time: '20220121035947'
battery:
batSoc: 76
doorOpen:
frontLeft: 0
frontRight: 0
backLeft: 0
backRight: 0
trunk: 0
hood: 0
trunkOpen: 0
hoodOpen: 0
tirePressureLamp:
tirePressureLampAll: 1
airCtrlOn: false
defrost: false
sideBackWindowHeat: 0
sideMirrorHeat: 0
steerWheelHeat: 0
airTemp:
value: '72'
unit: 1
dte:
value: 25
unit: 3
odometer:
value: 4231.2
unit: 3
vehicleLocation:
coord:
lat: 21.83753333
lon: -86.7367888889
alt: 160
altdo: 0
syncDate:
utc: '20220121035947'
offset: -8
Then you can give it a try kia_uvo services for remote start and stop. Lock should be accessible as a UI element.
From your data output, i see very interesting sensors but do you miss anything particularly?
Just want to say, that integration works fine with my Kia EV6.
I have battery percentage and range on my Apple watch. Action to start climate control. Need to reverse engineer one day so I can open trunk from watch. Easier than keys. Have plenty of experience with MitM API reverse engineering for the purpose of compatibility But Kia App does not do it yet
I am using Node Red for my IOS actions. How do I specify the Json parms to set a temp?
Should it be “Temperature”:22.3 - Temperature:“22.3” and with or without {} ?
{
"temperature": 22.3
}
1 Like
Great. Just what I needed. Name in “” - value not (numeric).
Everything worked yesterday, today it does not. Here debug info:
First expures refresh token, then invalid application ID.
Maybe we have a new app ID for Kia Connect (as oppsed to Kia Uvo app)
Any other suggestions ? Or is Fiddler the way to go
2022-02-07 10:03:38 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Refresh token started 2022-02-07 09:49:57.599383 2022-02-07 10:03:38.823751 True
2022-02-07 10:03:38 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Refresh token expired
2022-02-07 10:03:41 DEBUG (SyncWorker_7) [custom_components.kia_uvo.KiaUvoApiEU] kia_uvo - Get Device ID request {'ccsp-service-id': 'fd..0a', 'Stamp': '9...0=', 'Content-Type': 'application/json;charset=UTF-8', 'Host': 'prd.eu-ccapi.kia.com:8080', 'Connection': 'Keep-Alive', 'Accept-Encoding': 'gzip', 'User-Agent': 'okhttp/3.12.0'} {'pushRegId': 'f...D', 'pushType': 'GCM', 'uuid': 'fa...f3'}
2022-02-07 10:03:41 DEBUG (SyncWorker_7) [custom_components.kia_uvo.KiaUvoApiEU] kia_uvo - Get Device ID response {'retCode': 'F', 'resCode': '4017', 'resMsg': 'Invalid request value - Invalid Application Id. - 9994.394000053406', 'msgId': '88...782'}
2022-02-07 10:03:41 DEBUG (SyncWorker_7) [custom_components.kia_uvo.KiaUvoApiEU] kia_uvo - Retry count 0 - Invalid stamp 9o..90=
2022-02-07 10:03:41 DEBUG (SyncWorker_7) [custom_components.kia_uvo.KiaUvoApiEU] kia_uvo - Get Device ID request {'ccsp-service-id': 'fd..0a', 'Stamp': '9o3mpjuu/h4vH6cwbgTzPD70J+JaprZSWlyFNmfNg2qhql7gngJHgZp8DEsVTtI=', 'Content-Type': 'application/json;charset=UTF-8', 'Host': 'prd.eu-ccapi.kia.com:8080', 'Connection': 'Keep-Alive', 'Accept-Encoding': 'gzip', 'User-Agent': 'okhttp/3.12.0'} {'pushRegId': 'fL..aD', 'pushType': 'GCM', 'uuid': 'fab..f3'}
2022-02-07 10:03:41 DEBUG (SyncWorker_7) [custom_components.kia_uvo.KiaUvoApiEU] kia_uvo - Get Device ID response {'retCode': 'F', 'resCode': '4017', 'resMsg': 'Invalid request value - Invalid Application Id. - 10243.642999887466', 'msgId': '719e0e38-5649-40c2-baef-bfd3f4e3406d'}
2022-02-07 10:03:41 DEBUG (SyncWorker_7) [custom_components.kia_uvo.KiaUvoApiEU] kia_uvo - Retry count 10 - Invalid stamp 9...I=
Just for info, opening/closing charge port (I5/EV6)is done by calling below URL - Note the api/v2 in the URL as opposed the the other stuff on v1.
https://prd.eu-ccapi.kia.com:8080/api/v2/spa/vehicles/a0...10/control/portdoor HTTP/1.1
with Json message:
{"action":"open"}
{"action":"close"}
1 Like
Hello,
i set up your Kia Uvo / Hyundai Bluelink in Home Assistant a few days earlier for my new Hyundai Kona. I am still unable to login with my Hyundai crendentials
“Login failed into Kia Uvo / Hyundai Bluelink Servers. Please use official Kia Uvo app to logout and log back in and try again!”
Logout and log back in the Blulink App does not solve the problem, i tried multiple times…
I am stay in the EU/Germany.
I have no idea and need your help please.
Thanks
Rob