Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

Questions about spot API

  1. I think that "spot set <id> lifetime_seconds=<n>" sets the spot's expiration to n seconds after the "set" command is run, and not n seconds after the original "spot add" was run. This makes sense. Can I have confirmation please?
  2. It seems like there is some deduplication of spots internally — a "spot add" with the same rx_freq and callsign as an existing one will return the ID of the existing one instead of adding a new one. Could we know the exact rules that apply so that they can be documented in the wiki?

Thanks!

Tagged:

Best Answer

  • Administrator, FlexRadio Employee admin
    Answer ✓
    1. Confirmed. The lifetime_seconds just sets a field and a timestamp is created and compared to the original spot timestamp to know when to eliminate that spot.
    2. The frequency/Callsign combo is considered unique. This note is in the source:
    // Check to see if this Callsign-RXFreq combination is already in the DB
    // If so - treat as a duplicate and simply update the fields in the spot
    

    Both of these clarifications should go into the wiki description, and I'll do what I can to get them updated. Thanks for pointing this out.

Leave a Comment