Tesla: in PV mode, charge always starts at 5A despite min current being set to 1A, causing start/stop oscillation #13007
Comments
|
Take a look at #12427 |
|
Hi. I checked #12427 which indeed look similar, but I think I'm in a slightly different situation here, as the issue I observe is cycle of start/stop of charge. I wouldn't mind if it was starting at 5A and reduce the current afterward, but this is not the case. Unless I manually change something, the charging is not working properly and I'm sure a solution to that could be found (even a workaround, like sending again the desired current until Tesla take it into account ;-)) |
|
@FraBoCH could you kindly set |
|
In #12427 (comment) it seemed as if evcc sent the right command but is was ignored by the vehicle. Please provide log of MinPV (working) and PV (not working). |
This comment was marked as resolved.
This comment was marked as resolved.
|
I cannot test with pv mode now as there is no more sun. However, I've made some progress investigating this issue with the following steps:
So as I see it, tesla reduce the power but is somewhat "blocking" at 5A when going down, requiring an additional request to go further down in power. In other words, evcc cannot assume tesla executes properly the set_charging_amps and should resend the request until the actual charge power match the expectation. Here is the corresponding log, with the tesla trace: |
|
a while ago, "under 5A" worked only if the set_charging_amps was sended twice (this was only requierd for values 1-4A) |
|
Good input, thank you. I was already wondering what made the difference. Sounds like a bug in the Tesla Fleet api that should be fixed? |
|
That was with the old unofficial API. |
We could try doing something like "send command twice if power <5A and last value >=5A". |
This looks like a possible workaround.
I would be happy to beta-test a fix. |
|
Würde das als damaliger Ersteller von #12427 natürlich auch gerne testen. |
|
Vielleicht hängt das auch damit zusammen, dass man in der Tesla App den Strom nur auf minimal 5A stellen kann. Ich hoffe, dass die Möglichkeit per API da drunter zu gehen nicht nur ein Bug ist, den Tesla irgendwann schließt... |
|
Naja, wirklich Sinn macht das ohnehin nicht, denn auch Tesla kann nicht zaubern. Das hier ist daher wenn dann nur nach dem Motto: "Weil es geht". |
|
alte Teslas ziehen bis zu 300W beim "rumstehen", neuen um die 150W. So oder so, mit "Ab 1A" muss man nicht mit Phasenumschaltung spielen. Einziger Nachteil bleibt nur noch ca. 700W Schritte (bei 3ph) |
|
Ich habe leider nur eine 1,75kWp PV. Da bin ich auf die niedrige Stromstärke angewiesen. Und es funktioniert auch besser als erwartet. Die Effizienz ist so bei 75% Minimum laut Teslamate. Normalerweise ist sie sogar eher bei mindestens 80-90%. Hat zumindest selbst an eher durchwachsenen Tagen wie den letzten 2 dafür gereicht 10% in die Batterie zu bekommen. Wenn das Wetter konstant sonnig ist, kann ich so wahrscheinlich teilweise komplett nur mit PV laden, da ich regulär nicht viel Auto fahre, besonders bei gutem Wetter. Und ich kann mir einen Heimspeicher sparen. edit: Habe gerade mal mit Scan my Tesla nachgesehen und mein 2023 Model 3 hat im aufgeweckten Zustand einen Verbrauch von 110-140W. Das deckt sich dann mit den Werten von Teslamate und es macht definitiv Sinn auch unter 6A zu laden, wenn man wie ich nur eine kleine PV hat und ansonsten den Überschuss verschenkt. |
|
Könnte jemand #13099 testen wenn ich das in einem Docker Build zur Verfügung stelle? |
|
@andig |
Sollte machbar sein. Es muss aber natürlich auch das Wetter mitspielen. |
|
Build läuft, Tag |
andig
added
enhancement
|
It's the first time I'm running evcc docker image so I may be doing something wrong. But the vehicle fails at creation: So then, quite logically, I get a "vehicle not capable of current control" whenever trying to change something. |
|
Ups- scheint mein local build wäre nicht erfolgreich gewesen. Probiers bitte nochmal. |
This comment was marked as resolved.
This comment was marked as resolved.
|
Same result with :testing image. The logs are quite similar to what happens when I try to build & run locally without a proper TESLA_CLIENT_ID, maybe this is what's missing in your build ? |
|
Sorry for the confusion. |
This comment was marked as resolved.
This comment was marked as resolved.
|
Thanks. Added the function but never called ;). New |
|
We are almost there ! Here is the corresponding logs extract: |
|
Test is successful with latest :tesla image. Thanks a lot @andig ! Looking forward to see this fix in the next release |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@Neffe1337 mach bitte ein neues Thema. Dieses hier ist gelöst. |
Describe the bug
I have a Tesla charging on a Tesla Wall Connector Gen 3 (twc3). I configured the min current on the loadpoint to 1A (~700w with 3 phases) to charge even with few excess power.
The problem is that in PV mode, the charge always starts at 5A, thus using more current than available and stopping, then starting again, and stopping, ....
In Min+PV mode, the 1A is properly sent to the vehicle and taken into account. So the charge starts at ~700w and then increase/decrease properly with the available solar power in excess.
Steps to reproduce
Configuration details
Log details
What type of operating system are you running?
HomeAssistant Add-on
Version
0.124.10
The text was updated successfully, but these errors were encountered: