I use FiatUConnect version 12.1.0. I had trouble with FiatChamp and I've chosen not to upgrade to FiatUconnect 12.1.5 on basis of if not broken don't fix it.
In the early days of the 500e, the wake ups did have an adverse effect on the 12V battery, but car firmware updates a couple of years ago seemed to have overcome that.
I use the MyEnergi Zappi EV Charger and the Intelligent Octopus Go tariff which are ideal for UK. With that combination, I've got Home Assistant automations to work well, in particular only to request data from the car when needed rather than the fixed update rate.
What is available to you in your country might make this less easy.

I don't know how much of a Home Assistant expert you are. It does have quite a steep learning curve.

I could go into great detail on my use of Home Assistant. It might be best to PM me to exchange more detail.

Andy

 

My idea was to share the information here so others can potentially benefit from it.
I am too with Octopus, but in Spain . They have an Octopus Go tariff here too but I choose the non-EV specific tariff with 3 different price bands as it seemed more beneficial. And I use the scheduled charging which works pretty well, except for the issue of the HA integration's refresh causing it to start charging immediately when certain configuration is applied.
Going back to the topic of HA I have a little display in my hallway with basic information such as time, date, current and forecasted weather, electricity usage and the Fiat's battery percentage and remaining estimated milage. I would ideally want it as up-to-date as possible, but as I said earlier I'm a bit concerned about the car being "woken up" every 15 minutes or so as it was probably not how the electronics was designed and I don't want to cause an expensive issue.
Does anyone have a clue when the car reports anything to Fiat servers?
In an ultimate scenario I would like to have dashboard, with the following data:

• SOC (already have it)
• SOH
• remaining milage (already have it)
• average consumption
• daily milage (already have it)
• next service

I think some of those are impossible to get and the ones I managed to get can be a few hours old.

 

I wonder why you wouldn't just post it here to help others.

 

I am using IObroker to limit the charge level: https://www.fiat500owners.com/threa...t-value-e-g-80.155276/?post_id=1338424&nested_view=1&sortby=oldest#post-1338424
I am using this since 9 mo without any issue, every AC charge session at home or on the road is controlled / limited by the IObroker script.
The IObroker adapter does not wake up the car when refreshing the object values. It only polls the mopar server (I set the interval to 10 min). The car pushes the last values up to the server when closing the door after shutting down, and when plugging in for charging.
The only function waking up the car is "remote/deeprefresh" . This is only required during charging, since the car is not updating the charge level by itself, probably to avoid losses by control unit consumption.
(Edit: of course other refresh functions, e.g. location refresh, or switching climate / lights / door locks will also wake up the car, and should be avoided unless plugged in)

Since IObroker is open source, you could compare the codes, where apparently the IObroker adapter is coded more cleanly. Make sure that your adapter is not toggling the "remote/deeprefresh" value unless the car is plugged in and charging.

 

Ya post your stuff here, I pick my car up next week so will be playing with HA to see what I can do.

 

I have been reluctant to provide details on my approach because my solution is highly dependent upon my EV charger type and my electricity supplier's interface with that charger and I felt it might serve to confuse rather than assist.

The key issue I had when first using either of the FiatChamp or FiatUConnect Addons was that if one set too high a data rate the 12V battery would get flattened. Firmware updates to the car in 2022/23 reduced, but didn't eliminate, this risk.

Also there was a risk, which I think remains today, that too many interrogations in a day would lock out your connection to the Fiat servers.

The approach I adopted was to set a low update rate in the add-on configuration and to interrogate the car more frequently during charging. The outline of the HA Automation I use follows:

triggers:
- minutes: /15
trigger: time_pattern
conditions:
- condition: state
entity_id: binary_sensor.zfaexxxxxxxxxxxxx_evinfo_battery_chargingstatus
state: "on"
enabled: true
actions:
- data: {}
target:
entity_id: button.zfaexxxxxxxxxxxxx_deeprefresh
action: button.press
mode: single

I hope this is some help.

 

