-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Minimum charging amps #77
Comments
I was wondering about the same thing. Have you figured out what the actual limit is? |
I've read in the past that values below 5A need to be sent twice through the API to be accepted from the car. |
Bump Can double sending < 5 A commands be implemented? |
Hi Jonas, did you try if it was working ? You can use the HA Developer Tools to send twice the command, but there's no way to really know if the command was accepted .. via the Tesla APP is says 5A, and on the Tesla itself, same .. |
If I send for example 3 A, it sets the current to 5 A. If I sent 2 A afterwards, 2 A will be set. The app also says 2 A then |
This was found on tesla_ble_mqtt too already and they just fixed it by sending 2 commands when charging amps is below 5A. Would be great if @yoziru could add a similar fix 🤩 |
The minimum charging amps slider has a range from 0 - 16 (set at charging_amps_max).
When setting the slider to below 5amps the car seems to have a minimum (as per app) limit of 5amps so will default to that value.
Is there any way to set a charging amp value below 5amps. The app cannot go below this however using the API connection this is possible (however rate limited) but not preferable due to rate limits.
I guess if 5amps is infact the hard limit over ble than the slider should have a hard limit.
substitutions:
ble_mac_address: !secret ble_mac_address
tesla_vin: !secret tesla_vin
charging_amps_max: "16"
From cliemt.yml
number:
name: "Charging amps"
id: charging_amps
icon: mdi:ev-station
unit_of_measurement: "A"
mode: slider
min_value: 0
max_value: $charging_amps_max
The text was updated successfully, but these errors were encountered: