Skip to content
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

Fiat 500e not showing charging status #964

Open
pfwolbers opened this issue Jan 11, 2024 · 5 comments
Open

Fiat 500e not showing charging status #964

pfwolbers opened this issue Jan 11, 2024 · 5 comments

Comments

@pfwolbers
Copy link

I've just installed the ovms module in my fiat 500e (2015).
I can see the soc and lock doors etc.
But when i charge the car (granny charger) it is not detected by ovms.

Not charging
SOC: 64.0%
Est. range: 65km
ODO: 74587.0km

@pfwolbers
Copy link
Author

State is not chowing correctly in app and webpage, but is showing correctly at mqtt server.

@dexterbg
Copy link
Member

You should check your server v2 connection & configuration then, as there is no difference regarding state data source between v2 & v3 (MQTT) transport.

@pfwolbers
Copy link
Author

I checked the metric list:
v.c.charging yes

Webpage:

Vehicle
Not charging
SOC: 71.0%
Est. range: 79km
ODO: 74645.0km

Server
State: Connected
OVMS V2 login successful, and crypto channel established
State: Connected
OVMS V3 MQTT login successful

@dexterbg
Copy link
Member

v.c.charging is only one part of the charging state info. The web page displays v.c.state, and for a minimum charge state record, the vehicle also needs to supply the charge port state v.d.cp.

The Fiat 500e module source has logic to supply these. If that doesn't work correctly for your model, you should contact the module developer, Günther Huck. Check out his blog: http://fiat500e.eu/

@pfwolbers
Copy link
Author

Ok, thank you. Both metrics have no data. So that will be the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants