Release update 112 (2026-03-26)
Sprint 112 (released on 26-03-2026) brings 5 new features and 1 bug fix to the Cuebly platform. This release focuses on improving usability across the Account Manager environment, enhancing beacon identification, and giving account managers greater control over location validity. Read on for the full details.
New & improved features
[#109] Beacon major and minor shown both in Decimal and Hexadecimal in the beacon list
The beacon overview list in the Account Manager environment now displays both the Decimal and Hexadecimal values for the Major and Minor fields of BLE beacons. Previously, only the Decimal value appeared in the list. Because some beacon brands display Hexadecimal values directly on the hardware, this change makes it significantly easier to identify a specific beacon in the platform. Furthermore, you can search on both value formats using the column filter feature.
- Both Decimal and Hexadecimal values for Major and Minor are now visible in the beacon list.
- The column filter supports searching on both value formats.
- Identifying a beacon by its printed label is now much quicker and more reliable.
[#112] New behaviour on Account and Device filter in Account Manager environment
Previously, the Account and Device filter in the Account Manager environment began filtering as soon as you started typing. Based on user feedback, this behaviour felt unintuitive, and Cuebly agrees. As a result, the filter field now only triggers when you either click the newly added search icon or press Enter on your keyboard. This gives you full control over when the filter activates.
- Filtering no longer starts automatically while typing.
- A new search icon has been added to trigger the filter manually.
- Pressing Enter on your keyboard also triggers the filter.
[#115] Contact name is being used as device name when an app user is created directly from a contact
There are two ways to create an app user: directly from the user overview in the Account, or directly from a contact (provided the contact has an email address). Previously, both methods named the newly created device after the email address. Now, whenever you create an app user from a contact, the platform uses the contact name as the device name instead. This improves the overall user experience and removes the need to rename the device manually afterwards.
- The contact name now serves as the device name when creating an app user from a contact.
- App users created from the user overview continue to use the email address as the device name.
- The contact must have an email address in order to create an app user from it.
- There is no longer a need to rename the device after creation in most use cases.
[#15] Warning shown when Emerit device cannot be configured through Cuebly
When an Emerit device connects to the Emerit Services platform, Cuebly cannot configure that device remotely. In preparation for upcoming improvements, such as advanced connection monitoring and reduced data and battery usage, Cuebly now displays a warning on the DevCon icon of any Emerit device that it cannot control remotely. These future improvements will only function when the device is under Cuebly’s control, so this warning helps users identify devices that need attention ahead of that release.
- A warning now appears on the DevCon icon for Emerit devices that Cuebly cannot control remotely.
- The warning prepares users for upcoming Emerit improvements, including advanced connection monitoring and lower data and battery usage.
- Those future improvements will require the device to be controlled by Cuebly.
[#86] Option to choose the location validity on an Account level
Cuebly displays both when a location event is received and when the device itself determined the location. When the gap between those two moments is small, the location is current. When that gap is larger, the location is older and may be less relevant depending on the use case. This new feature lets you set the maximum location validity at account level, using presets ranging from 30 minutes to 24 hours. By default, the setting remains ‘always show last known location’, as before. When you set a validity of 30 minutes, for example, any location older than 30 minutes is hidden and the platform treats the device as having no location available. This can make a significant difference in how alarm operators experience location data.
- A new account-level setting controls the maximum validity of location data.
- Presets range from 30 minutes to 24 hours.
- The default remains ‘always show last known location’.
- Locations older than the chosen threshold are hidden and treated as unavailable.
- The setting is configurable per account to suit different use cases.
Bug fixes
[#126] Reverting to last edited dashboard tile when adding a new tile
In some cases, after editing a dashboard tile, the settings of that previously edited tile would appear instead of the new tile selection list when you tried to add a new dashboard tile. This issue has now been resolved, so adding a new tile correctly displays the tile selection list every time.
Other changes
No other changes in this release.