State always starts as moored

[bergie]

If the system starts whilst we're moving, it still goes to moored for the first 10 minutes before enough movement has been detected. We could utilize speedOverGround to prevent this. Or maybe not set state between sailing/moored until we have 10 minutes of data.

[marcobergman]

Hi, could you have a look at this issue with a view to resolving it? I restart signalk regularly while en route, and this issue causes many false logbook entries. Thx!

[bergie]

Maybe the best option would be to persist the state on disk every time it changes, and read it on start-up.

[marcobergman]

Possible; the litmus test for me is in the logging of signalk-logbook, but I cannot judge how this option would affect other applications of this plugin's output, navigation.state.