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

# November 2026

**Version 2026.11**

***

### Highlights

**myPortal 2.0** reached every user in the first week of November and is replacing myPortal, which now receives fixes and small adjustments only. Accounts were opened in batches from 3 to 6 November at [app.myrspoven.com](https://app.myrspoven.com), and each user has a role that decides which pages appear in the menu. Since the launch, alerts have comments and a step-by-step **Investigate** tab, the dashboard map runs on Google Maps, **Sensor Map** has myPortal's one-click **Used by AI** switch above the sensor tabs, and the whole interface works in Swedish and on tablets and phones. The [myPortal 2.0 guide](https://docs.myrspoven.com/use-myportal-2.0/myportal-2) describes every page.

On the control side, signals the AI does not control are now held at their baseline and left out of the optimization's penalties. When the AI controls one heating circuit out of four, that circuit carries the full weight of the heating terms instead of sharing it with circuits it cannot move.

***

### myPortal 2.0

* **Available to every user:** all myPortal users got access in the first week of November. A user's role (Energy Specialist, Technical Specialist, Building Technician, Systems Integrator or Management) decides which pages they see; to change it, ask your Myrspoven contact. See [myPortal 2.0](https://docs.myrspoven.com/use-myportal-2.0/myportal-2).
* **Alerts:** each alert has a **Comments** tab where the team notes what it found or did, and the table and the dashboard card show the newest comment. The **Investigate** tab says what happened in one sentence and lists the steps to check it, each opening its page already on the right group or point. Alerts with no update for more than seven days are left out everywhere, and **All alerts** follows the portfolio group picked in the sidebar. See [Alerts](https://docs.myrspoven.com/use-myportal-2.0/alerts).
* **Alert map:** the dashboard map is now Google Maps, with towns, streets and building names as you zoom in. It shows the buildings of the status you pick, opens on your city, and the list and building card can be closed to see the whole map.
* **Sensor Map:** the **Used by AI** switch sits above the sensor tabs again, as in myPortal: switching it on saves at once, switching it off asks first. Buildings without floor plans get the full sensor panel and a list, the list sorts by its column headers, and the trend view shows one measure at a time with dates, zoom and long ranges. See [Sensor Map](https://docs.myrspoven.com/use-myportal-2.0/sensor-map).
* **Deviations:** hours outside the usual range are red ▲ and blue ▼ triangles, you can choose which point types the portfolio counts or count a single type in one click, and the chosen view stays as you move between buildings and pages. A building that deviates both ways now shows under either direction. See [Deviations](https://docs.myrspoven.com/use-myportal-2.0/deviations).
* **Equipment Control:** air handlers show their heat recovery and valve signals, and the averages can be read over a chosen period. Charts here and in **Group Control** can show the outdoor temperature as an overlay or on the same axis. See [Equipment Control](https://docs.myrspoven.com/use-myportal-2.0/equipment-control).
* **Savings:** when the AI started part-way through the period, the savings cards say "kWh since" and the start date.
* **Language and layout:** every user can pick English or Swedish, point types read in the chosen language, and the pages fit tablets and phones. The sidebar marks the current page and keeps the section headings in view, and the interface says "building" throughout, with **Portfolio overview** and **Building overview** as page names.

<figure><img src="https://2074044488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ0IsWgRagqUQj5pl27zJ%2Fuploads%2Fgit-blob-28b11fbd34da1ce86f2e0814aa91ad24ae4db8a9%2Falert-investigate.png?alt=media" alt="myPortal 2.0 alert sheet for an indoor temperature alert: the group was at 18.0 °C, 2.5 °C below its 20.5 °C minimum; tiles for building, active for 8 hours, last updated and severity Medium; the Investigate tab opens on Group Control with the group&#x27;s temperature against its limits."><figcaption><p>An alert opened on its Investigate tab, with Timeline, Comments and Technical details beside it.</p></figcaption></figure>

**Fixes**

* Signed-out users go straight to the login page instead of a blank page.
* **Occupancy** shows a building's air-handler schedule the day after its data arrives; an empty answer was kept for two weeks before.
* **Group Control** marks the groups the AI does not control and no longer warns about a lower bound before the AI controls the group.
* The outdoor temperature comes from the building's BMS outdoor sensor, or from its weather data when there is none.
* Filtering the **Portfolio overview** keeps the selected portfolio, and the **Feedback** button keeps the page responsive while it takes its screenshot.

### BackOffice & Integration - Partners

#### **Integrations**

* **Siemens Building X:** discovery maps heating circuits, tap water, room CO₂, valves and setpoints, keeps room signals on their room, and stops with a reason when it cannot read the equipment or the component types. A text value that Building X sends without escaping no longer loses every value of its device.
* **Ouman:** setpoints that differ from the previous write only in the second decimal now reach the controller, which used to see them as unchanged and fall back to its own curve.
* **Fabege:** each building gets a Myrspoven control switch that reads on, since Fabege's system has no building-wide one, and the startup check no longer blocks buildings over signals without a unit.

#### **BackOffice**

* **Single sign-on users:** a user who signs in through single sign-on is created without a password or two-factor setup, and the admin chooses whether to send an invitation.
* **User roles:** user-type roles decide which myPortal 2.0 pages a user sees, and are set in **User administration**.
* **Shadow signals:** one BMS point can feed several components. The extra signals follow their parent, are never read from the BMS, and get every stored value copied to them.
* **Lindinspect import:** stays responsive in buildings with thousands of zone components (requested by Fabege). The component field is a search box with the row's best matches first, components already used by other rows are left out, and each component takes one sensor per signal, with the reason shown when a row gets none.
* **Signal editor:** shows each signal's status and details, and the position picker shows the current position.
* **Myrspoven\_DS check:** signal validation checks the DS signal's name and position, since a misnamed or misplaced one silently drops a building's meter cleaning and ON vs. OFF analysis.
* **Golden Report:** PDF generation is removed from BackOffice. Savings are reported as [AI ON vs. OFF](https://docs.myrspoven.com/measure-savings/ai-on-off-savings).
* **Security:** access checks on the Web API are tightened, request tokens are kept out of logs, and vulnerable packages are patched in the platform and in myPortal 2.0.

**Fixes**

* Signal data writes no longer time out several times a week.
* Partners can save users who have myPortal 2.0 access; the save used to read the missing access as a removal and refuse it.

### Smart Control

* **Partly controlled systems:** signals the AI does not control (fixed, switched off in BackOffice, or steering no measured value) are held at their baseline over the whole plan and left out of the penalties. A controlled heating circuit next to three fixed ones now gets the full weight of the heating terms. Zone heating and cooling loads stay steered through the zone setpoint.

**Fixes**

* A building whose air handlers are all fixed is no longer put through air-handler grouping.
* A reference formula with a missing signal names that signal instead of failing the run.
* Setpoint mismatches are flagged only on signals the AI controls.

### Data Platform

* **Corrections reach the datalake:** updates and deletes in the platform database are applied to the datalake every three hours, and every step of the history backfill is checked against the source by row count and checksum. **Power Insights** reads the corrected values.
* **Prediction metrics:** the direction and bias of the digital twin's predictions are measured for every building.

**Fixes**

* **AI ON vs. OFF:** a day no longer loses its AI status when some of its hours have no reading of it.


---

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