-
Notifications
You must be signed in to change notification settings - Fork 33
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
chargingInstantaneousPower on Zoe50 #354
Comments
Thanks @kamahat Do you want to provide a PR? It would be useful to have a new method like renault-api/src/renault_api/kamereon/models.py Lines 192 to 199 in 7c2336c
|
I'm not able able to provide a PR since programing in python is not my cup of tea.
I'm not able able to provide a PR since programming in python is not my cup of tea. But I hope someone would be able too do it with the good input :) |
Can someone confirm that the unit is in kW ? Personally I've got a Zoe5.0 connected to a Hagger Witty Charger on mono-phase so limited ot 7.4kW. My conclusion is that de Charging Power unit is not in kW but in Amperes |
And that would need a PR. |
Sadly, there is no "official" documentation on the Renault API. There are related discussions: For HomeAssistant, this would need to be a PR on the home assistant core. |
@kamahat sorry but those calculations don't seem right to me. I'm charging at 10A (would be 2300W@230V) and |
@fabiopedrosa do you propose a better calculation? |
Just for the records: on my Captur PHEV this value looks completely invented, varying between 2.0 and 3.2 while charging using the 2.3kW/10A/230V home charger. It is != 0 even when no charging... |
Hi, I think (almost 100% sure) that this is the maximum allowed charge power. When at 100% soc this value reduces to e.g 3.5kW, and I can see that the consumed charge power also reduces to 3.5kW. |
the right values for chargingInstantaneousPower seems to be :
TrueChargingValue (W) : chargingInstantaneousPower * K * sqrt(2)
with 120=2*12 *1000 *(5/362)]
Does someone has the same value for K ?
The text was updated successfully, but these errors were encountered: