Documented customer deployment

EnergyCAP integration with EpiSensor Edge

EpiSensor and EnergyCAP have been used together for portfolio energy monitoring, and EnergyCAP currently lists EpiSensor among its supported meter brands. Each new deployment still confirms the receiving service and data contract.

See the complete route Plan the site system
Royal Mail logistics facility from the EpiSensor and EnergyCAP portfolio energy-monitoring deployment
A published Royal Mail deployment and a previously documented HTTPS integration establish the route; current projects re-confirm endpoint and mapping details.

The complete route

Every boundary below has its own configuration and evidence. Treating “connected” as one state is how mapping and delivery errors become invisible.

  1. EpiSensor meters

    Electricity and other agreed site measurements

  2. EpiSensor Edge

    Stable export identifiers, units and reporting interval

  3. Secure HTTPS

    Project-approved endpoint and credentials

  4. EnergyCAP

    Mapped meters in Interval Data

What this route does

  • Connects each physical meter or channel to a stable reporting identifier.
  • Delivers mapped readings to the receiving service over HTTPS.
  • Supports portfolio analysis while Edge continues to provide local dashboards, history and automation.

Prepare both ends before sending data.

The platform administrator and the site engineer should agree the identity and data contract before credentials are installed.

  • 1

    Agree the exact platform account, receiving endpoint and permissions with the EnergyCAP administrator.

  • 2

    Define each meter name, identifier, unit, interval and cumulative-or-interval meaning.

  • 3

    Choose a small set of source readings that can be compared at both ends.

Commission the route in order.

Keep the first test deliberately small. One reading checked end to end is stronger evidence than a busy dashboard whose source is uncertain.

  1. Create or confirm the destination meter records and keep their identifiers stable.
  2. Map the intended Edge channels and verify that export is enabled only for the required readings.
  3. Send a controlled sample and compare identifier, value, unit and timestamp in EnergyCAP Interval Data.
  4. Check at least one normal reporting interval and one Gateway reconnect before scaling to more sites.
  5. Record any transformation, aggregation or counter-differencing responsibility explicitly.

What not to infer

These limits make the guide usable during design review and acceptance, not just persuasive before purchase.

  • The historical electricity configuration documented kWh readings; it must not be assumed to export every electrical quantity.
  • Legacy Gateway menu paths and endpoints are not copied unchanged into a new Edge deployment.
  • A transport success does not prove the receiving meter, unit or reporting interval is correct.

Evidence and further reading

  1. Royal Mail portfolio energy monitoringEpiSensor
  2. EnergyCAP Interval Data and supported metersEnergyCAP
  3. Energy management with EpiSensorEpiSensor

Reviewed September 19, 2026 · revision 1. Platform names and trademarks belong to their respective owners; a guide does not imply endorsement unless the linked evidence says so.