Ecotopia

Website: https://druid.tech/ecotopia/ 

Prerequisites

Ecotopia

You will need:

  • Ecotopia account (username and password)

Gundi

You will need:

  • Credentials or an authentication token to access the delivery system.

EarthRanger

To send movement 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 Support.
  • A long-lived token for authentication assigned to the user created in the previous step. Please refer to EarthRanger's documentation or contact Support.

Configuration

Integration Requires Assistance

Self-Service integration not available yet, please contact our Support Team.

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

Go to Gundi v1

Go to the Inbound Integrations and select Add Integration

Follow these steps to configure the integration.

Name: Enter a suitable name (e.g., "Sitename - Druid Tech")

Owner:  Select the integration's owner

Type: DruidTech / Ecotopia

Provider Key:  Leave empty. It will automatically give it a name.

Default Device Group: Leave empty. Gundi will automatically create a default group.

Endpoint:  https://www.ecotopiago.com

Token:  Leave empty

Login/Password:  Username and password provided by the user

State:   

{}

Click Save

Configure the Default Device Group to select the destination site. 

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

Q1: Why is battery level showing as 0 or not appearing for some Druid tags?   

Battery level comes from the status_env.battery_power field in the Druid API. Some older firmware devices (firmware < 1003) don't report this value, so it will show as blank. Devices on newer firmware should report a percentage (0–100). If all devices show 0, it may indicate the integration was running an older version of the connector — deploying the latest version should resolve it.  
 

Q2: Why are some tags showing temperature data but not battery data (or vice versa)?

Temperature and battery level come from different sub-fields on the device. Temperature is more broadly supported across firmware versions. Battery percentage requires status_env.battery_power to be populated by the tag's firmware — not all hardware versions support it.
 

Q3: What does "Survivor Mode" mean for a Druid tag?  

Survivor mode (survivor_number = 1) means the tag has entered a low-power emergency state, typically due to low battery or lack of recent GPS fixes. The tag reduces transmission frequency to extend battery life. The survivor_time field shows when survivor mode was activated. Rangers should prioritize checking on animals whose tags are in survivor mode.  
 

Q4: Why are some tags showing 403 Forbidden errors and no location data?

A 403 means the API account associated with this integration doesn't have permission to access that specific device's GPS data. This typically happens when a Druid account manages multiple device groups and some devices belong to a different access tier. The connector will skip those devices and continue processing the rest — no action needed unless the missing devices are expected to report.   
 

Q5: Why does a tag show a valid location in the Druid portal but no recent positions in EarthRanger

This can happen when the GPS record has coordinates outside valid bounds (longitude outside ±180 or latitude outside ±90) — the connector filters those out. It can also happen if the tag's last position predates the integration's state window. Check the Druid portal export for that device and compare timestamps with what's visible in EarthRanger.

 

 

 

 

Animal Tracking, Movement Data, Gundi v1, Pull Integration, Data Provider
April 14, 2026