Craig, did any of the metrics dumps show anything unusual? Did the staleness reflect the stopped updates? Did you see any inf/NaN in the dumps? I've had a similar effect lately where I had a bug in the e-Up code that could set a float metric to inf. That did not affect the V2 App though, only the web UI, as the JSON encoder does not handle NaN or inf. I thought if we should test for special float values in the JSON encoder, but then decided it's rather a bug to set a metric value to NaN or inf first place. The metric that was affected by my bug was no V2 transport metric, so if the Apps have an issue with special floats as well, that could have been your issue. You would have seen "inf" or "NaN" in the metrics dump then. Regards, Michael Am 20.11.21 um 02:44 schrieb Craig Leres:
A few days after filling up I noticed that the ovms app was reporting 53% SOC when I knew it should read much higher. I just reset persistent metrics ("metrics persist -r") and ran the engine for a bit and now it shows 92%.
My other car was showing 91% but after cycling power to the ovms module it (the other way to reset persistent metrics) it dropped to 89%.
Is it possible persistent metrics gets corrupted such that they can no longer be updated? I'm thinking if I see this again I'll write something to dump out the related data structures.
Craig _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26