#Debugging hyundai_kia_connect_api pincode issues

1 messages · Page 1 of 1 (latest)

elder halo
pallid totem
#

Could you try 48.7? I realized 48.6 fixes root cause but config data would be messed up and carry over. .7 repairs the data too.

#

I think I know root cause though.

elder halo
#

Sorry I just saw this but yes I tried .7 already. I deleted and created it again now and will see if that helps at all

#

@pallid totem separate question - is there a reason that the polling of the cached state is limited to 15 minutes? I'd prefer to drop it to 1 minute and I did setup an automation to just run the action manually to catch any updates coming from the car when it chooses to send data to bluelink but it's kinda there to work around the integration refusing to do it faster.

#

to be clear I'm not talking about force updates

pallid totem
#

They do have a limit on total API calls. Trying to also stay off kia's radar. They are very aware of us and my impression aren't fans.

#

Force updates also wake the battery and due to really poor BMS on the cars can kill them.

#

At one point even non forced refresh would wake the car - was a bug on the kia / hyundai server side.

elder halo
#

my biggest gripe with this integration compared to what I've done with the toyota one is that I can't easily / quickly get feedback on actions - maybe I'm just doing it wrong but when I send an action I seem to need to request updates manually to get info on whether it worked which is no fun

#

maybe this issue will fix it better but it just seems like with the long latency it's kinda hosed - for example I tell it to lock the doors, I get a notification from myhyundai mobile app saying the doors are locked (indicating the server cached state is updated), but the integration doesn't update for quite a while to show that they are locked

#

super frustrating that you have to use the client id / secret I assume from the mobile app - they need to get their act together

#

@pallid totem I did close the issue - appears to be fixed. Thanks so much 🙂

pallid totem
#

Which region are you again?

#

A lot of that boils down to reverse engineering each regions api.

elder halo
#

USA

pallid totem
#

USA Hyundai right?

elder halo
#

Yeah

pallid totem
#

USA Hyundai and Kia are totally different. Other countries they are the same.

#

Europe for example has an api we can call to check for status for when it’s finished and if successes. We can call that in a loop and update when we hear back. That feature has been broken for a bit.

Would need someone to sniff the traffic for Hyundai usa to see if it has the same.

elder halo
#

Are you typically just MITMing the mobile app?

pallid totem
#

Yeah. I haven’t in years but people in each country do yeah.

elder halo
#

Is that documented anywhere? I’d be happy to try to contribute / compare

pallid totem
elder halo
#

I guess if I figure anything out I'll look into a PR or at least putting the info in a ticket.

pallid totem
#

If you manage to capture and find a loop for action completion should be easy to add.

elder halo
#

annoyingly the ios app has a pinned certificate so will require more hoops to mitm it