I thought I would share my dashboard. I wanted to have a calculated average consumption based on the power meter's reading that I attached to the charger, so it includes charging losses too, which is the real consumption in my opinion. One challenge with it is to include public charging too, otherwise the value is not accurate. Since I can't integrate with all the possible public charging networks I decided to use a manual input field that I always increase with the amount I charged at a public charger. It was tricky to achieve it and is still not perfect, but now I have a fairly accurate value of it.

 

It's really cool! Especially taking into account that almost everybody else forgets or just ignores charging losses, which is unfair

 

There are a few PIDs on the IDCM module that may have some interest for you:

 

All of those are of value if one is able to access data through the OBD port.
However, none are supplied over the API which Home Assistant can exploit (unless I'm missing something)

 

The data is coming from the OBD2 port. I don't know if there a public sheet with ECU number / PID number to get them. If not, I can sniff the traffic from the Autel box to the OBD2 port, and publish the info here.

 

Serious question. What if any effect does HA have on the driving experience, range etc or is this about max efficiency?

 

I use Home Assistant to get reports of the car's main battery State of Charge via the Fiat servers in conjunction with HA integrations to control my Zappi EV Charger.
It has no effect on the car when moving or efficiency or performance. The only potential downside is that one has to be careful that HA doesn't interrogate the Fiat servers for data too frequently, otherwise one can have problems. See my earlier posts.

 

You might want to check if your car's Bluetooth presence is being detected reliably—mine had issues until I tweaked the connection timeout. Also, for anyone trying to sync smart home stuff, my door alerts started working better after linking with my https://www.vivint.com/products/doorbell-camera setup. It helped with keeping notifications in sync when coming or going, especially when paired with location-based triggers.

 

Just FYI some time ago I wrote a native Python integration for Home Assistant: github

Me & the guy behind of one of FiatChamp forks are maintaining it a bit, but it looks mostly complete & working unless Stellantis breaks anything...

 

This is amazing, great job!!

• Imports statistics like battery level 🔋, tire pressure ‍💨, odometer ⏲ etc. into Home Assistant
  [*]Multiple Brands: Fiat, Jeep, Ram, Dodge, Alfa Romeo, Chrysler & Maserati
  [*]Multiple Regions: America, Canada, Europe & Asia
  [*]Supports multiple cars on the same account 🚙🚗🚕
  [*]Location tracking 🌍
  [*]Live vehicle status such as windows/doors, and ignition status for supported vehicles
  [*]Home Assistant zones (home 🏠, work 🏦 etc.) support
  [*]Uses the same data source as the official app 📱
  [*]Remote commands (unlock doors 🚪, switch HVAC 🧊 on , ...). Use a service (action) to trigger commands. Some commands may not work with all vehicles

 

Seems there is some confusion here.
1. The SGW is restricting write access on the wired Can / OBD2 interface. This is only powered when the car is switched on. Therefore, OBD2 cannot be used to read from or control anything in the car when the controllers are in sleep mode, while the car is off / parked. Some write access can be purchased outside of the Fiat system, described in ETS' link collection.

2. A totally different thingy is the mobile network link of the car. The car has a 4G mobile network module + sim in the u-connect system, that allows for outgoing calls (SOS and Fiat assistance) as well as for a data link through the 4G mobile network. To use this latter system, you need to subscribe and pay for one of Mopar's data plans (comparable to a mobile phone subscription). The Mopar servers are connecting to the car wirelessly, allowing for some remote control and data retrieval. Polling the car through the servers is waking the BCM and Uconnect from sleep temporarily even when the car is off / parked.
All existing remote solutions including the above HA, IOBroker, or Fiat app, are using this route.

These two data bus systems are totally separate.

 

I was referring to an OBD2 reader that connects to the internet through Wifi (whether it's the car's or in/around the garage doesn't matter) and can push the readings to HA, while the ignition is still on.

 

Its all about finding the right cable pairs and bypass the SGW.

 

If you try this @Karlmb, do let us know what success you have.
Remember the 500e has 3 independent CAN-buses, you'd need to find 3 break-in points.