• Updated the Payload Management main menu:
  • Reordered and modified menu items to improve design
  • Added a Logs menu item (Payload Management logs were previously under Status & Logs menu)
• Updated the following BACnet Device Settings:
  • Device Object Name: Increased from 25 to 128 Characters
  • Device Description: Increased from 64 to 128 Characters
  • Device Location: Increased from 64 to 128 Characters
• Made the following improvements to the Sensor Definitions page:
  • Moved the Sensor Definitions page under the Definitions and Templates menu item
  • Combined the Current, Default, Custom and Import pages
  • Added icons to identify custom and default sensor definitions
  • Added a Delete icon next to custom sensor definitions and a Delete All button to the Sensor Definitions page to remove all custom sensor definitions
  • Added an Add Sensor icon next to each sensor definition the system is currently using
  • Added an ? icon next to default sensor definitions replaced with custom sensor definitions, which also do not display the Add Sensor icon
  • Updated the Filter By field to filter by Source, Manufacturer, Sensor Type and Description
• Added an Import button to the Sensor Definitions page that opens a pop-up window
• Included the same fields as were previously on the Import page
• Combined the previous BACnet Objects and Managed Sensors menu items under Sensors
• Included pages for both Sensors and BACnet Objects under the Sensors menu item

Made the following improvements to the Sensors page:

• Included all previous functionality, with some improvements:
  • Sensors list with Device EUI, Source, Manufacturer, Type and Options columns
  • Filter by field to filter sensors by key data
  • Delete icon next to each sensor or Delete All option to remove all sensors
  • Download option to download a Sensors Map to a JSON file
  • Import option to import sensors from a JSON file
  • Add Sensor option to add a sensor manually
• Added Apply Template option to apply Sensor Type Templates to sensors
• Added an Edit icon under Options to view and edit sensor details

Made the following updates to the BACnet Objects page:

• Included all previous functionality, with some improvements:
  • BACnet Objects Map list with ID, Name, Property, Sensor ID and Options columns
  • Filter by field to filter BACnet Objects by Type, ID, Name, Sensor ID, or Property
  • Delete icon next to each BACnet Object or Delete All option to remove all BACnet Objects
  • Download option to download BACnet Objects Map to a JSON file
  • Import option to import BACnet Objects Map from a JSON file
  • Edit icon under Options to view and edit BACnet Object details
  • Add Object option to add a BACnet Object manually
• Added support for sensors with applied Sensor Type Templates

You create BACnet Objects for a particular sensor. This release allows you to see all BACnet Objects for a selected sensor in one screen.

Add BACnet Objects by either:

• Clicking Edit to update a sensor’s details on the Sensors page
• Clicking Add Object on the BACnet Objects page

For both options, the system opens a pop-up window where you choose a sensor by Device EUI. The system shows all BACnet Objects for the sensor with the selected Device EUI. You can then add, delete or edit the sensor’s corresponding BACnet Objects.

1. To add a BACnet Object, select or enter values in the following fields:
   • • Property
     • Type
     • Identifier
     • Name
     • Description (optional)
2. Click OK to create the BACnet Object
3. Update a BACnet Object by clicking the Edit icon for a property, either on the BACnet Objects Map page or in the Managed Sensor Details window

A sensor definition may contain uplink and downlink properties:

• The system recognizes a downlink property if the Downlink field is set to true.
• If the Downlink field is not present or set to false, the system considers the object an uplink.
• The BACnet Objects Map does not store information regarding uplinks or downlinks.
• The system uses the sensor definition file to distinguish uplink and downlink properties.

• Supported BACnet object types are different for uplink and downlink properties. The tables below list the supported objects types for each property type. 

Note: The first type in the list is the default one.

Implemented Sensor Type Template feature to:

• Simplify adding multiple LoRaWAN sensors of the same type to the system
• Add LoRaWAN devices of the same type to the Local Join Server (Local End-Device Credentials), the Managed Sensors list, and the same set of BACnet Objects for each sensor.

By default, there are no pre-defined templates in the system, so users must:

• Create new templates before using them.
• Specify the following data in the template:
  • Template Name
  • Sensor Definition
  • LoRa WAN Device Details:
    • Class
    • Device Profile
    • Network Profile
  • BACnet Objects

The system automatically:

• Adds ALL properties with a corresponding default Object Type to the BACnet Objects List when users select a sensor definition
  • This list changes if users choose another sensor definition
• Generates the BACnet Object Name
  • The name consists of PropertyName and BACnet Object Type abbreviation separated by a hyphen

1. To add a BACnet Object to the template, specify:
   • Property
   • Type
   • Name
2. Review the resulting BACnet Object Name, which includes the four last digits from the sensor Device EUI.

The system allows:

• Editing or deleting BACnet Objects added automatically
• Adding BACnet Objects manually
• Adding any number of BACnet objects to the template

The Apply Template option is:

• Available on the Sensors page
• Disabled if there are no Sensor Type Templates in the system

1. To apply a Sensor Type Template, choose a sensor type template from the drop-down list.
2. Specify the BACnet Object ID Start Value.
   • The system will increment the value for each new BACnet object added while applying the template.
   • If the ID was already used, the system skips it and applies another value.
3. Add sensor details manually (Device EUI, App EUI, and App Key) or upload data from a CSV file.
4. Click Submit.

• The system allows using a CSV file with or without a header:
  • If the CSV file does not have a header, you must add the sensor details in this order:
    • DevEUI
    • AppEUI
    • AppKey
  • If the CSV file has a header, the system will search for these values.
    • The system parses the file and retrieves only the values needed.

• When applying a Sensor Type Template to a specified list of sensors, the system makes the following changes:
  • Adds Local End-Device Credentials (LoRaWAN Network Server > Key Management page)
  • Adds sensors to the Manages Sensors list (Payload Management > Sensors page)
  • Adds a set of BACnet Objects for each sensor from the list
• The system adds Local End-Devices credentials only if you enable the Local Join Server.
  • The system does not add Local End-Devices and displays a warning message if:
    • You do not enable the Local Join Server
    • There is at least one sensor with a DevEUI that already exists in the Local End-Devices list
• The system adds sensors to the Managed Sensors list and:
  • Creates BACnet Objects even if it skips adding Local End-Devices
  • Uses the sensor definition specified in the template
• The system displays an error message and stops adding sensors and BACnet objects if there is at least one sensor with a DevEUI that already exists in the Managed Sensors list
  • Users can delete duplicated sensors and try adding them again
• After the system applies the template and creates the corresponding sensors and BACnet objects, there are no dependencies or connections between the created items and the template.
  • Users can change or delete templates without affecting the items created via the templates.