<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Steve,<br>
<br>
the V3 metrics framework has staleness for every metric. You can
query the staleness by the command "metrics list -s". Values aren't
supposed to disappear/clear when becoming stale.<br>
<br>
The "live" indicator on the App is showing if the App has received
any update recently (i.e. within the last minute). It doesn't
indicate that update had new values, just that the connection to the
car is alive.<br>
<br>
Regarding value staleness, the V2 protocol (which the Apps still use
and probably will continue to use, as it's much more efficient than
MQTT) only has support for staleness info on a handful of values,
mostly the temperature readings. Those get grey when becoming stale.<br>
<br>
See <a class="moz-txt-link-freetext" href="https://docs.openvehicles.com/en/latest/protocol_v2/index.html">https://docs.openvehicles.com/en/latest/protocol_v2/index.html</a>
for the protocol details. You can add some more staleness info to
the V2 message protocol quite easily, and adding support for greying
out the values in the App also isn't hard. Add new data to messages
at the end for compatibility. Think about which staleness actually
matters. Up to now, the staleness indication for temperatures has
been sufficient, as these also indicate general staleness. If you
plan to add data to the V2 protocol, it's probably best to discuss
that first here.<br>
<br>
The web UI currently doesn't care about staleness. If you miss that
info, it isn't hard to add as well, just a bit of work to connect
the dots.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 26.12.20 um 16:00 schrieb Steve
Davies:<br>
</div>
<blockquote type="cite"
cite="mid:CABFTEGXoV8sbYvEFJfFKO89bzS7dDg4A7smpq+Bb1O2uthWnCQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, 26 Dec 2020 at
16:35, Steve Davies <<a href="mailto:steve@telviva.co.za"
moz-do-not-send="true">steve@telviva.co.za</a>> wrote:<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>My car's OBD currently goes off after a while
whenever it's not READY (to drive) (whether charging or
not),<br>
</div>
<div>
<div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Trying not to spam with questions - but ...</div>
<div><br>
</div>
<div>If the car is off and not responding on OBD then
obviously information going through to the apps becomes
stale.</div>
<div><br>
</div>
<div>But the apps still show "Live" in the corner and it's not
obvious that the info is out of date.</div>
<div><br>
</div>
<div>Is there a way to show how many minutes old the data is
or something like that?</div>
<div><br>
</div>
<div>Does this interact with the autostale stuff in some way?
I'm not really understand the effect of this - I changed the
metrics for 12v current to SM_STALE_MID and it must be stale
by now but the misleading 8.9A figure is still showing in
the OVMS web "status" page. Also in "metrics list". Is it
supposed to disappear when it goes stale.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Steve</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>