Integrations

Works with the fleet you already bought.

Victron in one state, Huawei in another, SparkMeter billing over both — Gen318 speaks to all of it through one adapter layer. Below: a real onboarding, timestamped.

onboarding · adamawa-07 · existing hardwareELAPSED 28 MIN
10:02:04$ gen318 connect victron --site adamawa-07
10:02:09vrm.victronenergy.com — authenticated (read + write scope)
10:03:31discovered: MultiPlus-II 48/5000 · 3× MPPT 250/100 · BMV-712
10:07:12registers mapped: 47 read · 12 write — control path verified
10:11:48edge node paired · buffer initialised · sync tier policy set
10:12:29first telemetry received (2G uplink, 41s round trip)
10:30:00CONNECTED — baseline learning begins · smarter in 72h
18+
Adapters live
6
Wire protocols
R+W
Control, not just reading
~30 min
To first telemetry
01 · The catalogue

Depth, not logos.

Anyone can list brands. What matters is the capability badge: MONITOR means we read it, CONTROL means the dispatch agent can act on it — volt, because the machine is acting. Victron ships with the full write path; more control surfaces follow it.

Adapter catalogue · universal hardware layerGENERIC MODBUS COVERS THE REST
Filter · category
  • ALL18
  • INVERTERS5
  • BMS2
  • METERS4
  • GENSETS1
  • SENSORS1
  • CAMERAS1
  • PROGRAMS1
  • CHANNELS2
  • DATA1
VIC
Victron
Inverters
CONTROL
VRM APIMQTTMODBUS-W

Full write path — dispatch control enabled

HUA
Huawei SUN2000
Inverters
MONITOR
FUSIONSOLAR API
GRO
Growatt
Inverters
MONITOR
SHINESERVER API
SMA
SMA
Inverters
MONITOR
SUNNY PORTAL API
SCH
Schneider Conext
Inverters
MONITOR
MODBUS
BYD
BYD Battery-Box
BMS
MONITOR
CAN BUS
PYL
Pylontech
BMS
MONITOR
RS485
SPK
SparkMeter
Meters
MONITOR
KOIOS API

Billing + consumption per connection

STE
SteamaCo SHYFT
Meters
MONITOR
FLEXVIEW API
OKR
Okra Pod
Meters
MONITOR
HARVEST API
GVE
GVE G-Vend
Meters
MONITOR
API
GEN
Diesel gensets
Gensets
CONTROL
MODBUSFUEL SENSORS

Auto start/stop inside guardrails

ENV
Env. sensors
Sensors
MONITOR
LORAWANCELLULAR
THR
Thermal / drone
Cameras
MONITOR
IMAGE UPLOAD
ODY
Odyssey
Programs
EXPORT
DARES EXPORT

Compliance-formatted, audit-trailed

NSA
NASA POWER
Data
MONITOR
WEATHER API
WHA
WhatsApp Business
Channels
CHANNEL
CLOUD API
SMS
SMS
Channels
CHANNEL
GSM
Through the adapter layer · today · 48 sitesLive
2.4M+180k
Telemetry points
1,204100% verified
Commands acked
96+12 this wk
Reports to Odyssey
3.1kdelivered
WhatsApp alerts
0all tiers drained
Sync backlog
Is your hardware supported?DEVICE REGISTRY
growattMATCHING DEVICES
Growatt SPH seriesSHINESERVER API · MONITOR200+ units in cohortSUPPORTED
Growatt MIN TL-XSHINESERVER API · MONITOR80+ units in cohortSUPPORTED
Growatt WIT (new)NOT YET LISTEDgeneric Modbus covers itREQUEST ADAPTER →

Named adapters are built against real fleets, not spec sheets — misses ship as generic Modbus first.

02 · Connection health

Connected isn't done. Audit-accepted is done.

Every adapter is scored continuously — heartbeats, register coverage, data completeness. The number matters because DARES audits it: gaps in your telemetry are gaps in your grant evidence.

Integration health · fleet
98.4%TARGET ZONE 95–100
FLEET AVG 96.8BEST NIGER-03 · 99.6

Data completeness is a DARES audit metric —
this gauge ships in your compliance report.

Score breakdown · by adapter30-DAY WINDOW
Victron · VRMVERIFIED99.2
Last heartbeat
12s ago
Register coverage
59/59 mapped
Last audit export
Q2 · accepted
SparkMeter · KoiosVERIFIED97.8
Okra · HarvestVERIFIED96.1
Huawei · FusionSolarWATCH · API LAG93.4
03 · Control abstraction

One command. Every dialect.

The dispatch agent doesn't know or care what brand of inverter runs your site. It issues one guardrailed command; the abstraction layer translates it into whatever the hardware actually speaks — verified, retried, acknowledged.

Control abstraction layer · one schema, every dialectWRITE PATH · GUARDRAILED
Unified command
dispatch.genset.stop(
  site: "adamawa-07",
  reason: SOLAR_SURPLUS,
  guardrails: verified ✓
)
MODBUS RTU
Victron · gensets
write 0x2103 ← 0x0000
verify · retry ×3 · ack
MQTT
Victron GX
W/…/Relay/0/State
{ "value": 0 } · QoS 1
VENDOR API
cloud-managed fleets
POST /control/genset
mode: STOP · idempotent
04 · The last mile

Integration means nothing if the link is 2G.

Most platforms integrate for broadband and degrade in the field. Gen318's sync engine is designed the other way round: alerts always get through first, history waits its turn, and a month of outage loses nothing.

  • Sensors uplink over LoRaWAN or cellular — whichever exists
  • Edge compresses and batches before anything leaves the site
  • Priority queue drains in order when signal returns
4-tier priority sync · bandwidth budget on 2GEDGE BUFFER: 30+ DAYS
T1
Alerts & safety
immediate · bytes, not payloads
T2
Control acks
seconds · command confirmations
T3
Telemetry
batched · compressed on the edge
T4
Bulk history
opportunistic · waits for good signal

When the network drops, nothing is lost — the queue drains in priority order when signal returns.

Thirty minutes to first telemetry. Bring your VRM login.

Free fleet assessment on the hardware you already own.

Connect a site