In this release
This release adds faceted twin search to ProptechOS MCP. Twin references can now resolve by littera, so agents can find and address twins by the names an estate already uses. Autonomous agents get the current date and time on every run, and access policies scoped to a collection now cover the twins in it.
Three new quantity kinds model thermal and generic power and energy. A new SafeLine connector, an unmanaged connector type, MQTT over TLS and several connector and platform fixes complete the release.
If your agents or integrations call ProptechOS MCP, read the breaking changes below. Five MCP tools are removed and two response fields change.
For teams running agents across a portfolio, this means less setup and more reliable output. Agents can refer to equipment by the tags your estate already uses, so prompts no longer need long lists of IDs maintained by hand. Reports carry the correct date. Access can be granted to a single system, such as one ventilation or heating system, without opening up the whole building. District heating and cooling meters get their own quantity kinds, and the connector fixes close gaps in energy, footfall and weather data.
MCP
Faceted twin search
MCP search used to be a substring text search with no filters or relations. Three new tools find twins of a given type with the same filters as the platform API:
- find-devices: filter by quantity kind, placement, unit, function, device class, building, storey, room, served building, super device, asset, collection, name, littera and status.
- find-spaces: real estates, buildings, storeys and rooms, scoped by building or storey and filtered by collection, name, littera and status.
- find-assets: scoped by building or room and filtered by collection, name, littera and status.
All three accept resultFormat=COUNT, which answers questions like “how many energy meters are in this building” without returning rows. They replace five older tools; see Breaking changes.
Twin references accept littera
Every *Ref argument across ProptechOS MCP now resolves a twin by UUID, popular name or littera. Before, only UUID and popular name worked, so agents had to look a twin up by littera and then pass its UUID.
Resolution goes in this order:
- A UUID is used as is.
- An exact popular name or littera match wins. If longer partial matches also exist, they are returned as a note on get-sensor-latest-data and get-sensor-historical-data.
- A single partial match resolves, with a note saying so.
- Several exact matches, or several partial ones, return a disambiguation list with the full UUID of each candidate. The tool never guesses.
Agent prompts no longer need hard-coded lists of twin UUIDs.
Name references and twin status
- Name resolution covers all statuses. Name references prefer Valid twins and fall back to any status when no Valid twin matches, so twins being onboarded (for example Incomplete or Test) can be referenced by name. The response says when the fallback was used. Two exceptions stay Valid-only: actuator references, so a setpoint never lands on an actuator marked Test, Incorrect or Archived, and room and storey matching in the climate tools.
- Full status filter. The search tools accept every twin status, including Archived and Suspended, and return each match’s status.
- Clearer twin references. Assets report their room as locatedIn, building components report partOf, and every twin reference includes its twinClass. Device and asset rows now include their building.
- Smaller responses. When every row on a page shares the same parent or facet, it is returned once in sharedRefs instead of on every row.
- Paged history. get-sensor-historical-data now reads observations page by page.
Autonomous Agents
Current date and time in agent context
The agent runtime now stamps the current date and time on every message it sends to the model. The stamp is in ISO 8601, in both Europe/Stockholm time and UTC. This covers scheduled routine runs, human messages and agent-to-agent routing.
Agents now date their reports correctly and judge data freshness against the real time without prompt workarounds. Agents whose prompts have a rule like “don’t run twice within 4 hours” no longer skip runs because they can’t tell the time.
API
Collection-scoped access policies
An access policy with included.Collection and propagatable: true now grants access to the twins the collection contains. Before, it covered only the collection twin itself.
A policy scoped to one System now grants its devices, sensors and actuators. Before, you had to list every member twin or grant the whole building. Because membership is checked when a twin is read, twins added to the collection later are covered too.
- Only direct members are covered. Membership is not followed through nested collections.
- Write access to members still requires their class in allowWriteTwinClasses.
- A twin in excluded is still excluded.
- This applies to every collection type: System, TenantUnit, Apartment, Region and SpaceCollection.
Edge Management API
Unmanaged connector type
A new unmanaged connector type lets you model a connector that ProptechOS does not deploy or manage, such as one running on your own server, as a logical device in the twin graph. Edge Management never deploys a logical device of this type.
Ontology
New quantity kinds
Three quantity kinds are added to the ProptechOS extension ontology:
| Quantity kind | Description | Unit |
| PowerTotal | Generic instantaneous power | kW, W |
| ThermalPower | Thermal (heat flow) instantaneous power | kW, W |
| ThermalEnergy | Cumulative thermal energy | kWh |
District heating, district cooling and thermal submeters no longer need to borrow electrical quantity kinds such as ActivePowerTotal.
Edge Connectors
New edge connectors
- SafeLine – a new HTTP connector for SafeLine lift monitoring. It reads operating state, service mode, alarm state and connectivity, so you can tell whether a stopped lift is out of service or offline.
Connector improvements
- Alert clearing: an ERROR_WHILE_POLLING_DATA alert now clears when the connector sends data again. This applies to connectors built on the new connector library version.
- Network interruptions: connectors reconnect after short network interruptions.
- SMHI: weather analysis data now comes from SMHI’s Mesan2g v3 API, because v2 was retired on 1 November 2026. v3 uses a different grid, so expect a small step in the analysis values at the switch. One failed device no longer stops polling for the others.
- Ubiqisense: footfall counts are no longer dropped, and building-level footfall sensors are now polled.
- Google BigQuery: an unconfigured energy type no longer blocks the other observations in the same message.
- Enity: the configurable read delay (readDelayHours) is now applied.
- Saia: setpoint values sent to actuators are now stored as observations.
- Sungrow: the measurement point can be configured per sensor: lifetime energy, active power, MPPT DC, or status and fault.
- Profinet: LReal (8-byte double) data points are supported.
MQTT over TLS
The shared ProptechOS MQTT broker now accepts TLS connections on port 8883 (TLS 1.2 and 1.3) with a public certificate. Use the same username and password as on port 1883, which stays open for now. Devices with no built-in CA store need the Let’s Encrypt chain in their truststore.
Breaking changes
- MCP tools removed. Five tools are replaced by the new search tools. Update agent prompts that call them:
| Removed tool | Use instead |
|---|---|
| get-all-buildings | find-spaces {“spaceType”:”BUILDING”} |
| get-buildings-by-name | find-spaces {“spaceType”:”BUILDING”,”name”:”X”} |
| get-real-estate-by-name | find-spaces {“spaceType”:”REAL_ESTATE”,”name”:”X”} |
| get-assets (for a sensor inventory) | find-devices {“buildingRef”:”X”,”deviceType”:”SENSOR”} |
| get-assets (for a room list) | find-spaces {“spaceType”:”ROOM”,”buildingRef”:”X”} |
| get-actuators-by-room | find-devices {“roomRef”:”X”,”deviceType”:”ACTUATOR”} |
- MCP twin references. For assets, the parent room is now returned as locatedIn instead of partOf, and twin references include twinClass. Update any integration that parses these responses directly.
Fixes and minor improvements
- PLAT-5934: arithmetic function sensors on older function definitions were not calculated. A missing perSensorAggregation now defaults to Sum.
- PLAT-5981: GET /json/skills with search returned 500 when x-property-owner was set without privateOnly.
- PLAT-3852: updating a twin with a duplicated alias now returns a clear error.
- PLAT-5857: creating an internal autonomous agent could fail with a 400 and no message.
- PLAT-5878: updating application scopes did not finish correctly.
- PLAT-6053: Swagger login through the gateway host now completes. Each service’s Swagger UI redirects to the gateway’s own Swagger UI.
- PLAT-5989: Snowflake data warehouse import now retrieves data in pages.
- PLAT-5525, PLAT-5997, PLAT-6003: faster access checks and graph queries for API requests, including latest observations.
- PLAT-5976: each edge box now has its own identity instead of a shared secret.