Hi, could you explain where you get this information from? Is it out of the API or is it calculated? The reason I am asking is, that I cannot find them in the App and I want to know what is thebase for calculating the three different charging durations? I suppose different currents, but which value is behind which of these sensors? I also think they are sometimes a little off, since portable should be always the slowest, doesn’t it?
Please check data entity of the integration, they are all coming from the cloud (api)
ah yeah I can find this, which explains where the info comes from. Is there any documentation you used to identify these as the estimated charge times?
Hi.
Integration support region Russia (Bluelink Huyndai)?
Can be region RUSSIA added?
Is lock and unlocking the only commands that can be sent? IE I can’t adjust temp/start the car like I can from the app?
You can but it’s done using service calls rather than a pre-defined button/setting in the integration. The start_climate service call is pretty powerful depending upon the features of your vehicle, but you can for example tell the car to set the AC to 17 degrees or the heating to 22 degrees, turn on the heated stearing wheel, rear windows, seats etc. (again all depending on model) from the service calls.
Hi.
I have the same problem. How do you solved?
Regards.
Tracking the latest EU issue over here: [EU] Login fails: "Invalid request body - Invalid parameter." · Issue #348 · Hyundai-Kia-Connect/hyundai_kia_connect_api · GitHub
Issues impacting EU users for Kia and Hyundai brands, please get latest version of the integration, all is working fine now.
We are facing with another issue for Hyundai and Kia in EU region, integration becomes unavailable after some time with an error of invalid device id. Reloading the integration mitigates the problem until we have a proper solution in our hands
You should wait a few days, before you investigate further. If you take a look at the Facebook groups around KIA/Hyundai, people are complaining about problems with the app (and therefor the API) in the last few days. Seems to be they have some “in house” probelms at KIA/Hyundai. 
If I had to determine the time, I’d say some point last week.
I can’t pinpoint it down to something specific, as these user groups tend to be not really “techy”, and most people didn’t even know what I was talking about, when I was asking if they had done some typical steps to check if the app is even working…
Would someone be able to give me an example? Sorry for the dumb question.
Nevermind figured it out.
I see a sensor called My Sorento Set Temperature = 72. I think this is the temp the car sets at if I use the keyfob to start the car.
Can I change this value through the Uvo integration?
Hi, could you share some info about it?
I integrated my EV6 today, and your picture is perfect, I would like to copy… 
Thanks!
I think I shared it before on this thread, but happy to share again:
type: picture-elements
image: /local/images/kia-ev6.png
elements:
- type: state-icon
entity: sensor.ev6_last_update
style:
right: 0
bottom: 0px
margin-bottom: 0px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: sensor.ev6_last_update
style:
transform: initial
font-size: 0.8em
line-height: 2em
bottom: 0px
right: 30px
margin-bottom: 0px
color: black
- type: state-icon
entity: device_tracker.ev6_location
style:
right: 0
bottom: 0px
margin-bottom: 48px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: device_tracker.ev6_location
style:
transform: initial
font-size: 0.8em
line-height: 2em
bottom: 0px
right: 30px
margin-bottom: 48px
color: black
- type: state-icon
entity: sensor.ev6_odometer
style:
right: 0
bottom: 0px
margin-bottom: 24px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: sensor.ev6_odometer
style:
transform: initial
font-size: 0.8em
line-height: 2em
bottom: 0px
right: 30px
margin-bottom: 24px
color: black
- type: state-icon
entity: lock.ev6_door_lock
style:
left: 0
top: 0px
margin-top: 0px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: lock.ev6_door_lock
title: lock.ev6_door_lock
style:
transform: initial
font-size: 0.8em
line-height: 2em
top: 0px
left: 30px
margin-top: 0px
color: black
- type: state-icon
entity: binary_sensor.ev6_door_open
style:
left: 0
top: 0px
margin-top: 24px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: binary_sensor.ev6_door_open
title: binary_sensor.ev6_door_open
style:
transform: initial
font-size: 0.8em
line-height: 2em
top: 0px
left: 30px
margin-top: 24px
color: black
- type: state-icon
entity: binary_sensor.ev6_ev_charge_port
style:
left: 0
top: 0px
margin-top: 48px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: binary_sensor.ev6_ev_charge_port
title: binary_sensor.ev6_ev_charge_port
style:
transform: initial
font-size: 0.8em
line-height: 2em
top: 0px
left: 30px
margin-top: 48px
color: black
- type: state-icon
entity: sensor.ev6_ev_battery_level
style:
left: 0
bottom: 0px
margin-bottom: 0px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: sensor.ev6_ev_battery_level
title: sensor.ev6_ev_battery_level
prefix: 'Battery: '
style:
transform: initial
font-size: 0.8em
line-height: 2em
bottom: 0px
left: 30px
margin-bottom: 0px
color: black
- type: state-icon
entity: sensor.ev6_ev_range
style:
left: 0
bottom: 0px
margin-bottom: 24px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: sensor.ev6_ev_range
title: sensor.ev6_ev_range
prefix: 'Range: '
style:
transform: initial
font-size: 0.8em
line-height: 2em
bottom: 0px
left: 30px
margin-bottom: 24px
color: black
- type: state-icon
entity: binary_sensor.ev6_ev_battery_charge
style:
right: 0
top: 0px
margin-top: 0px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: binary_sensor.ev6_ev_battery_charge
style:
transform: initial
font-size: 0.8em
line-height: 2em
top: 0px
right: 30px
margin-top: 0px
color: black
- type: state-icon
entity: binary_sensor.ev6_ev_battery_plug
style:
right: 0
top: 0px
margin-top: 24px
transform: initial
font-size: 0.8em
line-height: 2em
'--paper-item-icon-color': black
- type: state-label
entity: binary_sensor.ev6_ev_battery_plug
style:
transform: initial
font-size: 0.8em
line-height: 2em
top: 0px
right: 30px
margin-top: 24px
color: black
Would you please share your configuration?
That would be nice
I can’t install the intergration via HACS.
When I want to add the repository http://github.com/fuatakgun/kia_uvo I get a error message Repository Hyundai-Kia-Connect/kia_uvo exists in the store…
How can I install this intergration?
Don’t add the custom repository, just search in HACS for “KIA” and you’ll find it. It is not necessary anymore to add a custom repository, because this integration is now HACS default. 
When I search for Kia in Hacs it can’t find anything, that’s why I tried to add the custom repository.
