Supported technology/IoT Systems and Device Management
| Platform | Gundi v1 |
| Type | Push integration |
JVA fence sensors send alerts to EarthRanger through Gundi. Alerts arrive as EarthRanger reports.
What you'll receive
We add details here as we confirm what JVA sends. If you know something we're missing, let us know.
| Positions | Not documented yet |
| Alerts and events | Yes. Fence alerts, as the event type fence_voltage. See JVA Event Type. |
| Sensor readings | Not documented yet |
| Photos and files | Not documented yet |
| Past data | Not documented yet |
How this integration works
This is a push integration. The data provider sends data to Gundi whenever it has something new, on its own schedule. Gundi passes each piece on to your destination as soon as it arrives.
Who's involved
- You create the Route in Gundi and share its API key with the data provider.
- The data provider turns on sending to Gundi with that key.
- Your destination, for example EarthRanger, is where the data shows up.
- Gundi support helps only when the setup badge at the top of this page says so.
Historical data
Gundi passes on whatever the provider sends, old or new. Gundi can't ask the provider for past data, so if you need history, ask the provider whether they can send it again.
When data doesn't show up
Gundi doesn't check the provider for new data; it waits for the provider to send it. If nothing arrives, check with the provider first that they are sending, then look at your Route Activity Logs.
How often data arrives
That depends on how often the provider sends it. Some send each reading right away, others in batches every few minutes or hours.
Prerequisites
JVA
You will need:
- JVA account.
- Assistance from the JVA team.
EarthRanger
To send event data to EarthRanger, you will need:
-
A special EarthRanger user (e.g., “Gundi Service Account”) for this integration.
Please refer to EarthRanger's documentation or contact our Support team. -
A long-lived token for authentication assigned to the user created in the previous step.
Please refer to EarthRanger's documentation or contact our Support team. - Confirm that the required event type and schema are configured in EarthRanger.
Configuration
This integration requires assistance from our support team for setup and configuration. 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!
GUIDES
Gundi Connection Settings
1. Go to Gundi v1.
2. Create an Outbound Integration
- Use a token tied to the Gundi Service Account permission set.
3. Create an Inbound Integration
Go to the Inbound Integrations and select Add Integration.
Follow the steps below to configure the integration.
Name: Enter a suitable name (e.g., "Trackers - AreaName")
Owner: Select the integration's owner
Type: Select your technology
Provider Key: Leave empty. Gundi will automatically give it a name.
Default Device Group: Leave empty. Gundi will automatically create a default
group.
Endpoint: Leave empty
Token: Leave empty
Login/Password: Leave empty
Click Save
4. Configure the Default Device Group
Configure the Device Group with the Outbound Configuration created for this connection.
5. Share the API Key or Configure it in your data source system
Visit the Inbound Configuration you created during this process, and copy the Gundi API key.
Send the API key and your account identifier to your contact at the data source provider, asking them to set up an integration with Gundi (URL: https://cdip-api-prod01.pamdas.org/positions/). Alternatively, configure the API key directly in their system if you have access to those settings.
Suggested Contacts:
- Vernard Vertuin - VernardV@stafix.co.za
- Shaun Westerveld - swesterveld@pakton.com.au
2. EarthRanger Settings
The following configurations are optional:
2.1. Select the data you want to see in the map.
2.1.1 Log in to EarthRanger as an admin (site.pamdas.org/admin).
2.1.2 Go to
Source Providers.
2.1.3 Select the
Source Provider created for this integration (e.g., "jva")
2.1.4 Click on Subject Details Configuration.
2.1.5 Configure the
additional information you would like to see on the map.
2.2 Assign your Subjects to a Subject Group.
2.3 Rename your Subjects
Please refer to EarthRanger's documentation or contact Support.
Other IoT Systems and Device Management
| Liquid Intelligence Technologies | Sigfox | The Things Network |
| Connected Conservation Foundation | Kerlink |
| Back to the integration catalog | Need help setting this up? Contact us |
