-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Tessie: number.tesla_charge_current limited to 16 #118302
Comments
Hey there @Bre77, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) tessie documentation |
The charge range is based on what's returned by the Tesla API and should match what's in your Tesla app. Ensure your vehicle is plugged in, check the Tesla app, and if it's still limited to 16A in Home Assistant send a diagnostic. I cannot support what shows up in Node Red, so let's make sure Home Assistant is correct. |
Thanks for the feedback @Bre77, it seems that when the cable is connected and not charging it is set to 16. but when charging it can be adjusted to 25, odd. |
That is a little odd indeed, what type of charger? I get to select up to 32 as long as my Wall Connector 3 is plugged in, but I get 16 when unplugged. |
It's a Shell newmotion advanced 3.0 level 2 charger |
Right, the last two things to validate is does the Tesla and Tessie Apps also limit you to 16 Amps when plugged in but not charging? If so there is nothing I can do. |
thanks for your time and help. it is the same in both. i'll have to make do with 16 amps :) |
The problem
Hi,
is there any way to extend the range for this entity?
trying to implement solar charging via node-red and getting the following
"HomeAssistantError: Validation error: Value 21.0 for number.tesla_charge_current is outside valid range 0 - 16"
What version of Home Assistant Core has the issue?
2024.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
tessie
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: