Versions

New Features

• NAO® SDK

  • New interface available – NAOSDK integrates a new callback, to notify the application when the SDK is unable to scan BLE measurements. See complete documentation: https://docs.nao-cloud.com/docs/ble-scan-callback-error/

  • Cybersecurity: NAOSDK will, by default, verify the server certificate. Impact:

    Server Configuration	NAOSDK Action	Use of NAOLogger
    SaaS	Default operation (no impact)	no change
    On-premises with p12	p12 certificate to be copied onto the phone	p12 certificate to be copied onto the phone
    On-premises	Use the new interface: ”allowInsecureConnections”	A new checkbox will be added in the settings menu to enable or disable this option

• NAO® Server

  • NAO Logger iOS is now available on-prem

Improvements

• NAO® SDK
  • Performance optimization for very large sites.
  • New React Plugin for Android & iOS available. See online documentation.

• NAO® Logger Android
  • Cybersecurity improvements
  • FOTA Mission Optimization: Improved robustness of the FOTA mission on NAO Logger to ensure firmware updates are applied to a tag regardless of the tag model or its current firmware version.
• NAO® Cloud
  • NAO BlueListener monitoring dashboard improvement: the status “Warning” is now available for Pole Star BlueListener with MQTT issues.
  • Return a success or error message after publishing a configuration on BLE Listener(s)

Bug Fixes

• NAO® Cloud

  • OTA mission workflow fixed: After applying an OTA mission on NAO Logger, the new configuration sometimes remained in the “pending config” status instead of being set as “last config,” causing the OTA mission to restart. This issue is now fixed.

• NAO® Server
  • Map Import Fix on NAO Cloud: Fixed a bug that occurred when importing a large map as an image, which led to scaling issues.

Other

• Now available:
  • NAO Track Legacy with push button: When the correct services and parameters are activated, the location can now be computed on demand.
  • NAO Track Legacy deployment with NAO Repeater: Reduce infrastructure cost for NAO Track Legacy using NAO Repeater.
    
  • Note: coordinate with a Pole Star Manager for any production implementation of this solution.
• Cybersecurity:
  • The default WebSocket token of NAO BleListeners will not be considered valid anymore on NAO Cloud. For future site deployments, you must add a new configuration on all Pole Star BleListeners. See the documentation on How To generate a WebSocket token for your NAO Cloud site

HotFix