Battery Incorrect Report - Drops to zero randomly

[eximo84]

Odd issue where the battery for a period of time showed 0% despite showing 90% previously.

This actually reflected the app until i forced a refresh to get the value back to normal. I've noticed this a few times with the bluelink app?

Maybe some logic to check for instant recharge of battery which couldn't happen unless the odometer increases or something is left on but even then it wouldn't be 90%-0%

[fuatakgun]

Checking sudden changes might look suitable for EVs but not suitable for PHEV, they have a range of 50km (9kwh) and decrease can happen so quickly. But I noticed that this is happening when car is still / not moving. If you can confirm this too, I can come up with a solution;

• if car was not running and is not running now and
• if EV battery decreased to 0% and previous value was not 0%
• initiate force_update.

[eximo84]

Yep car was stationary and hadn't moved. Logic sounds good.

[fuatakgun]

OOO for 2 weeks.

[TobiasLaross]

I have a related problem. I have an automation that if the car has less than 45% battery it is set to charge needed and will be charged until >65%. While charging, force_update is called once per hour during the blackout period. It is interesting that when charging was started it dropped to 0 and after it reached 65% it dropped again. And afterwards it dropped to 30% which was the initial level before charging started.

This makes me think that it has something to do with force_update and I was sleeping during this charging session but I have seen similar behaviour before and when opening the UVO application it also reported 0% until I hit refresh in the app. Do I need to trigger update after each force_update?

My workaround is now that charging needed is only set if charging needed has been off for 5 hours.

[cdnninja]

Maybe we either

1. Force a rescan if a 0 value occurs. I would think most people don't run a car to 0%.
2. Force a rescan when the value changes by more than X percentage from last value.

First one may be an easy approach but based on the above chart 0% doesn't seem to be the only issue as I assume your car didn't go from 35 to 100 in a single scan.

[dahlb]

I'm going to try to put this logic into a pr tomorrow

• if car was not running and is not running now and
• if EV battery decreased to 0% and previous value was not 0%
• initiate force_update.

[dahlb]

#144 should fix this, extra testers needed as it takes a while to repro, I'll be running for a few days and expect to see no errors and no more 0 logs