Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Saillogger Community

  1. Home
  2. General Discussion
  3. Wrong moorage label in realtime monitoring page

Wrong moorage label in realtime monitoring page

Scheduled Pinned Locked Moved General Discussion
4 Posts 2 Posters 476 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    andreshs1
    wrote on last edited by
    #1

    Hi Iiker

    I am having an issue with the Realtime monitoring page, it is showing the wrong moorage name for the boat location.
    While currently the boat is at the Aberdeen Typhoon Shelter, the realtime monitoring page reads a different location

    Regards
    Andres

    1 Reply Last reply
    1
  • adminA Offline
    adminA Offline
    admin
    wrote on last edited by
    #2

    Hi Andres,

    This seems to have resulted from your last log, which seems to be the one from Aberdeen Typhoon Shelter to ABC Middle Island. Looks like you have since moved from ABC Middle Island but it is not captured as a log. That is the reason of the discrepancy. There are two things here:

    1. Wondering why your last log is not captured, could it be deleted?
    2. Independent of above, there is a question whether monitoring should do live lookups based on latest location. This answer has some caveats but it is likely yes.

    I pushed a change to address (2) and this should give you the correct location on the monitoring page but the question around (1) is still warranted.

    Thanks,

    Ilker

    1 Reply Last reply
    0
  • A Offline
    A Offline
    andreshs1
    wrote on last edited by
    #3

    Thanks Iiker

    I think that this was the time that the Pi was on failed state for a few days and I did not realize

    Yes, I think that a lookup based on current location would be ideal, I will sail to Macau over the weekend, and although still part of China, I will not have data roaming on the boat, thus, for the next 4 days there will not be updates sent to the server. So unless it caches up to 5 days worth of updates, all those will be missing, thus not showing the correct anchorage

    Thanks for the fix!

    Cheers
    Andres

    1 Reply Last reply
    0
  • adminA Offline
    adminA Offline
    admin
    wrote on last edited by
    #4

    Ok, that explains.

    On caching, it should not be a problem, it can cache data for more than a year as long as there is enough space on the Pi. And the space it uses for every record is trivial, so this should practically be a non-issue.

    1 Reply Last reply
    0

Powered by NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular