<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 14 Jan 2021 at 09:23, Michael Balzer <<a href="mailto:dexter@expeedo.de">dexter@expeedo.de</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>Both are historical records, i.e. kept on the server until deletion
or expiry. If you're looking for a GPS log, we've already got that
in form of the "L" messages. These are kept for 24 hours, and the
log frequency adapts to user choice and App connection state
("streaming mode", feature #8 / config vehicle stream).<br></div></blockquote><div><br></div><div>Thanks! </div><div><br></div><div>Is there documentation that I failed to find? IE "feature #8" - seems like from a list somewhere?</div><div><br></div><div>I'm working at the moment with the MQTT server.</div><div><br></div><div>In the mqtt server code I found "m_streaming" and it looks like I need "config set vehicle stream 1"</div><div><br></div><div>If I understand correctly this will result in metrics being published to mqtt as soon as they change.</div><div><br></div><div>Looking at the code I'm also trying to understand what exactly a "client" is. Here's how it looks to me: a client sends a message with topic <prefix>/client/<clientid>/active with the payload being non-0 to "connect" and 0 or empty to disconnect. Must send that at least once every 120 seconds to stay connected.</div><div><br></div><div>With a client "connected" the MQTT server will send metrics at the updatetime.connected rate rather than the idle rate (nowithstanding that with "stream 1" they are sent immediately).</div><div><br></div><div>Clients can also send commands too: <prefix>/client/<clientid>/command</div><div><br></div><div>Am I on the right track?</div><div><br></div><div>Thanks,</div><div>Steve</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div></div></div>