[Ovmsdev] Happy discovered: I3 seems to manage 12v battery charge by itself
steve at telviva.co.za
Sat Jan 16 22:19:27 HKT 2021
On Sat, 16 Jan 2021 at 15:52, Steve Davies <steve at telviva.co.za> wrote:
> I'm not clear why another "vehicle.charge.state" event was not sent with
> I did not implement GetNotifyChargeStateDelay in my vehicle module - so I
> wonder if it ended up suppressed.
> Alternatively - at 09:26:42 the module was sending all metrics to MQTT.
> This implies that it had lost and re-established MQTT session. I wonder if
> that interfered with the MetricChanged logic.
Oh - I misread the code the sending of the vehicle.charge.state event has
nothing to do with the GetNotifyChargeStateDelay stuff.
So I'm not clear why another vehicle.charge.state event was not sent then
the v.charge.state was set to idle. My best guess is the hypothesis that
the v3 reconnect logic was busy sending all metrics just after reconnecting
and so the "metricchanged" flag was lost and the vehicle.cpp MetricModified
method was never called for the v.c.state metric and thus the event send
was never triggered.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev