search

Hyundai-Kia-Connect / kia_uvo

A Home Assistant HACS integration that supports Kia Connect(Uvo) and Hyundai Bluelink. The integration supports the EU, Canada and the USA.
MIT License
391 stars 81 forks source link

Charge limit is pulled back to 100% after the HA extension has lost connection #810

Closed DavyLandman closed 5 months ago

DavyLandman commented 5 months ago

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 EU, Ioniq 5

Version of the integration 2.19.0 (I've been running the extension for a year now)

Describe the bug

Since 20-01, the charge upper limit is randomly put back to 100%. It took me a long while to figure out what is happening. But I'm quite sure it's something that HA integration is causing.

What is happening is that I tend to have it at 80%, but I noticed it would be back at 100% at a later point. I've tried using the bluelink app, and the car to set it to 80, it just wouldn't stick.

Then I noticed a pattern in HA, just before the "bump" back to 100, the connection would be dropped (or the limit would be at 0%)?

image

and more detail.

image

Debug logs if an error occurred

I've not been able to capture it, but I've enabled debug reporting.

To Reproduce

Expected behavior

Keep the charge limit at 100%

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

Additional context

there are no automations enabled around the car.

cdnninja commented 5 months ago

Enable debug logs outlined in the readme. Watch for a set command. I highly doubt this is the integration.

DavyLandman commented 5 months ago

It happened again.

From 6:28 till 9:59 it was at 0%, and then jumped to 100%.

2024-02-01 05:28:35.288 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 2.246 seconds (success: True)
2024-02-01 05:58:36.914 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.871 seconds (success: True)
2024-02-01 06:28:58.893 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 21.852 seconds (success: True)
2024-02-01 06:59:00.750 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.709 seconds (success: True)
2024-02-01 09:29:15.046 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 2.004 seconds (success: True)
2024-02-01 09:59:16.747 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.706 seconds (success: True)
2024-02-01 10:29:19.655 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 2.613 seconds (success: True)
2024-02-01 10:59:20.436 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.395 seconds (success: True)

The logs show nothing (except that the one that dropped it to 0%) took suddenly 21s to return. I'll close the issue, sorry for noise.

image