You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
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.
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 utilizespeedOverGround
to prevent this. Or maybe not set state betweensailing
/moored
until we have 10 minutes of data.The text was updated successfully, but these errors were encountered: