Solar Gate integration guide

Connect an existing energy system without sending a Solar Gate team to site.

The customer, vendor or chosen local technician provides lawful access to the existing data source. Solar Gate supplies the connection contract, normalization, secure ingestion, APIs, monitoring and commercial workflows online.

Create Sandbox key Connector catalogue Pricing

Physical wiring, network access, meter ownership and local electrical compliance remain the customer's or local contractor's responsibility. Solar Gate does not ask customers to expose field devices directly to the public internet.

End-to-end journey

Eight steps from use case to live API access.

Choose the result

Decide whether you need raw telemetry, latest values, alarms, portfolio health, billing evidence, invoices or a future forecast/tariff product.

Create a developer client

Sign in, create a Sandbox client and generate an API key. The key is displayed once; store it in a server-side secret manager.

Select the data source

Use an existing vendor cloud, Home Assistant, a customer-managed HTTPS gateway, or a local Modbus/SunSpec/BACnet connector.

Create the connection

Register the connector type and obtain a separate connection key and ingest token. Developer API keys and ingestion tokens are never interchangeable.

Register devices and points

Create the inverter, meter, battery, BMS controller or other device, then map its measurements to Solar Gate metric codes and engineering units.

Send and validate data

Send UTC timestamped batches with stable device/point identifiers and idempotency keys. Review accepted, duplicated and rejected sample counts.

Grant API access

Grant the developer client access only to the required projects and scopes, then read normalized data through the Core, Telemetry, Operations or Commercial APIs.

Move to live use

Choose a paid module or bundle, complete payment/contract entitlement and run the production acceptance checklist before live credentials are enabled.

Connection requirements

What the customer needs for each integration route.

Generic HTTPS gateway

Foundation-ready, read-only

✓ A device, server, gateway, Raspberry Pi or existing application that can make outbound HTTPS requests on port 443.
✓ Solar Gate connection ID and ingest token stored outside source code.
✓ Stable external device and point identifiers.
✓ UTC ISO-8601 timestamps, explicit engineering units and numeric/text/boolean value type.
✓ A unique batch idempotency key for each logical upload.
✓ Payloads matching the Solar Gate connector schema and size/sample limits.

Responsibility: The customer controls the gateway and sends normalized or mappable data. No inbound firewall port is normally required.

Home Assistant

First working edge adapter, read-only

✓ An always-on Home Assistant instance accessible to the local adapter.
✓ A Home Assistant long-lived access token kept only on the customer-managed host.
✓ A mapping file listing only the entity IDs approved for Solar Gate.
✓ Correct units and entity meanings for solar, load, battery, meters and alarms.
✓ Outbound HTTPS 443 from the adapter host to Solar Gate.

Responsibility: The adapter polls selected entities locally and sends mapped data. Solar Gate does not need direct access to the whole home or building network.

Modbus TCP/RTU or SunSpec

Architecture ready; production adapter and device maps require validation

✓ A local gateway computer with network or serial access to the equipment.
✓ Official register map or SunSpec model support for the exact inverter, battery, meter, PLC or controller model.
✓ Device address, unit ID, baud/parity settings where serial is used, register type, scale factor and engineering unit.
✓ Read permission from the asset owner and safe isolation from control registers.
✓ Outbound HTTPS 443 from the gateway; inbound internet access should not be opened to the field device.

Responsibility: The customer or local technician supplies the official register map and provides local network access. Solar Gate validates the mapping remotely before data is accepted for billing.

BACnet/IP BMS

Planned local gateway connector

✓ BACnet/IP access from an approved local gateway within the building network.
✓ Device instance numbers, object list, point names, object types, units and expected update intervals.
✓ BMS owner/integrator authorization and network segmentation requirements.
✓ A defined read-only point scope for HVAC, meters, pumps, generators, water and environmental sensors.
✓ Outbound secure transport from the local gateway to Solar Gate.

Responsibility: The building owner or BMS integrator grants local read access. Solar Gate does not require a routine physical visit and does not bypass the BMS vendor's safety controls.

Vendor cloud API

Per-vendor: public API, partner agreement or commercial hold

✓ A supported manufacturer and an approved API or partner-access method.
✓ Asset-owner consent through OAuth, delegated access or a documented service credential.
✓ Plant/site ID, device IDs and the permissions needed for read-only monitoring.
✓ Compliance with the vendor's rate limits, data-use terms and commercial restrictions.
✓ A fallback plan if the vendor changes or withdraws the API.

Responsibility: The customer connects the vendor account or supplies approved credentials through a secure flow. Passwords and API secrets must never be emailed to Solar Gate.

Utility bills and interval data

Planned; coverage depends on country and provider

✓ Authorization from the utility account holder.
✓ PDF/CSV statements, a supported provider authorization, or customer-owned utility API credentials.
✓ Account timezone, billing currency, meter identifier, billing period and tariff name where known.
✓ Consent for retention and processing of account and consumption data.
✓ Manual verification where utility formats or estimates make automatic extraction uncertain.

Responsibility: Coverage and collection cost differ by utility. Solar Gate will show whether the source is customer-uploaded, BYOK, partner-collected or unavailable before charging.

Billing and settlement evidence

Commercial engine implemented; connector evidence requires acceptance

✓ A cumulative energy register where settlement depends on kWh—not only instantaneous power.
✓ A documented measurement boundary explaining what the meter includes and excludes.
✓ Timezone, currency, billing cycle, contract model and approved rate structure.
✓ Provider/customer approval roles and evidence-quality rules.
✓ A process for meter resets, replacement, estimated data, gaps and disputes.

Responsibility: Solar Gate can calculate PPA, shared-savings, lease, O&M, EPC and monitoring invoices only after the evidence source and commercial terms are approved.

Controlled commands

Restricted—not available in the first release

✓ Separate safety review, customer consent, vendor permission and contractual responsibility.
✓ Named approvers, MFA, command expiry, limits, acknowledgements and immutable audit history.
✓ Defined rollback and local manual override.
✓ Device-specific testing that proves a failed command cannot create an unsafe condition.

Responsibility: Do not design a production dependency on Solar Gate commands yet. The current release is deliberately read-only.

Normalization examples

Different vendors, one metric vocabulary.

The source name can differ, but the mapped meaning, unit and reading type must be explicit. A cumulative meter register must never be confused with instantaneous power.

Meaning	Metric code	Unit	Reading type
Solar production energy	`energy.production.total_kwh`	kWh	cumulative
Grid import energy	`energy.import.total_kwh`	kWh	cumulative
Grid export energy	`energy.export.total_kwh`	kWh	cumulative
Active power	`power.active.kw`	kW	instantaneous
Battery state of charge	`battery.soc.percent`	%	instantaneous
Temperature	`environment.temperature.c`	°C	instantaneous
Equipment running	`equipment.running`	boolean	state

Reading the API

Use the developer key only from a trusted server.

curl \
  -H "Authorization: Bearer sg_test_REPLACE_WITH_YOUR_KEY" \
  -H "X-Request-ID: 8d3f4a0e-unique-request-id" \
  https://<project-ref>.supabase.co/functions/v1/energy-developer-api/v1/sites

Never put a production developer key in browser JavaScript, a mobile application, a public repository or an email.

Sending telemetry

Ingestion uses separate credentials.

{
  "batch_id": "stable-unique-batch-id",
  "recorded_at": "2026-07-31T20:00:00Z",
  "samples": [
    {
      "device_external_id": "meter-01",
      "point_external_id": "import-kwh",
      "value": 12540.8,
      "quality": "valid"
    }
  ]
}

The connection ID and ingest token authenticate the data source. They do not grant access to read customer projects through the developer API.

Production acceptance

Do not use a new connector for billing until these tests pass.

✓ Connection authenticates with the correct token and a revoked token fails immediately.

✓ Device and point identifiers remain stable between uploads.

✓ Units, scale factors, sign conventions and cumulative/instantaneous meaning are documented.

✓ Duplicate batch and duplicate sample tests do not create duplicate commercial evidence.

✓ Timestamps, timezone conversion and late-arriving data behave as expected.

✓ Data gaps, estimated values, meter resets and equipment replacement are tested.

✓ A second customer cannot read or write the first customer's projects.

✓ API quota, history-window and entitlement denials return controlled errors.

✓ The customer confirms which points may be used for monitoring only and which are approved for billing.

Security rules

✓ Keep vendor, Home Assistant, ingest and developer credentials separate.
✓ Use least-privilege scopes and explicit project grants.
✓ Rotate credentials after exposure, personnel changes or vendor-account changes.
✓ Prefer outbound connections; do not port-forward meters, inverters, PLCs or BMS controllers.
✓ Remove secrets from logs, screenshots, tickets and shared documents.

What affects total price

✓ Number of connected projects and retained history.
✓ Sample frequency and whether Solar Gate operates the connector.
✓ Vendor API, utility authorization or licensed-data charges.
✓ Custom mapping, migration, dedicated hosting or SLA requirements.
✓ API modules and request volume used by the customer's application.

View transparent pricing

Solar Gate

Loading your workspace

Please wait while we prepare the latest project information.