Component | Version |
|---|---|
NAO® Cloud | 25.06 |
NAO® Viewer | 25.06 |
NAO® SDK iOS | 25.06 - V4.12.1 |
NAO® SDK Android | 25.06 - V4.12.1 |
NAO® Logger iOS | 25.06 - V4.12.1 |
NAO® Logger Android | 25.06 - V4.12.1 |
Tooling to support the new Manufacturer-Direct Fulfillment process, allowing select customers and partners to order hardware from our manufacturers directly. Documentation is available here.
Fully integrated support for USB dongles deployment, with the addition of a new "Dongle configuration" menu under the existing "BLE listeners" menu.
Extended existing visual system: Device icons now consistently represent hardware family across all pages, providing clear hardware identification for planning and operational teams:
Beacons appear as square icons on every page
Listeners/gateways appear as round icons on every page
Dongles appear as triangle icons on every page
Smart Page Display:
Large, interactive icons show devices with functions relevant to the current page (beaconing devices on Beacons pages, listening devices on Listeners pages)
Small, non-interactive icons show other hardware present at the location for spatial context
Installation status continues to be indicated by color (blue for planned, green for installed)
Device brand (Aruba, Cisco, Pole Star) will now appear in the center of the large icons to help quick identification between the different hardware models
Limitation: If a listener/gateway is configured only for beaconing (e.g., a Cisco AP used exclusively for beaconing), it will appear as a beacon (square icon) on every page, reflecting its configured function rather than its hardware capabilities.
Advanced 3rd party infrastructure monitoring improvements (may be subject to a specific license):
High latency detection
iBeacon configuration mismatch detection (requires a dedicated monitoring infrastructure)
See here for details.
Removing tracked device that are in NAO Cloud logs now archives them instead of throwing an error. Archived tag are hidden by default, and unarchived if re-commissioned on the same NAO Cloud site.
NAO Cloud can now simulate a gateway sending a message through websocket just like a real gateway. The user can select the gateway, the tag and BLE frame. This helps verifying locations, and network centric push button alerts. This feature can be accessed via “Tracking dashboard” → Actions menu → Emulate listener reports.
Ekahau projects can now be imported on NAO Cloud directly to import maps and APs placement.
Maps are automatically imported with the right size / scale and aligned at the center of the site. We recommend checking/updating the georeferencing of the maps after import.
If APs are unknown in the database, they will be automatically imported with the following ADV ID: "iBeacon@504f4c45535441520000000000000450:#{site_id}:#{number}". This definition should be updated to match the reality after import.
Device tagging feature fixed
Fixed OTA configuration conflict display issue for beacon declared on multiple sites
Cisco IoT Orchestrator v1.1 support
3rs party hardware models can now be imported from a CSV file to facilitate custom setups. The CSV files must be requested from Pole Star.
Added an option to hide tags on the map whose location status is considered “offline” (no position reported).
Added an option to configure the period after which a tag is deemed “offline” (red dot in NAO Viewer).
This works in tandem with the previous option.
The default value remains 120 seconds.
Added an option to choose where the alert pops up on the map (9 positions, bottom-right by default).
Improved the option for alert display time (default 60 s).
This value can now be 0 to keep the alert permanent until the user closes it.
Improved the alert-sound option: it is now a selector with three values – no sound, play once, or play continuously.
Added an option to control how multiple alerts stack: they can overlap, stack one above another, or you can show only the most recent one.
When positioned at the top, stacking flows downward.
Added an option to trigger Windows notifications when the NAO Viewer browser tab is minimized, sending the same information via Windows toasts.
Note: Windows must allow notifications from the browser; the permission prompt appears when you enable the option in the config page.
Re-organized map-interaction settings into their own section on the configuration page: five independent options.
Improved the “lock to coordinates” behavior – scrolling is now locked to the center of the specified point.
Added an option to lock map rotation & scrolling (desktop & mobile).
Implemented clustering: tags that are close together aggregate into a circle showing the number of contained tags.
The cluster’s style (circle with number), merge distance, size, and scaling are all configurable.
Currently, clustering does not distinguish between tag types, properties, or any other parameters.
Battery level is now displayed on the Assets page, with a dedicated filter.
CSV export from the Location History page now includes all stored tag properties.
The tracking ID now appears on the Location page when you hover over a tag’s name in the info panel (when the tag is selected).
In the details panel for a selected tag, an icon can open that tag’s property page (or the global tag-property page if empty).
The button shows to the right of the property line only when the “see more” button is visible (i.e., at least one property type is hidden by default).
Tooling to support the new Manufacturer-Direct Fulfillment process, allowing select customers and partners to order hardware from our manufacturers directly.
Dongles and Listeners can now be installed with NAO Logger, matching the feature existing for beacons. They will be configured automatically during the installation, provided that a configuration is set.
iOS offline mode now works as expected.
Fixed an MQTT reconnexion logic bug when running NAO Logger in background while in Tracking mode.
In /monitoring MQTT topic, Status field filled for ACTIVE_GWS and ACTIVE_BNS existing messages.
ACTIVE_GWS: the Status is a list of latencies in seconds separated by comm
ACTIVE_BNS: the Status is a list of iBeacon configuration mismatch detection statuses separated by comma, -1 means no issue, 1 means iBeacon issue, 0 means did not check.
Examples:
{
"Type"=>"ACTIVE_GWS",
"Value"=>"AC233FC0092B,AC233FC02903",
"Timestamp"=>1749492348,
"Status"=>"17,1200", // list of corresponding latencies in seconds
"SiteID"=>12059
}
{
"Type"=>"ACTIVE_BNS",
"Value"=>"AC233FC0092B,AC233FC02903",
"Timestamp"=>1749492348,
"Status"=>"0,1", // first GW OK, second GW has iBeacon issue
"SiteID"=>12059
}A new “is_dongle” field is added when querying devices via the sites/{site_id}/ble_listeners and sites/{site_id}/beacons REST APIs.
A new “latency” field (in s) is added to the sites/{site_id}/ble_listeners response.
A new “ibeacon_issue” (boolean) is added to the sites/{site_id}/ble_listeners response.