Release notes

Device profiles: shared configuration for several devices, assignable from the device list (Devices).

Device profiles can be exported and imported.

A device profile can be shared across tenants and reassigned to another space.

Calibrated floor plans are shown on the world map in the location views (Location > GPS).

Floor plans larger than 8192 x 8192 pixels are supported (Locations).

An anchor can be operated without a scenario in order to scan before it is configured — device setting "Scan without a scenario" in the device view.

The outline of a place found through the place search can be taken over as the boundary of the GPS location being edited; until now it was only displayed (Location > GPS).

New device type "Generic" for devices that rtlscloud does not manage. They only report events and measurements and can be registered under an IoT gateway or an Edge without a profile of their own (Devices).

BLE presence detection has two additional settings: a location a tag is booked to when it leaves, and how long it may go unseen before that happens (600 seconds by default).

The standalone distribution exposes the interfaces for devices, device profiles, locations and location types. Intended for integrations with third-party systems.

The space wizard asks for the type of the space in its first step. General and Infrastructure are offered; the type determines which of the following steps apply and is fixed afterwards (Space setup).

Firmware images for xTags can be uploaded to the file store. Devices fetch them from there instead of carrying them inside their own distribution package (Files).

The default values of the LTE tag profile v1.05 were updated. Relevant for newly assigned LTE tags (Tags).

The location map editing dialogs and the device placement wizard step were moved to the new map component (Location, Space setup).

GPS locations are edited in a dedicated dialog (Location > GPS).

By default, BLE presence detection now considers every MAC address. Previously two vendor prefixes were preset and all other tags were silently passed over.

Application spaces are not shown in IoT Spaces — this is where infrastructure is configured, and such a space owns none. In the device and tag lists it is no longer selectable as an owner either (Space type).

Switching application can change the selected space: if it is not one the target application works with, the corresponding one is selected instead — leaving an application space lands on its infrastructure space. The application itself always stays reachable.

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.

If a presence scenario of yours relied on the preset MAC prefix list, enter the prefixes you want explicitly after updating. Otherwise tags that used to be passed over will now be picked up.

A crosshair shows the exact position under the pointer while calibration points are set and items are placed (Location).

The map of a location can be replaced without creating the location again (Locations).

A confidentiality agreement can be shown before an export, which the user has to accept.

The device model and the profile for LTE tag firmware 1.05 were updated (Tags).

A shared tag profile could not be created (Tags).

Opening an indoor map through a URL used the wrong zoom level (Location).

A message-processing template was not loaded from its template definition (Gateways).

A retry time can be configured for the tag service, after which a failed operation is tried again (Tags).

Device model and profile for LTE tag firmware 1.05 (Tags).

The labels filter in the tag list did not return the expected matches (Tags).

Filtering the tag list by profile failed with an error (Tags).

Signing in to a fresh installation without an existing space raised an error (Space setup).

The tag filter can negate values and filter explicitly for empty values — for example all tags without a profile (Tags).

The CSV export of the tag list contains the profile (Tags).

The timestamp of the last successfully or unsuccessfully processed message is shown (Gateways).

Lists show the real number of matches beyond 1000 rows (Tags).

The filter of the tag list is evaluated in the query, which keeps the match count and the paging correct (Tags).

Error messages no longer contain technical stack traces.

The CSV export contained two confusingly similar fields for the firmware version; one remains (Tags).

The CSV export of the tag list did not contain the expected columns (Tags).

A space administrator could not create devices (Devices).

The space selection is presented as a tree (Space setup).

Every space gets a generated key (Space settings).

Flows can be managed, started, stopped and monitored per tenant (Gateways).

A shared edge can be run in the cloud per tenant (Gateways).

Profile for LTE tag firmware 1.04 (Tags).

The space of a device can be changed in the administration (Devices).

REST interfaces for location types and locations, including the child locations and the path to a location (Locations).

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

The tag profile selection respects the space of the selected tags (Tags).

A device could be moved into a space where that is not allowed (Devices).

A device administrator could not create new Anchor+ devices (Devices).

The filter of the tag list behaved unpredictably (Tags).

A feature of a location type was not inherited by its child types (Locations).

Map popups are no longer cut off at the edge of the map (Location).

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

Events are now distributed through the event streaming system instead of inside the application. Make sure the streaming service is reachable.