End of drive/begin of charge missly received/detected resulting wrong drive stats

[Kytrix]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

It seems that teslamate/graphana sometimes misses some data.
Sometimes I saw that the end of the drive doesn't match the real data (battery level, efficency..)
here is an example of grapaha chart:

and here are the data from my HomeAssistant (data from Teslamate)

It seems there were a data gap at begin of the charge.

here is the data sumarized in the drives and charge tables:

Expected Behavior

The drive must be stopped before charging.

I understand this could be very tricky to fix (or nearly impossible without a dedicated algorithm)
but maybe:

• we could be inform that the data is inconsistent
• we could manually modify the end of drive/begin of charge to solve this

Steps To Reproduce

No response

Relevant log output

see attached zip

Screenshots

No response

Additional data

teslamate-db.zip

if you need other exports, tell me :)

Type of installation

Docker

Version

v1.32.0