Supported technology/IoT Systems and Device Management
Victron Energy users can bring the readings from their VRM installations (batteries, solar chargers and inverters) into EarthRanger, where each installation appears as a stationary subject.
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.
Note on Latency
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 5 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.
Other IoT Systems and Device Management
