Supported technology/IoT Systems and Device Management
| Direction | Data provider |
| Data | Sensor readings (stationary subjects) |
| Platform | Gundi v2 |
| Type | Pull integration |
Victron Energy sends the latest battery, solar charger and inverter readings from your VRM installations to EarthRanger through Gundi. Gundi checks your VRM account on a schedule, and each installation shows up as a stationary subject with its readings.
What you'll receive
We add details here as we confirm what Victron Energy sends. If you know something we're missing, let us know.
| Positions | Yes, one stationary subject per VRM installation, named after the VRM site name. VRM doesn't share coordinates, so each installation is placed where you set it in Location overrides, or at latitude 0, longitude 0 without one. Excluded installations and ones silent longer than the Maximum data age are skipped. |
| Alerts and events | No |
| Sensor readings | The readings you tick in Sensors of interest, named as VRM names them: battery voltage, current, temperature, state of charge, consumed amphours, time to go, cell voltages and temperatures, solar power, PV voltage, yield, charge state, error code, battery state and power, DC system and AC consumption. |
| Photos and files | No |
| Past data | No. Each check sends only the latest readings for each installation. Readings more than an hour older than the installation's newest one are left out. |
How this integration works
This is a pull integration. Gundi checks the data provider for new data on a schedule, using the account details you enter in the Route, and passes what it finds on to your destination.
Who's involved
- You create the Route in Gundi and enter your provider account details, or give them to Gundi support when the setup badge says so.
- The data provider keeps your account and devices active.
- 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
When you first connect, Gundi fetches a limited amount of past data. How far back it goes depends on the integration and is shown under "Past data" above.
When data doesn't show up
Check your Route Activity Logs first: wrong account details and provider outages show up there. Then check with the provider that your devices are reporting.
How often data arrives
Gundi checks on a schedule. Where we know how often, it's shown under "Data Pull Frequency" on this page. New data arrives after the next check, plus the time the device takes to upload it to the provider.
Prerequisites
Victron VRM
You will need:
- A VRM account that can see the installations you want in EarthRanger.
- A VRM access token for that account. Create it in VRM under Preferences → Integrations → Access tokens. Gundi connects with the token, not with a username and password.
EarthRanger
To send sensor 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
GUIDES
1. Gundi Connection Settings
1.1 Login to Gundi.
1.2 Click on Create Route.
1.3 Select Victron Energy.
1.4 Select your Workspace.
1.5 Enter a name for this Route (e.g., “Victron Energy - AccountName”)
1.6 Paste your VRM access token, then click Test Connection. Gundi lists every installation the token can see, with its ID and name.
1.7 Optionally, adjust the settings below. Every installation the token can see is synced automatically, so no per-site setup is needed.
- Subject subtype: the subtype for the subjects (default “static-sensor”).
- Sensors of interest: the readings to bring in. A default set is ticked.
-
Additional sensor codes: extra VRM codes, case-sensitive (e.g.,
PVV,gs,mcT). Most setups leave this empty. - Maximum data age (hours): default 24, from 1 to 720. Installations that haven't reported for longer than this are skipped until they report again.
- Location overrides: an installation ID with a latitude, a longitude and, optionally, a subject name.
- Excluded installations: installation IDs you don't want to sync.
1.8 Click Next.
1.9 Click Add destination on the flow map and select a destination. Please consult our guide.
2. What you'll see in EarthRanger
- One stationary subject per VRM installation, named after the VRM site name (or the name in its location override). The integration runs every 10 minutes.
- VRM doesn't share installation coordinates, so installations without a location override are placed at latitude 0, longitude 0. You can move them in EarthRanger, or add a location override in Gundi.
- Measured readings arrive as numbers without units (e.g., Voltage 25.27). Status readings arrive as text (e.g., Charge state “Off”, Error code “No error”, Battery state “discharging”).
- The Route's Activity Logs note when an installation hasn't reported for longer than the maximum data age, and when a location override doesn't match any installation the token can see.
3. EarthRanger Settings
The following configurations are optional:
3.1. Select the data you want to see in the map, with its label and units.
3.1.1 Log in to EarthRanger as an admin (site.pamdas.org/admin).
3.1.2 Go to
Source Providers.
3.1.3 Select the
Source Provider created for this integration.
3.1.4 Click on Subject Details Configuration.
3.1.5 Choose the readings
you want to see and set their label and units. You can copy the units from this table:
| Reading | Units |
|---|---|
| Voltage, PV voltage | V |
| Current | A |
| Consumed Amphours | Ah |
| State of charge, Battery SOC | % |
| Time to go | h |
| PV power, Battery Power, PV - DC-coupled, DC System | W |
| Yield today, Yield yesterday | kWh |
| Charge state, Error code, Battery state | Text, no units |
3.2 Assign your Subjects to a Subject Group.
Please refer to EarthRanger's documentation or contact Support.
Other IoT Systems and Device Management
| Kerlink | LoRaWAN and other LoRa protocols | Sigfox |
| Smart Parks | The Things Network |
| Back to the integration catalog | Need help setting this up? Contact us |
