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

Battery drain despite of refresh=false #278

Open
cr0ste opened this issue Apr 20, 2024 · 2 comments
Open

Battery drain despite of refresh=false #278

cr0ste opened this issue Apr 20, 2024 · 2 comments

Comments

@cr0ste
Copy link

cr0ste commented Apr 20, 2024

Describe the bug
I'm using blulinky in my home automation and I request the status every hour.
I'm explicitly doing it with "refresh: false" parameter in order to avoid a battery drain in my car. As double-checked in another issue discussion, this should only fetch the cached status from Kia server and no request to the car should happen, to save it's battery.

Unfortunately this is not true at least in my scenario.
During the last months we often had a completely empty 12 V battery and unfortunately I blamed Kia and they didn't find any issue.
Now I bought a battery monitor (https://amzn.eu/d/b5nsRNh) and noticed that clearly the car is woken up by the blulinky requests. On every blulinky request I see a short drop in voltage of car battery, which recovers after ~1 minute.

Please don't get me wrong, I'm not blaming you and this great adapter. I guess there's something special at my side (e.g. my implementation, car, EU region) and I would like to understand it.

Would you have any idea why this unexpectedly happens?
I try to summarize my code here:

let client = new BlueLinky({
                username: kiaConfig.username,
                password: kiaConfig.password,
                brand: niroEVConfig.brand,
                region: kiaConfig.region,
                pin: niroEVConfig.pin,
                useInfo: false,
                autoLogin: false
            });
const response = await client.login();
req.vehicle = await client.getVehicle(niroEVConfig.vin);

let status = await req.vehicle.status({ refresh: false, parsed: false });

Usefull info(please complete the following information):

  • OS: Linux, Alpine
  • Bluelinky Version: 8.2.1
  • Region: EU
  • Brand: Kia (Niro EV SG2 2022)

Additional context
See discussion on closed issue #184

@cr0ste
Copy link
Author

cr0ste commented Apr 24, 2024

Issue is reproducible by using the official app without refresh.
Kia Connect support says:
"it might happen, that a certain communication between the app and the vehicle can take place upon opening the app (or even in the background), as for example the localization the alarm and security features are automatically triggered. You can of course try turning these these off in the App via more -> Servicelist.
Nevertheless, like I've said before, just using the app cannot drain your 12V Battery dry, it's technically not possible."

So I would say blulinky is doing it right, but it should be documented that each request wakes up the car (even though Kia says it should not fully drain).
I can raise a PR on my own if you agree.

@neoPix
Copy link
Contributor

neoPix commented May 13, 2024

This is stated in the warnings section of the README of this repository here : https://github.com/Hacksore/bluelinky/blob/master/README.md#warnings

Nonetheless, feel free to push a PR if you have an idea on how to tackle this.

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

2 participants