> 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/ai-features/loadshift.md).

# myLoadshift

myLoadshift factors energy prices into myCoreAI's control decisions, shifting consumption toward cheap hours and away from expensive ones. Comfort bounds are untouched — only the timing of energy use moves.

## What it does

myCoreAI balances comfort, energy use, and — when myLoadshift is enabled — energy cost. Each hour's energy penalty is multiplied by that hour's price, so cheap hours look cheaper to use and peak hours look costlier to avoid. Comfort targets remain fixed.

## How it works

* **Normalization** — the price curve is scaled so its mean over the optimization horizon equals 1. Only the *shape* of the curve influences when energy moves, not its absolute level.
* **Peak amplification** — prices in the top of the day's range are amplified, so peak hours are actively avoided rather than mildly deprioritized.
* **Edge cases** — negative prices clamp to zero. Missing prices fill from the hour-of-day average across the available window. Past prices never influence future policy.

### Worked example

A district-heated office on a utility that publishes a dynamic tariff sees a sharp morning peak between 06:00 and 08:00. With myLoadshift enabled, myCoreAI pre-heats heating circuits during the cheaper overnight hours so the building reaches the morning comfort bounds on stored thermal mass. Supply temperatures drop during the priced peak, then resume normal control once the tariff falls. Indoor climate stays inside the configured comfort bounds throughout — only the energy timing shifts.

## Scope

myLoadshift acts on heating supply temperatures for heating circuits and air handling unit (AHU) heating coils. It runs against two price sources:

| Controls                                                     | Energy source    | Price source                           |
| ------------------------------------------------------------ | ---------------- | -------------------------------------- |
| Heating supply temperatures (circuits and AHU heating coils) | Electricity      | ENTSO-E spot market                    |
| Heating supply temperatures (circuits and AHU heating coils) | District heating | Dynamic district heating tariff signal |

myLoadshift is enabled per energy type and only influences the parts of the building supplied by that source.

## Requirements

* **Component setup** — each heating component linked to its energy source so myCoreAI applies the correct price curve.
* **Price data** — a live or forecasted price feed for the targeted energy type. Electricity uses the ENTSO-E spot market; district heating depends on whether the utility publishes a dynamic tariff.

## Comfort always wins

myLoadshift operates strictly within the building's comfort bounds and operating limits. If a shift would compromise indoor climate, myCoreAI does not execute it.


---

# 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/ai-features/loadshift.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.