Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Two EVs in one Bluelink Account: second EV not recognized as EV but fossil car #758

Open
aswdo opened this issue Nov 24, 2023 · 22 comments
Open

Two EVs in one Bluelink Account: second EV not recognized as EV but fossil car #758

aswdo opened this issue Nov 24, 2023 · 22 comments

Comments

@aswdo
Copy link

aswdo commented Nov 24, 2023

Please check Services, Known Bug / Issues and Troubleshooting over here first: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
Region and Brand of car
Germany, 1st EV : Kona Electric 2020, 2nd EV: Kona Electric SX2 2023

Version of the integration
newest 20231124

Describe the bug
Integration works well for first EV (Kona 2020).
After adding a second EV in Bluelink App, also in integration the new car popped up.
Unfortunately the second car has been identified as fossil car although it is an EV too.

My assumption: as the new Kona Electric is pretty new it might not been listed as EV yet.

Debug logs if an error occurred

Outlined here: https://github.com/fuatakgun/kia_uvo/blob/master/README.md

To Reproduce

Expected behavior

Thanks for checking!

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
@cdnninja
Copy link
Collaborator

cdnninja commented Nov 24, 2023 •
edited
Loading

Will need some debug logs of the vehicle info to figure this out:

Here is the logic for EU today:

entry_engine_type = None
  if entry["type"] == "GN":
      entry_engine_type = ENGINE_TYPES.ICE
  elif entry["type"] == "EV":
      entry_engine_type = ENGINE_TYPES.EV
  elif entry["type"] == "PHEV":
      entry_engine_type = ENGINE_TYPES.PHEV
  elif entry["type"] == "HV":
      entry_engine_type = ENGINE_TYPES.HEV

I am interested to see what "type" your car is reporting in the debug logs.

@aswdo
Copy link
Author

aswdo commented Nov 24, 2023 via email

@cdnninja
Copy link
Collaborator

cdnninja commented Nov 24, 2023 •
edited
Loading

You did the right steps. Now go into settings> system>logs> go to the bottom and click load full logs. If you can't find it in that in a different tab restart the kia integration. You should see the API logs dumping responses from the servers. One of the early login ones should have that "type" It won't be entry_engine_type. That is our name for it.

@cdnninja
Copy link
Collaborator

It also may be in the "data" sensor's attributes. Not sure though.

@aswdo
Copy link
Author

aswdo commented Nov 24, 2023 via email

@cdnninja
Copy link
Collaborator

That power item is something that should be improved in latest release.

Data sensor is a sensor on the car device.

As mentioned the entry_device_type is our value not the api. You are looking for type. If can't can't it post the logs.

@aswdo
Copy link
Author

aswdo commented Nov 24, 2023 via email

@cdnninja
Copy link
Collaborator

Both data points show as EV in logs. Can you screenshot where it shows ICE?

@aswdo
Copy link
Author

aswdo commented Nov 25, 2023 via email

@cdnninja
Copy link
Collaborator

Does look to show up.

@aswdo
Copy link
Author

aswdo commented Nov 25, 2023 via email

@cdnninja
Copy link
Collaborator

I still don't see a screenshot. I also need the integration version number. The number above is home assistant version not integration.

@aswdo
Copy link
Author

aswdo commented Nov 26, 2023 via email

@cdnninja
Copy link
Collaborator

I still don't see them. I don't think attaching by email works. Please confirm you see them in github.

@aswdo
Copy link
Author

aswdo commented Nov 26, 2023

IMG_2716
IMG_2717
IMG_2718
IMG_2719

home-assistant_2023-11-26T08-58-55.262Z.log

@cdnninja
Copy link
Collaborator

I don't see a spot where it is showing as ICE. What I do see is you are missing sensors you would expect to see such as as charging levels?

@cdnninja
Copy link
Collaborator

Looks like the same issue as Hyundai-Kia-Connect/hyundai_kia_connect_api#440 and #760

@aswdo
Copy link
Author

aswdo commented Nov 27, 2023

Exactly! Kona2 ist integrated and displayed, but almost all EV-specific sensors are missing. So my assumption was that Kona2 is identified as ICE and not as EV.
Sorry again for not being precisely enough 😞

@aswdo
Copy link
Author

aswdo commented Nov 29, 2023

Here another screenshot showing the ICE related sensors
IMG_5728

Fuel status seems to be ICE- related.

What could be checked: as Ioniq 5/6 have nearly the same infotainment and sensors as the new Kona Elektro, why not treating Kona as it would be an Ioniq 5/6? Worth a try …..

@cdnninja
Copy link
Collaborator

We aren't treating them any different. We are displaying all data provided by the api in both cases. API looks to have changed.

@aswdo
Copy link
Author

aswdo commented Nov 29, 2023

Layout and functionality of the Bluelink App has changed for the new Kona. It is also different from Ioniq 5/6, so my approach wouldn't work.

This is probably the cause for the changed API and finally for missing sensors in your integration.

Thanks so far for your support! I will be patient and wait for new API adaptions .....

@cdnninja
Copy link
Collaborator

Someone with one of these new layouts needs to sniff the traffic and provide that for us to solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cdnninja @aswdo