Website: https://explore.garmin.com
This integration requires configurations in the Garmin Portal, Gundi, and EarthRanger. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.
We are actively working to make this integration self-service in the future. Stay tuned for updates!
Prerequisites
Data Fetch
You will need:
- Garmin Explore (Garmin Explore™ ) account.
- Garmin Professional Subscription.
Data Delivery
You will need:
- Admin access to EarthRanger.
- A special EarthRanger user with permissions to post observation data and messages.
- A long-lived token for the special user.
Please refer to EarthRanger's documentation or contact Support.
Configurations
This integration requires two Connections in Gundi to configure a bi-directional integration for messaging.
Important:
To avoid duplicating subjects in EarthRanger, if the EarthRanger - Garmin InReach integration has already been active through a previous version of Gundi, please contact the dev team before proceeding with this guide.
1. InReach to EarthRanger
Click to expand..
1.1 Gundi
Log in to Gundi.
Click Create Connection.
Select Garmin InReach.
Select your Organization.
Enter a Connection Name (e.g., InReach to ER).
Leave all other fields empty.
Click Next.
Select a Destination. Please consult our guides.
Go to the Connection's “Overview” tab.
Copy the API Key.
1.2 Garmin
Log in to https://explore.garmin.com/
Go to Settings
Go to Portal Connect
Turn Outbound Settings ON
Set the Outbound Settings URL:
https://hooks.gundiservice.org/webhooks?integration_type=inreach&apikey=[apikey]
Important: Replace apikey with the API Key you copied from the Gundi Connection Overview tab.
Click Test
Click Save
You should see a subject with an observation and a message on the EarthRanger site.
2. EarthRanger to InReach
Click to expand..
2.1 Configure Garmin
Log in to https://explore.garmin.com/
Go to Settings
Go to Portal Connect
Turn Inbound Settings ON
Configure an IPC User Name and IPC Password. These fields can't be left blank.
Take note of the Inbound URL (Garmin). Example:
2.2 Configure Gundi
Log in to Gundi.
2.2.1 Create a Connection
Click Create Connection.
Select "API Push".
Select your Organization.
Enter a Connection Name (e.g., ER to Garmin InReach).
Leave all other fields empty.
Click Next.
2.2.2 Create a Destination
Select “+ New Destination”.
Select Garmin InReach.
Name: Enter a Destination name (e.g., InReach AccountName).
Organization: Enter the Organization who owns the radios.
Configure the following parameters so they match the IPC Inbound settings configured in https://explore.garmin.com/
URL: Inbound URL (Garmin)
inReach Portal Connect (IPC) Inbound API: Inbound URL (Garmin)
https://Example:
Replace “eur-enterprise.inreach.garmin.com”
with “https://eur-enterprise.inreach.garmin.com”
Username: IPC User Name
Password: IPC Password
Save the destination.
2.2.3 Add the new destination to the Connection
2.2.4 Copy the API Key
Go to the Connection's “Overview” tab.
Copy the API Key you will use it in a later step.
2.3 Configure EarthRanger
Log in to the admin site.
Go to “Source Providers”
Search for the source provider created for this integration (i.e., gundi_inreach_integrationid)
Enable Two-way messaging:
- Choose adapter type “smart-integrate-adapter”
- Entre URL: https://sensors.api.gundiservice.org/v2/messages/
- Enter the <API Key> noted from the portal
Click Save
Data Delivery
The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 10 minutes).
If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.
Troubleshooting
Contact the Gundi team to confirm that the integration requirements (e.g., Garmin Professional Subscription) are met. Also, provide the list of device IMEIs.
Log Explorer Query
Tags: Radios, Messaging, Pull Integration, Data Provider, Data Destination
Last Update: Aug 28, 2024