> 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.md).

# Energy data

## Overview

There are several ways to get energy data flowing into Myrspoven, depending on how your meters are connected and how granular your data is. This page covers what's supported, what to expect at each resolution, and why higher-resolution data unlocks better results.

### Integration options

#### BMS (Building Management System)

The simplest and most efficient method. If your energy meters are already connected to a BMS, Myrspoven retrieves signals directly from it — no extra integration work needed. If your meters are not yet on the BMS but could be, we strongly recommend connecting them there.

#### Third-party energy providers

For energy data that comes from an energy company rather than a BMS, Myrspoven currently integrates with **Mestro** and **Metry** in Sweden. These services typically deliver hourly data when available, and daily or monthly data otherwise.

Third-party providers usually charge for data access — the cost depends on your contract with them.

#### Manual upload

If you can't share data automatically — or if you use a third-party provider that Myrspoven doesn't yet support — you can upload energy data manually. Most resolutions are supported, but data within each upload must use a consistent resolution.

### Granularity levels

Myrspoven supports a range of data resolutions, because not every site can provide real-time data. We always recommend the highest resolution you can offer — higher granularity unlocks better analysis, more accurate reporting, and stronger optimization.

| Resolution    | Best for                                      | Notes                                          |
| ------------- | --------------------------------------------- | ---------------------------------------------- |
| **Real-time** | Control, reporting, analysis, troubleshooting | Instantaneous or accumulated consumption       |
| **Hourly**    | Reporting, analysis, troubleshooting          | Accumulated or hourly consumption per hour     |
| **Daily**     | Daily reporting comparisons                   | Limited for building-level impact analysis     |
| **Monthly**   | Reporting only                                | One value per month — analysis is very limited |

### Why low-resolution data limits what Myrspoven can do

Daily and monthly data still work, but the trade-offs are real. Higher resolution makes a measurable difference in three areas.

**Energy control.** Without detailed data, advanced machine learning can't be used to optimize energy use; Myrspoven falls back on simpler heuristic methods. These work, but they require deep expertise to tune and don't adapt as well to new systems or unexpected conditions.

**Reporting.** Reporting on dynamic features like load shifting becomes harder. Reports end up based on simplified models or raw invoices, which are harder to interpret. Climate-compensated energy reporting also loses precision at lower resolutions — workarounds like SMHI normalization factors exist but only apply in Sweden.

**Future capabilities.** More advanced functionality — precise energy optimization, detailed system breakdowns, enhanced reporting — depends on having granular data to work from. Examples include breaking down energy usage for component-level analysis, and fine-tuning HVAC systems for maximum efficiency.

For sites aiming for the best possible optimization and reporting, higher-resolution data is the single biggest input you control.

### Requesting a new third-party integration

If you'd like Myrspoven to support an energy provider we don't currently integrate with, get in touch with your Myrspoven representative. We evaluate new integrations on a case-by-case basis depending on coverage, demand, and feasibility.

***


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.