---
title: Release notes
id: "en:tpm:ROOT:release-notes.adoc"
site: en
component: tpm
module: ROOT
version: 3.0
lang: en
url: "https://help.rtlscloud.io/en/tpm/3.0/release-notes.html"
source_repo: "https://github.com/iot-invent/rtlscloud-tpm.git@3.0.x"
source_path: "docs/en/modules/ROOT/pages/release-notes.adoc"
---

# Release notes

All changes per version, grouped into Added, Changed, Fixed and notes. For a shorter summary of the highlights see [What’s New in Tag Provisioning & Management 3.0](whats-new.md).

## Tag Provisioning & Management 3.0

> **NOTE:** Version 3.0 is still under development. The information on this page may still change before release.

### Changed

-   The German user interface is fully translated; labels that were previously shown in English now appear in German.

-   The map views – decision events, position cache and choosing a position in the wizard – were moved to the new map component.

-   Forwarding device messages between UDP and TCP handles connection drops more reliably.

### Update notes

-   MongoDB 6.0 is now the minimum requirement.

-   The user interface was moved to a new version of the UI framework. Please check your usual workflows after updating.

## Tag Provisioning & Management 2.1.10

_Released on 29 July 2026._

### Fixed

-   A tag seen through a BLE beacon acting as a gateway additionally received a conflicting position from the online service ([How a Position is Determined](positioning.md)).

## Tag Provisioning & Management 2.1.9

_Released on 16 July 2026._

### Added

-   The clients view shows the connection status of every client ([Clients](clients.md)).

### Fixed

-   Large responses of the UDP-to-TCP gateway were truncated.

## Tag Provisioning & Management 2.1.8

_Released on 9 July 2026._

### Added

-   New administration views over the tags and the decision events of all tenants ([Tags (administration)](admin/tags.md), [Decision events (administration)](admin/decision_events.md)).

-   The content of the position cache can be inspected and filtered ([Geo Cache](admin/geo_cache.md)).

-   A BLE beacon can act as a gateway, and the tags it sees take over its position ([Custom Locations](custom_locations.md)).

-   The provider can be selected for a manual position request ([How a Position is Determined](positioning.md)).

### Fixed

-   No position request could be created from the web interface ([How a Position is Determined](positioning.md)).

-   An update of an LTE tag is only accepted for the client the tag belongs to ([Clients](clients.md)).

-   The tenant settings could not be changed with the tenant administrator role.

### Update notes

-   TPM can be run with several instances: every client connection gets its own assignment, and the load is divided between the instances instead of being duplicated.

-   Events and decisions are published through the event streaming system. A single-node installation does not need an external service.

## Tag Provisioning & Management 2.1.7

_Released on 13 May 2026._

### Added

-   A tag carries a desired configuration. On connect, TPM checks whether the tag’s configuration profile has to be updated, and only then sends a new configuration ([Tags](tags.md)).

### Update notes

-   In a cluster, the position cache of a newly started instance is synchronised with the existing ones ([Geo Cache](admin/geo_cache.md)).

## Tag Provisioning & Management 2.1.6

_Released on 16 April 2026._

### Added

-   Neighbouring cells can be taken into account, which improves the position where the serving cell alone is not enough ([How a Position is Determined](positioning.md)).

-   If the provider returns no usable result, a second provider is queried ([How a Position is Determined](positioning.md)).

-   If a request with WiFi data is not valid, the search falls back to the serving cell alone ([How a Position is Determined](positioning.md)).

-   Filters for the lists of cells, WiFis and beacons ([Custom Locations](custom_locations.md)).

### Fixed

-   IMSI, ICCID and IMEI are checked to be numeric before they are stored, so a garbled report no longer creates a tag with an unusable identity ([Tags](tags.md)).

## Tag Provisioning & Management 2.1.5

_Released on 26 March 2026._

### Added

-   The tag filter allows several values per field and explicitly empty values ([Tags](tags.md)).

### Fixed

-   The group selection showed the groups of all tenants ([Groups](tag_groups.md)).

-   Telemetry events were not forwarded to the connected clients ([Clients](clients.md)).

## Tag Provisioning & Management 2.1.4

_Released on 20 March 2026._

### Fixed

-   Creating unique database indices failed on existing installations.

## Tag Provisioning & Management 2.1.3

_Released on 19 March 2026._

### Added

-   The tag list shows the real number of matches beyond 1000 rows ([Tags](tags.md)).

### Fixed

-   When all WiFis were filtered out, the search over the serving cell was skipped and no position was produced ([How a Position is Determined](positioning.md)).

-   Decision events now always show the most important data in the same format ([Decision events](decision_events.md)).

-   The location area code is no longer used to find a locally configured cell, because it changes without the cell changing ([Custom Locations](custom_locations.md)).

-   The clients view was not visible with the tenant administrator role ([Clients](clients.md)).

## Tag Provisioning & Management 2.1.2

_Released on 10 March 2026._

### Fixed

-   Resolving a tag occasionally failed with a duplicate key error ([Tags](tags.md)).

## Tag Provisioning & Management 2.1.1

_Released on 4 March 2026._

### Fixed

-   WiFi data below the required minimum count is no longer sent to the provider ([How a Position is Determined](positioning.md)).

-   A tenant administrator could not invite new users.

## Tag Provisioning & Management 2.1.0

_Released on 2 March 2026._

### Added

-   The tag list can be exported as CSV or JSON ([Tags](tags.md)).

-   A wizard assembles a position request by hand and shows what the provider answers ([How a Position is Determined](positioning.md)).

-   The position cache can be configured to use exact matches only ([Geo Cache](admin/geo_cache.md)).

-   Several simultaneous connections of the same client are allowed ([Clients](clients.md)).

-   The tag name and the actions column stay visible while the list is scrolled sideways ([Tags](tags.md)).

-   Actions in lists are also available through a button in the toolbar, and the online help is opened with a button in the header.

### Fixed

-   BLE beacons could not be managed with the tenant administrator role ([Custom Locations](custom_locations.md)).

-   A search over the serving cell alone only returns results that are themselves based on the cell alone ([How a Position is Determined](positioning.md)).

### Update notes

-   The position cache is based on a new technology and can be distributed over several instances. The previous settings for lifetime and cleanup interval are no longer evaluated; expiry is now configured in the cache configuration ([Geo Cache](admin/geo_cache.md)).

-   The user interface was moved to a new version of the UI framework. Please check your usual workflows after updating.
