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

# April 2026

**Version 2026.4**

***

### Highlights

This release focuses on making AI performance more visible and verifiable, both for customers in myPortal and for partners in BackOffice. The new AI Performance view provides a cleaner, more complete picture across all building systems.

***

### myPortal — Customers

#### **AI Performance** *(replacing AI vs Baseline)*

* The new AI Performance view lets customers monitor and compare AI-controlled system performance across their building.
* Components are grouped by system, such as Heating and Ventilation, with individual time-series graphs showing how the AI manages each signal.
* Customers can filter by component type and date range, and drill into any signal for a detailed breakdown.
* The view also includes a side-by-side comparison of actual AI behavior vs. the estimated without-AI counterfactual, plus weather context and air quality data.

<figure><img src="https://2074044488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ0IsWgRagqUQj5pl27zJ%2Fuploads%2Fgit-blob-d02434490c66eff334c25cbdef0e587ec460fcc0%2Fimage%20(4).png?alt=media" alt="AI Performance view showing system performance."><figcaption></figcaption></figure>

<figure><img src="https://2074044488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ0IsWgRagqUQj5pl27zJ%2Fuploads%2Fgit-blob-6e8d096a3d3ec0f392386610c84502dc4e911742%2Fimage%20(5).png?alt=media" alt="Sensor Map view for a building without a floor plan."><figcaption></figcaption></figure>

#### **Sensor Map** *(signal list for blueprint-free buildings)*

* For buildings without a floor plan, the Sensor Map now displays as a full signal list.
* Customers can see all apartment and zone sensors in one scrollable view, with live comfort status, current temperature values, AI-enabled toggles per sensor, and editable min and max setpoints.
* From the same view, users can search, filter by group, flag bottlenecks, and save custom sensor groups or create trends — the same capabilities as the map view.

### BackOffice & Integration - Partners

#### **Integrations**

* **Building-data integration** — write and discovery capabilities improved.
* **Siemens Building X** — Discovery enriched with point-group tags and improved HVAC tag aliases for better SignalPosition mapping.
* **Propeye** — Historical read support added.

#### **AI Control Page**

* A new diagnostic view in BackOffice highlights and helps debug AI Control configuration issues per building.

#### **Signal History Gap-fill**

* Preview and insert missing data gaps in signal history directly from BackOffice.
* Useful when BMS data readings have been faulty, or to upload historical energy meter data essential to evaluations.


---

# 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/april-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.
