> 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/2026/february-2026.md).

# February 2026

**Version 2026.2**

Covers changes since the December 2025 release.

***

### Highlights

This release introduces the new **Insights** page, which provides clear analysis across **climate, signals, and ventilation**. It is powered by our evolving Data Platform, which we have enhanced over the past few months to deliver reliable, well-structured data. The release also brings increased reliability, performance, and data accuracy throughout the system.

***

### myPortal — Customers

* Faster, more responsive views for large datasets — especially Zone Assets in buildings with areas greater than 10,000 m².
* Improved handling and display of sensor values, with clearer units and error messages.

### BackOffice & Integration - Partners

* Added **Yggio** as a building data provider to support seamless integration.
* Enhanced visualization of faulty data in the **Dataset Viewer**, including clear indicators for frozen periods.
* Focused improvements to Zone Assets building integration tools, including the **Components Editor**.

### Smart Control

* Greater robustness in optimization and training workflows, with improved handling of data issues — resulting in higher uptime and more consistent savings.
* Improved handling of non-office periods, especially around end-of-year holidays when many systems are offline. Optimization now continues reliably during these periods instead of failing on missing data.

### Insights

The Insights menu includes three views.

#### **Climate**

* Display historical climate data (temperature, CO₂ level, relative humidity) with up to one year of history.
* Show climate thresholds to assess optimization performance.

#### **R/W Discrepancies**

* Pinpoint deviations that require attention to ensure optimal energy savings results.
* Tap to select Office hours / All hours.

#### **CO2 Detailed**

* Information about CO₂ levels during the day/week.
* Suggestions for changing start/stop times for ventilation based on CO₂ level analysis.

<figure><img src="https://2074044488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ0IsWgRagqUQj5pl27zJ%2Fuploads%2Fgit-blob-00fde4717a20cf4a2d513a265f020318ebda0ec8%2Fimage%20(6).png?alt=media" alt="Insights view showing indoor-climate data."><figcaption></figcaption></figure>


---

# 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/2026/february-2026.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.
