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

# October 2026

**Version 2026.10**

***

### Highlights

**myPortal 2.0** (Beta) is still in testing, with release planned for November 2nd. Two of its pages are shown below as a preview: **Alerts**, redesigned around a map of the portfolio with each property coloured by status, and the new **Property overview**, which puts a property's key figures, open alerts and health check on one page. The full write-up follows with the release.

On the control side, the **AHU supply temperature** heuristic again treats outdoor temperatures up to 15 °C as half cold, with a gentler band during occupied hours. The AI control status of every signal now reaches the optimizer: a point switched off is observed but never written to, and switching the AI off for a building stops the writing while optimization keeps running. The savings method is stricter too: a heating baseline that stays flat as it gets colder no longer passes as a heating curve.

For partners, **Siemens Building X** discovery now maps rooms, chillers, heat recovery and heating supply temperatures, the old **Fidelix** integration is retired in favour of Fidelix Analytics, a signal that moved to another data provider can be merged into its predecessor, large signal sheets upload in seconds, and every API compresses its responses for clients that accept it.

***

### myPortal 2.0 (Beta)

Some samples pages that are in the current main view, full details after the release.

* **Alerts:** redesigned with customer-facing categories, a status timeline per property, one filter bar with stale alerts hidden by default, one-click acknowledge and the newest alerts first. The dashboard opens with what needs action, a map of the portfolio coloured by status (Needs action, Underperforming, All clear) and recent events, and the AI status reads Online, Offline or Disabled everywhere.
* **Property overview:** one page per property: AI status with its switch, indoor temperature and drift, savings over 365 days, AI uptime over 30 days, how much of the equipment the AI may use, the most important open alerts and the health check. It replaces the Healthcheck page; old links open the overview.

<figure><img src="https://2074044488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ0IsWgRagqUQj5pl27zJ%2Fuploads%2Fgit-blob-f75bebf0360c87fa95754a97e35adfa262cd243e%2Fdashboard-alert-map.png?alt=media" alt="myPortal 2.0 dashboard: four cards for average temperature, active buildings, total savings and AI uptime, then the Alerts section with a map of the portfolio where each property is a dot coloured by status, a list of the buildings that need action, and the alert card of the selected property with its five active alerts by category."><figcaption><p>Dashboard: the alert map, the properties that need action, and the alert card of the selected one.</p></figcaption></figure>

### BackOffice & Integration - Partners

#### **Integrations**

* **Siemens Building X:** rooms are now modelled as zone controls with their temperature, heating and cooling valves, supply temperature and fan, which positions 260 points where 103 were positioned before. The heating supply temperature, chiller pumps, exhaust air flow, cooling coil valves, exhaust dampers and heat recovery efficiency are mapped, setpoint limits no longer land in the setpoint position, and supply and exhaust fan indications are no longer crossed.
* **Fidelix:** the old integration is retired and Fidelix Analytics replaces it. Retired providers are no longer offered in provider pickers.
* **Electricity meters:** per-phase power (L1, L2, L3) has its own signal positions used mainly for **Power Insights**
* **Propeye:** discovery records each meter's DevEUI and keeps unit, description, read/write and AI control status current, and missing or rejected credentials are explained instead of failing silently.
* **Discovery:** an integration can keep the signal properties it owns up to date on existing signals; manual edits stay.

#### **BackOffice**

* **Signal merge:** a signal that moved to another data provider can be merged into the old one, which keeps its id, history and components.
* **Installations:** Access > Installations lists each Myrspoven Edge installation with its status, version and last successful process.
* **Faster large uploads:** re-uploading a 46 000-row signal sheet took two minutes and timed out; it now completes in seconds, and edits that are valid only together now pass validation.
* **Compressed responses:** every API, including the Reports API, compresses its responses for clients that accept gzip.

**Fixes**

* The comfort schedule building picker lists buildings shared through cross-company groups.
* Signal group averages no longer come back empty for recently added signals.
* Each validation problem is reported once instead of once per field.

### Smart Control

* **AI control status:** myCoreAI now reads each signal's AI control status instead of inferring it from the signal's role. A point switched off is observed but never written to, and switching the AI off for a building stops the writing to the BMS while optimization keeps running, so predictions and insights continue.
* **AHU supply temperature:** outdoor temperatures up to 15 °C count as half cold (previously 10 °C), and during occupied hours the supply bounds sit 0.5 to 1.5 °C below room temperature instead of 1 to 3 °C, so less cold air is pulled in while people are there.
* **Training with sensor gaps:** the digital twin masks missing observable signals per equation during training.
* **Pump indications:** pump on/off indication signals have their own positions in the building model.

**Fixes**

* An optimization no longer fails when a return-pressure offset refers to a signal without a minimum.

### Data Platform

* **Savings method hardened:** a heating baseline that stays flat as it gets colder is rejected instead of passing as a heating curve, and meter days without hourly on/off data are labelled rather than left blank.
* **Power Insights data:** hourly series and per-phase peaks are stored per meter, which is what the phase lines in the interface read from.
* **Daily building metrics** run in Airflow and land in the datalake, and reference data metrics are written even when a building's run fails.
* **Alerts:** building issues are ingested and exposed through the API, which the Alerts page reads.
* **Datalake maintenance:** orphan-file cleanup and partition rewrites run in batches and recover from resource exhaustion.


---

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