Big lag to refresh SOC with Enode and Citroën ë-C4
Dear, since I have started using the latest version 7.0 (5720) two days ago I have experienced a big lag in SOC refreshing. It did not happen to me in the previous version. I deleted the Enode setup and recreated but the issue still stays. My car is CITROEN eC4 54kwh
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments2
Linda ABRP
Feb 6
I got this answer from Enode:
“The underlying issue is a known limitation of Citroën's API. Looking at the logs for this specific vehicle, the last time fresh telemetry data was transmitted was on February 3rd at 18:50 UTC. Since then, the Citroën API has been returning cached data. This happens because the vehicle needs to wake up and actively transmit new data for the SOC to update.
Unfortunately, reconnecting the vehicle won't resolve this, as the limitation is on Citroën's side rather than with Enode. The end user may notice that data updates more reliably shortly after driving or charging, when the vehicle is awake and communicating.
Apologies that there's nothing more we can do here - this is a vendor limitation we're tracking internally.”
Linda ABRP
Jan 30
Hi
I can see that we get very little data from Enode from 23rd until now. I had another case but with a Citroën ë-C3 that also had issues with the Soc. The answer I got from Enode was that there is a bug on Citroëns side. I will make a report at Enode to see if it’s the same issue with your model.