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.

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

No window status on EV9 #1032

Open
patrickstanley opened this issue Feb 6, 2025 · 4 comments
Open

No window status on EV9 #1032

patrickstanley opened this issue Feb 6, 2025 · 4 comments

Comments

@patrickstanley
Copy link

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
USA, 2025 Kia EV9

Version of the integration
v2.35.2

Describe the bug
I just set up the integration with my 2025 EV9. There is no window status provided. The entity doesn't even display as existing. (As opposed to the entity existing but not having any data.)

Debug logs if an error occurred

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

To Reproduce
Install integration. Add 2025 EV9.

Expected behavior
Entities created which display the state of the 4 windows, matching the kia app.

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

Additional context

@Rebecca4546
Copy link

This would be lovely to add, although it doesn't look like window status is currently a supported entity in the ReadMe.

I did find the following entities in binary_sensor.py:

  • front_left_window_is_open
  • front_right_window_is_open
  • back_left_window_is_open
  • back_right_window_is_open

Wish I knew more to assist in troubleshooting...

@cdnninja
Copy link
Collaborator

Debug logs is what is needed. This is why the issue template requests it. The Data sensor attributes also would work.

@cdnninja
Copy link
Collaborator

Right now USA Kia has this setup but maybe it is wrong or a different place for EV9:

https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/blob/bf55258360b55fa48eb27a3d0d0fd442a5b00d29/hyundai_kia_connect_api/KiaUvoApiUSA.py#L394-L406

The logic of this integration is show anything that has data, otherwise don't. Once data shows up once it will display.

@patrickstanley
Copy link
Author

I wasn't sure if the logs would be useful or not since there wasn't an explicit error given.

Here they are with details redacted.

home-assistant_kia_uvo_2025-02-24T15-49-34.333Z.log

Not 100% that I am interpreting things right, but it looks like the data for the EV9 is structured as: lastVehicleInfo.vehicleStatusRpt.vehicleStatus.evStatus.windowStatus.windowFL instead of lastVehicleInfo.vehicleStatusRpt.vehicleStatus.windowOpen.frontLeft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants