Versions

NAO Cloud

Improvements

• Georeferencing: You can now disable the default georeferencing edit mode. Click the “Edit” button to freely navigate the map without modifying its georeferencing. Click the button again to re-enable georeferencing edit mode.
  
  
  

New Features

• New messages on /monitoring MQTT topic: TAG_ON, TAG_OFF, TAG_CHARGING_ON, TAG_CHARGING_OFF or DUMMY_BUTTON_PRESS. Example:
  

{
'Timestamp': 1519815037,
'SiteID':221,
'Type': "TAG_ON or TAG_OFF or TAG_CHARGING_ON or TAG_CHARGING_OFF or DUMMY_BUTTON_PRESS";
'Value': "11:22:33:44:55:66"

• New advanced infrastructure monitoring features (dependent on the installation of dedicated monitoring tags/dongles across a site): beaconing/reporting status updated every 5 minutes, allowing the detection of a device malfunction within 10 minutes.

• Periodic location updates following a tag event are now identified with a dedicated “post_event_location_update” trigger, allowing integrators to distinguish them from the source event (e.g. button press).

NAO Server on prem

Improvements

• Simplified installation and update process

NAO SDK

New Features

• Advanced Remote Debugging: A feature that can be enabled by the application integrating the SDK, allowing remote activation of debugging tools such as log uploads, advanced log levels, GWL log initiation, and more

MQTT API changes

/monitoring topic

• New tags events (new message types: TAG_ON, TAG_OFF, TAG_CHARGING_ON, TAG_CHARGING_OFF, DUMMY_BUTTON_PRESS)

• Active beacons messages will be sent in addition to the active gateways messages (message type ACTIVE_BNS)
  Example:
  {'Timestamp': 1741018673, 'SiteID': 6261, 'Type': 'ACTIVE_GWS', 'Value': '70F096FF2B20,70F096C93A40,70F096C9C800,70F096C927C0,70F096C8BE80,70F096C92540,70F0969D92C0,70F096C951A0,70F096C94000,70F096A0EF80,70F096C8BC00,70F096A0F460,70F096C942C0,70F096C92600,70F096C906A0,70F096C941A0,70F0969D5540,70F096FB2720,70F096C942A0,70F096C93D40,70F096C8ED80,70F096FF00E0,70F096FA9FE0,70F096C8C5E0,70F096C94840'}
  {'Timestamp': 1741018673, 'SiteID': 6261, 'Type': 'ACTIVE_BNS', 'Value': '70F096C8A400,70F096C942A0,70F096C941A0,70F096FAB000,70F096FA9FE0,70F096C93FE0,70F096C942C0,70F096C94240,70F0969D45A0,70F096C93A40,70F096C93D40'}

• Active beacons/gateways messages will now be sent every 5 minutes instead of 10 minutes

/locs and /alerts topics

• New event_id field in push button events, to help identify seed event if post-button press follow up location updates are configured.
  Example:

• {
  'tag_id': 2049,
  'site_id': 123,
  'lon': 1.3874217173837997,
  'lat': 43.56428367165108,
  'alt': 10.0,
  'loc_uncertainty': 1.0,
  'loc_updated_at': 1522856593000,
  'duration': 0,
  'zone_ids': [124],
  'event_id': 1,
  'trigger': 'button_pressed'
  }

• New post_event_loc_update trigger for post-button press follow up location updates
  Example:

  {
  'tag_id': 2049,
  'site_id': 123,
  'lon': 1.3874217173837997,
  'lat': 43.56428367165108,
  'alt': 10.0,
  'loc_uncertainty': 1.0,
  'loc_updated_at': 1522856603000,
  'duration': 0,
  'zone_ids': [124],
  'event_id': 1,
  'trigger': 'post_event_loc_update'
  }

• A location update can be received with the dummy_button_pressed trigger when a DUMMY_BUTTON_PRESS event is received

REST API changes

• New configurations field in /sites/{site_id}/nao_trackables resource, allowing to get the latest applied OTA configuration

  • Example:

    "configurations": {
                        "id": 939,
                        "name": "B10 F2.2"
                    }

• New fields in /sites/{site_id}/ble_listeners resource:

  • last_beacon_at: Last time the device was heard as a beacon, updated every 5 minutes.
    Example: "last_beacon_at": "2025-02-27T22:52:53.000Z"

  • last_report_at: Last time a scan report was received from the device, updated every 5 minutes.
    Example: "last_report_at": "2025-02-27T22:57:53.000Z"