Mestro
Mestro is a Swedish energy-data platform that consolidates meter readings from utilities and submeters. When meters are read through Mestro rather than the Building Management System (BMS), myCoreAI ingests energy data directly from Mestro instead of relying on manual uploads.
When to use this integration
The Mestro integration fits when:
Meters are read by an energy company or aggregator that delivers data into Mestro, not wired into the BMS.
An active Mestro account already covers the buildings in scope for optimization.
Hourly readings are required and the BMS does not see the meters.
If meters are already on the BMS, that route is simpler and avoids a separate data contract. See Energy data — Overview.
Data resolution
Mestro typically delivers:
Hourly values when the underlying meter supports it. Hourly is the resolution myCoreAI needs for both optimization and reporting.
Daily or monthly values otherwise — usable for reporting but constrains what myCoreAI can do on the optimization side.
See the overview page for what each resolution unlocks.
Requirements
An active Mestro account covering the buildings in scope.
Read permission for Myrspoven against the Mestro tenant (typically granted in the Mestro portal or via an API credential).
A confirmed mapping of Mestro meter IDs to buildings and signals in myCoreAI.
Myrspoven handles the access and meter-mapping steps during onboarding.
Cost
Mestro charges for data access on their side; the cost depends on the customer's contract with them. Myrspoven does not charge separately for the integration.
Troubleshooting
Missing values, delayed data, or wrong units almost always originate on the data-feed side rather than inside myCoreAI. Contact Myrspoven to check what is arriving from Mestro and resolve mapping or gap issues. Manual upload is available as a fallback for affected periods.
Last updated
Was this helpful?

