No announcement yet.

API to control device

  • Time
  • Show
Clear All
new posts

  • API to control device


    Two Questions:

    1. I would like to confirm that Garmin is going to continue proving the RAW api data feed going forward eg: (

    2. Could we have an api to change the the devices tracking sending interval?


    We have several years invested in creating a yacht racing tracking application ( that uses the inReach device. This application and portal is made available free of charge as part of giving back to the community. If Garmin have any changes to the feed api than we need to make alternatives plans.

    Having an api to control the devices tracking interval would enhance safety and battery life. During the start/finish of a race we would like to have the update rate set to every 10 minutes and then for longer races drop it back to every 4 hours. In areas of forecast bad weather or heightened risk we would like to have the device update at a higher rate. If a boat gets into trouble then it would be nice to have an api to request the current position and devices sleep interval.


  • #2
    It sounds to me like like what you are trying to do is built into the inReach software now. InReach software can be set to different tracking intervals between 4 hours to 1 second.
    I use the Android Earthmate app on a Nexus 6P with my inReach. I also use Windows 10.


    • #3
      You probably won't get a definitive answer to either question from anybody here on the forums.Most of us don't work for Garmin.

      Are you using enterprise or individual plans? The shortest interval for track points sent via the satellite network is 2 minutes for individual plans. I believe enterprise plans allow shorter intervals, perhaps down to 30 seconds, but do not know for sure. That would be the best you could do.

      It's clear that there is a mechanism for requesting the device's current position. You can do this from the web site through a locate request. Not aware of any API that exposes the functionality, though.

      Not sure what you mean by the device's sleep interval. When tracking is enabled, points will be sent at the specified intervals as long as the device perceives itself as moving. If it perceives itself as stopped, it will automatically revert to the 4 hour interval. Moving vs. stopped is based on the distance moved between position checks. That is, if the distance moved is below some fixed threshold, the device perceives itself as stopped. I don't know what the position check interval is when the device believes it is currently stopped. It's a trade-off between responsiveness and battery life. But anecdotally, it seems to be short enough to be effective.

      Looking at some available information on the enterprise plans, it appears that it might be possible to alter the send interval remotely. But it's a really vague reference.
      -- Tom
      inReach SE, inReach Explorer, PN-60WSE, Colorado 400t, Nuvi 2555LMT


      • #4
        Appreciate the feedback, I was wanting to put it in the public arena in the hope that the Garmin commercial arm may be listening and consider this use case as a good enhancement.

        We can have anywhere from 30 to 300 yachts in an ocean race. Some devices will be on the same garmin inreach account other may be privately owned. This makes controlling the devices through all those accounts an impossible job.

        In the perfect world, each device owner could select/activate remote management from the inreach portal and give us the "key". In much the same way you activate MapShare. Now we could send to the device through an API call, commands to:

        1. Start tracking
        2. Stop tracking
        3. Change tracking interval
        4. Ping current location
        5. Send it a text message
        6. Validate the key (use to confirm device details on setup and remote management is active)

        This would give the race organiser a simple interface as the portal would manage everything.

        Once the race is over the device owner could deactivate remote management. Keeping the owner in control. This would also keep it simple for everyone and reduce the support in getting the devices operational in a race.