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

# June 2026

**Version 2026.6**

***

### Highlights

June completes the **OpenMeteo** migration. Every building now uses the new weather provider for more stable and accurate predictions. A new data integration went live (**ProptechOS**), sensor onboarding added room-sensor support, and myPortal and BackOffice now support single sign-on. The optimizer is also faster and more resilient.

***

### myPortal — Customers

* **Single sign-on** — myPortal now supports a unified login across Myrspoven products.
* **Sensor map** — design improvements to the floor-plan view, and floor-plan blueprints are now supported for placing sensors.
* **Insights** — corrected the outdoor-temperature series in the climate trend.

**Fixes**

* Access pages occasionally failed to load (including when page styling was served from cache) — resolved.
* User lists now display correctly even when a user has no name set.

### BackOffice & Integration - Partners

#### **New integrations**

* **ProptechOS** — new building data provider with full discovery, read, write, and historical support.
* **Fidelix Analytics** — custom unit parser plus correct unit and data-type mapping.

#### **BackOffice**

* **Manual setpoints** — now shows optimizer status with an enable/disable toggle, and supports write signals without transformation tables (including self-referencing transformations).
* **Comfort schedule** — night cooling can now *raise* AHU pressure via a negative pressure factor, not only lower it.
* **Partner superusers** can now edit all of their company's building groups, not only the ones they belong to.
* **Blueprints** — create and manage floor-plan blueprints for sensor placement.

**Fixes**

* Long signal names no longer break the Comfort Schedule UI.
* Building groups now shown.

### Smart Control

* **All buildings now use OpenMeteo** — the weather-provider migration begun in May is complete, giving more stable and accurate weather inputs to every building.
* **Smarter ventilation grouping** — buildings where more than half the circuits are ventilation now switch to ventilation-based grouping automatically.
* **Faster optimizer** — per-run data fetch cut from 225 hours to 48; baseline ventilation handling reworked for speed.
* **More resilient** — the optimizer now handles signals being enabled or disabled mid-run without disruption.
* **Dew point safety margin** — added and validated the +2 °C condensation guard on chilled-water setpoints.

**Fixes**

* Comfort schedule no longer lowers too far when a signal's min/max bounds are low.
* Ventilation supply temperature on no-cooling systems is now clipped by outdoor temperature.

### Data Platform

* **Meter data processing** — district-heating and metering data processing now handles higher volumes more efficiently.
* **Building analysis overview** — a new weekly aggregation job and square-metre (m²) KPI normalization, complementing May's daily aggregator.
* **Faster deviation summaries** — deviation data is now preaggregated, cutting query time and memory use.
* **Data maintenance** — routine processing and maintenance now run more efficiently.


---

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