> 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/release-notes/2025/november-2025.md).

# November 2025

**Version 2025.1**

***

### Highlights

* This release brings improvements to Golden Reports, especially valuable during the reporting season.
* We have also added features that help manage periods of rapidly changing outdoor temperatures (typically in spring and autumn) and mitigate indoor climate issues by allowing ventilation to be used for heating.

***

### myPortal — Customers

* Historical min-max view in prediction graphs for longer time spans.
* Cleaned and stabilized the test suite, improving diagrams and visualizations.

### BackOffice & Integration - Partners

* Removed an unused internal tool from the Process Viewer.
* Removed changelog from BackOffice front page.
* Case-insensitive matching in signal upload.
* Better signal validation feedback and test coverage when uploading signal files during integration.

### Smart Control

* Introduced heat-with-ventilation factor improvements that allow ventilation usage to support heating, which is relevant in some buildings. This brings settings flexibility and supports a better indoor climate.

### Golden Reports

* Golden Reports dashboards support "no ventilation" components.
* Golden Report uptime calculation corrected.
* Golden Report dashboards: can pick end-of-month or first-next-month date.
* Golden Report baseline and potential energy computation adjusted.

{% file src="/files/gNjRmQLxsZ9uDfI8oeT6" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.myrspoven.com/release-notes/2025/november-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
