[Ovmsdev] Fiat500e Quirks

[William Reading]

Howdy there,

I recently got an OVMS set up with my Fiat 500e and was happy to see that it works, but I noticed noticed a few oddities.

The first one is that it uses Valet Mode (CommandActivateValet) for preconditioning instead of CommandClimateControl:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/bd192f5c1bf7ea77d94bf6e504cefa55f6365f5c/vehicle/OVMS.V3/components/vehicle_fiat500/src/vehicle_fiat500e.cpp#L550-L577 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/bd192f5c1bf7ea77d94bf6e504cefa55f6365f5c/vehicle/OVMS.V3/components/vehicle_fiat500/src/vehicle_fiat500e.cpp#L550-L577>

Is there a downside to changing the code to where it uses Climate Control instead? It seems like that would fit better with the intended functionality.

The other is that it seems to rapidly generate spurious charging / not charging events, which en masse seems to make the websocket connection on the web server time out.

I can put together a pull request to try to fix these issues, but was wondering if there are any thoughts on these two things before getting started. There's also no pictures of the Fiat on the iOS App, but I assume that's because the last release of the iOS App predates support.

Thanks,
William Reading

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20220222/811245df/attachment.htm>