> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/integrations/overview/energy-data/mestro.md). # 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](/integrations/overview/energy-data.md). ## 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](/integrations/overview.md) 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](/integrations/overview/energy-data/manual-upload.md) is available as a fallback for affected periods. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.myrspoven.com/integrations/overview/energy-data/mestro.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.