-
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
Considerable Success but Some Issues with FiatChamp #45
Comments
hi 😀
|
1 is not urgent and not vital. Firstly, the earliest I'll take delivery of the Alfa Giulia is September . Secondly as it's an ICE not an EV, I would only be using FiatChamp for the car's general data not for controlling it. In short, I'm very relieved that the lock out was temporary and I'll be further exploring how I can make best use of FiatChamp over coming days. Many thanks |
do you mean the charging level inside the car settings ? LOW to HIGH in 5 steps ? i got a 500e myself and this is NOT the same as the charging level over the api. i got confused about this myself but after reading the wikipedia page you can see there are only 2 charging level standards right now LEVEL_1 and LEVEL_2 and this is what the api reports. https://en.wikipedia.org/wiki/Charging_station |
Yes it was the 5 levels set from inside the car I had in mind. |
Update: Daytime - if the domestic storage battery's State of Charge is above a user defined threshold, an Automation commands my charger to commence charging (so long as FiatChamp shows the car_evinfo_battery_pluginstatus to be true). Another Automation will terminate charging when the domestic storage battery's SoC drops below a second threshold. By this means, I am preventing the storage battery getting to 100% and preventing Solar energy being fed to the Grid. (I am not paid for any energy I feed to the grid.) My mileage is such in sunny weather in spring, I am charging the car solely from solar energy. In winter, I rely more on the grid. |
Great work with FiatChamp, wubbl0rz!
I've been struggling to control the charging of my La Prima for over a year.
My solar system includes a GivEnergy hybrid inverter and 8.2kW domestic battery and a Zappi2 charger.
I was unable to control the car's charging as I would wish until I realised last week that FiatChamp was available.
I’m now using FiatChamp in conjunction with myenergi and GivEnergy integrations to great effect.
I charge the car overnight up to a manually entered SoC threshold.
In the daytime, I initiate charging if the domestic battery's SoC exceeds a high threshold and to cease charging if it drops below a second lower threshold.
There do seem to be some anomalies when using FiatChamp with my April 2021 La Prima, which I believe has all software updates up to about 6 months ago.
The drain on the car’s 12V when BatteryRefresh is set true is a concern. To offset this effect, I tried setting the refresh interval to a high number, however FiatChamp seems to effect refreshes every 15minutes whatever number is set in its configuration.
To reduce the 12V battery drain, I have chosen to set Force Refresh Battery Status false and have my HA automations request a battery refresh just at times when the car’s SoC is needed by them.
Today, just after I’d gone for a short drive throughout which FiatChamp was reporting valid data, FiatChamp has started logging ‘Wrong Pin?’ following each BatteryRefresh attempt. The Fiat iPhone app is still working fine with my normal pin. I’ve tried everything on HA including a re-install of FiatChamp to no avail. The Fiat System must have got confused. Hopefully, it will sort itself out.
I’m finding that the car’s battery charging level is reported as Level_2 whatever is selected in the car. I’d really like FiatChamp to be able to manage the car’s charging level. Perhaps the Fiat API doesn’t permit this.
I will be getting a new Alfa Romeo Giulia soon and I’d like FiatChamp to collect both cars’ data without having to restart FiatChamp each time after changing ‘Brand’ from Fiat to Alfa Romeo and vice versa.
The text was updated successfully, but these errors were encountered: