Hi,
Have you noticed that OVMS module on charge start event is beeing fired twice (the second one after 40 seconds). I'm receiving the charge notification twice on the smart phone. Then I've tried to write a sigle "print('test')"; on the "vehicle.charge.state" event and can see that the start charge and stop charge envent run twice each one.
I mean,
vehicle.charge.start ---> fires on charging the EV, then
vehicle.charge.stop ---> fires after a few seconds (inmediately), then
vehicle.charge.start ---> runs againg after 40 seconds
I'm using the OVMS on a Hyundai Kona EV, but it seems something generally because I have a friend with an Opel Ampera and other with a Nissan Leaf and are experiencing the same issue. We all are running Firmware Version 3.2.015
Not sure if you're aware that "vehicle.charge.state" isn't coupled to the ".start/.stop" events, and the ".start/.stop" events don't trigger a notification by default. ".state" is triggered by changes of metric "v.c.state", ".start/.stop" reflect changes to "v.c.charging".
I've never before heard of this, and 3.2.015 has been in use for quite a while. I suggest checking if you're all running a specific plugin and try disabling that.
Please provide a log excerpt at level "debug" if that's not the case.
Regards,
Michael
Thanks Michael for your reply.
I'm not using any plugin. This is my log on debug mode (sorry for the lenght, I've tried to trim the most important parts):
As you an see at 06:25:41 "vehicle.charge.start" then at 06:26:14 "vehicle.charge.stop", then agait at 06:26:16 "vehicle.charge.start"
BTW, is it correct that the Poller Send/Receive run constantly?
Thank you for your suppot.
As you can see from the log…
…it's the vehicle module that actually misdetects the charge stop. Please contact the vehicle developer (Geir I assume).
Regards,
Michael
Thanks for your replay. May I kindly ask, where to contact? Do you mean in this Forum? Thanks for your support