Maintained by EpiSensor

Enel X integration with EpiSensor Edge

EpiSensor maintains an Edge integration for Enel X flexibility programmes. It sends selected site measurements over certificate-authenticated MQTTS and can receive project-approved device commands.

See the complete route Plan the site system
Engineer commissioning demand-response equipment in the Enel X and Microsoft data-centre project
A packaged Edge flow with current operator documentation, project configuration and certificate workflows.

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. Site assets

    Meters, controls and project-approved Modbus points

  2. EpiSensor Edge

    Local validation, mapping, automation and export selection

  3. Secure MQTTS

    Assigned broker identity and client certificate

  4. Enel X

    Telemetry, registration and approved flexibility commands

What this route does

  • Packages the Enel X project settings and connection workflow on the Gateway.
  • Publishes selected, export-enabled measurements to the assigned platform environment.
  • Supports project-approved command handling while keeping physical output verification separate from message delivery.

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

    Obtain the assigned Enel X project, environment, Gateway identity and certificate provisioning method.

  • 2

    Choose one locally verified measurement with a known value, unit and timestamp.

  • 3

    Arrange a safe output test, recovery route and receiving-platform contact before testing control.

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. Apply the exact assigned project and read the effective broker, Gateway identity and environment back from Edge.
  2. Install the approved certificate material and verify identity, expiry, Gateway time, DNS and outbound connectivity.
  3. Confirm the MQTTS session, then ask Enel X to verify the intended Gateway in the intended environment.
  4. Send one known measurement and compare device, value, unit and timestamp at both ends.
  5. Qualify each writable point separately with a safe state, physical feedback and an agreed recovery procedure.

What not to infer

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

  • An online broker session does not prove that Enel X accepted or interpreted a measurement.
  • A platform command or reported shadow state does not prove the physical equipment reached the requested state.
  • Available devices, writable points and command semantics are project-specific; they are not generic Modbus capabilities.

Evidence and further reading

  1. Edge platform integrationsEpiSensor
  2. Enel X and Microsoft data-centre projectEpiSensor
  3. Enel X at Dublin AirportEpiSensor
  4. What is demand response?Enel X

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.