Release notes

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.

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.

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).

The clients view shows the connection status of every client (Clients).

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

New administration views over the tags and the decision events of all tenants (Tags (administration), Decision events (administration)).

The content of the position cache can be inspected and filtered (Geo Cache).

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

The provider can be selected for a manual position request (How a Position is Determined).

No position request could be created from the web interface (How a Position is Determined).

An update of an LTE tag is only accepted for the client the tag belongs to (Clients).

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

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.

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).

In a cluster, the position cache of a newly started instance is synchronised with the existing ones (Geo Cache).

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

If the provider returns no usable result, a second provider is queried (How a Position is Determined).

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

Filters for the lists of cells, WiFis and beacons (Custom Locations).

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).

The tag filter allows several values per field and explicitly empty values (Tags).

The group selection showed the groups of all tenants (Groups).

Telemetry events were not forwarded to the connected clients (Clients).

Creating unique database indices failed on existing installations.

The tag list shows the real number of matches beyond 1000 rows (Tags).

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

Decision events now always show the most important data in the same format (Decision events).

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

The clients view was not visible with the tenant administrator role (Clients).

Resolving a tag occasionally failed with a duplicate key error (Tags).

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

A tenant administrator could not invite new users.

The tag list can be exported as CSV or JSON (Tags).

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

The position cache can be configured to use exact matches only (Geo Cache).

Several simultaneous connections of the same client are allowed (Clients).

The tag name and the actions column stay visible while the list is scrolled sideways (Tags).

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

BLE beacons could not be managed with the tenant administrator role (Custom Locations).

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

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).

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