-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
"Vehicle limit <xx%> reached" inconsistent with charge percentage #13902
Comments
Can you provide a log file? The in-vehicle limit should be shown as |
@naltatis - added log file, you see that at May 14 09:15:33 the first time that the update vehicle soc limit is 95%, this was set by the Tesla App. Note: The functionality itself is correct, only the displayed message seems to be incorrect. |
Ok, so looks like a pure UI and not a data problem. Thats good :D |
@GrafRudi I can't reproduce this. In the log you've provided, the vehicle is charging. This does not correlate with the state in the screenshot where charging has finished. But maybe a few details on how we update the vehicle soc value: By default, evcc only requests soc (and limit soc) infos from the vehicle when it gets connected or during charging. When charging has stopped, we don't continue requesting soc (and limit soc) data to allow the vehicle to enter sleep state. The soc usually doesn't change unless the vehicle is driven (disconnect) or charged again. Self-discharge or vampire drain is ignored here. With the limit soc from the vehicle it's different. You can change this at any time in the app, but we only update it during charging. So it's quite possible to get an out of sync state when changing limit soc while the car is not charging. Functionality wise, this should not be a problem. Increasing the vehicle limit soc afterwards will result in the car starting to charge until the new limit is reached because evcc keeps the charger enabled. Only decreasing an already reached limit will not reflect in the UI. The described default behavior can also be configured via If this does not explain your observed behavior, I need more logs and detailed reproduction steps that go along. |
I think here is nothing to do at the moment. @GrafRudi feel free to add comments here if your effect does not match the above explanation. |
Sorry forgot to answer, closure is ok |
Describe the bug
"Vehicle limit <xx%> reached" inconsistent with charge percentage. See attached picture
IMHO a low prio issue as the functionality works correctly.
Steps to reproduce
Assume an internal variable is not updated if charging limit is adapted while charging.
Configuration details
If really needed I can attach one
Log details
What type of operating system are you running?
Linux
Version
0.126.2
The text was updated successfully, but these errors were encountered: