Information on key features and changes made to the Portal are found here. Preliminary release notes, when listed, are for features and changes planned for the next release.
August 2022 - Release Notes
- Updated Application Notifier Create/Edit controls to only allow modification by Admin users.
- Added the ability to include an Application's EUI in its associated Notifiers messages.
- Improved behavior of the Device Profile Channel Mask editor.
- Added support for generating a Registration Token from the Applications table.
- Added support for editing parameters associated with an Application's configuration.
- Updated Registration Token Expiration Alerts to no longer evaluate for short-lived Tokens.
- Addressed an issue displaying public Join Server names in the Application dropdown selector.
- Addressed an issue where Device Transfer results did not correctly reflect errors that occurred.
- Updated the Developer Portal to allow Device Registration with a Join EUI of "0000000000000000".
- Enhanced Device Event Details content for both Multicast Application and LoRaWAN MAC Command responses to indicate ACK or NACK.
- Addressed an issue where Multicast group configuration was attempted after being NACKed by a Device.
- Improved clarity of Multicast API results when adding Devices to groups and deleting groups.
- Addressed an issue for ADR-disabled Devices joining the Network in regions with dynamic channel plans that employ the CFList (e.g., EU, AS, or India).
- Added support for Cote d'Ivoire Channel Plan 868.1 - 869.5 .
- Addressed an issue where a Device's Profile assignment was reset to defaults.
- Addressed an issue where Device Events did not display the names of some Base Stations.
- Addressed an issue where the IN865 Channel Plan was not allowed for the Tektelic Macro Base Station.
June 2022 - Release Notes
- Updated the Device Events view to maintain row selection when scrolling horizontally.
- Added support for editing an Application's Description.
- Added a new UI workflow to transfer Devices between Customer accounts. Requirements include API keys associated with both the source and destination Applications as well as a common Join Server.
- Added the ability to onboard Devices using Senet's pre-defined Public Join Servers. Additionally, the control's layout and filtering capability were improved.
- Improved the Device Update workflow to allow appKey and nwkKey changes for Devices that have never joined the Network.
- Updated the Map's Device Statistics header to allow toggling visibility of groups of Device markers by clicking individual legend-labels of the active statistic chart.
- Addressed an issue where some Join Errors were not displayed in the Base Station Details Events view.
- Updated the Device Profile create/edit dialog with an improved control for editing channel masks.
- Updated the Device Profile's 'Deduplication Delay' setting to be derived as a percentage of the Profile's 'RX1 Delay' setting. This will improve downlink success for devices heard by Base Stations with longer round-trip times (RTT), requiring a non-default RX1 Delay.
- Updated the Device Registration workflow to accept custom Join Server and Application Key data by default.
- Updated the Device Edit dialog to allow overriding a non-default Device Profile.
- Addressed an issue where the Location link in Device Details Info Panel did not open the Map view.
April 2022 - Release Notes
- Added Device Type, Location, and Join Server EUI fields to the Device Details information panel.
- Updated the Device Management Join Server menu selection to include Server names.
- Added Application and Join Server EUI confirmation fields to the Device onboarding dialog to ensure devices are correctly registered.
- Updated the Device Onboarding process to allow duplicate Application Keys. Included a warning indicating non-unique keys are a security issue.
- Updated the Device Onboarding process to prevent duplicate Device Registrations.
- Added support for Device Profiles, which allow customization and management of a Device's LoRaWAN settings.
- Addressed an issue where the Application Dashboard could show data for the incorrect time range.
- Addressed an issue with the Application Dashboard where the displayed data did not always align with the timeframe selected.
- Updated the Device Management API to require that a Device be Deactivated before changing its Contract.
- Updated the Device Management API to prevent a Deactivated Device from being Deactivated again.
- Addressed an export issue with Planning Maps.
- Updated the FUOTA engine to use non-zero Multicast Group IDs to support Devices participating in multiple groups.
- Updated Downlink behavior to fail immediately when a requested Downlink PDU exceeds LoRaWAN specifications.
- Addressed an issue where FUOTA session timeout was not correctly calculated.
- Updated the FUOTA engine to accommodate Devices that do not support the Application Layer Clock Synchronization specification.
- Updated views throughout the application to include URL parameters, allowing for easy sharing of links to specific views.
- Added context-sensitive browser tab titles for easier browser tab management.
- Updated Device Edit workflow to provide an optional Device Profile configuration, allowing customization of LoRaWAN settings.
February 2022 - Release Notes
- Updated Device Tag Management to allow multiple tags to be deleted.
- Addressed an issue where tags could not be removed from a Device.
- Updated the Device Transactions view to hide the Application Payload field when the data is encrypted.
- Added support for Dynamic Multicast Groups for Devices that support the LoRa Alliance TS005: Remote Multicast Group V1.0 & V2.0 Specifications.
- Added support for the LoRa Alliance Backend Interface Specification version 1.1.
- Updated the Unique Uplink filters in Device LoRa Event views to exclude retransmitted events.
- Addressed an issue where late uplinks cause a suboptimal Gateway to be used for downlinks.
- Addressed an issue with deleting Devices.
November 2021 - Release Notes
- Updated the Application Dashboard to display statistics by Contract for Uplinks, Downlinks, Join Success, and Join Errors.
- Added the ability to optionally forward Layer-2 Uplinks to an Application Provider.
- Updated the Usage Files View in Application Details to always be visible.
- Updated the MQTT Notifier configuration to allow for a Broker Address length up to 255 characters.
- Updated Notifier payload to include the ‘ismBand’ and ‘maxPayload’ fields as part of the ‘RF Data’ option.
- Updated AWS API Gateway Notifier support to include all data fields available to HTTP Notifiers.
- Enhanced FUOTA support to parse and display downlinked commands from the Firmware Management, Multi Package, Application Clock Sync, Fragmented Data Block Transport, and Remote Multicast packages.
- Added FUOTA support for LoRaWAN v1.1 devices.
- Added FUOTA support for external handling of Firmware Management package.
- Added support for AS923-4 Region.
- Added support for the LoRaWAN v1.1 MAC commands: ResetInd, ResetConf, RekeyInd, and RekeyConf.
- Addressed an issue where new Security Session Keys were not used to encrypt Application payload for downlinks queued during the previous session.
August 2021 - Release Notes
- Added a selector to the Device Search boxes that scopes the search to the selected column.
- Enhanced Senet's LoRa Network Server FUOTA capabilities to allow Application Providers to set the fragment size limit for a firmware update.
- Updated the Device Delete workflow to allow Developers to delete a Device regardless of the Device's state.
- Added support for user-specified Device Types.
June 2021 - Release Notes
- Updated the 'Application Provider - Contracts View' user role to include the Application Usage view.
- Added a Join Server Details view to display Devices and Events associated with a Join Server.
- Updated the Date/Time control for event tables to support retrieving events either older or newer than the date/time specified.
- Addressed an issue where displaying events for Devices with extended periods of inactivity was incomplete.
- Added Auto Approval of Gateways running the Semtech Packet Forwarder or Basic Station software.
- Updated the Gateway Registration workflow to allow manufacturer EUIs to be used.
May 2021 - Release Notes
- Updated Application Usage Statistics views to display stacked column charts for selected Contracts.
- Updated the Application Usage Statistics views to render data with the correct timezone.
- Updated Northbound API to optionally include the Base Station receive time of an uplink.
- Updated the Devices with Notifiers table to control Diagnostic Mode and edit Notifiers for Devices in Diagnostic Mode.
- Improved Device Events table by disabling auto-refresh when the view is scrolled.
- Updated Device Management workflows to support Devices associated with an external Join Server.
- Improved the usability of the Configuration History view by adding filtering capabilities and improving the naming conventions used.
- Added support for creating and managing Custom Layers for Maps.
- Updated Senet's LNS to support Semtech's LoRa Cloud Join Server.
- Addressed an issue where the Network Server did not consistently manage Devices updating their own ADR state.
- Addressed an issue where Join Error System Events were not displayed in the Base Station System Events view.
February 2021 - Release Notes
- Updated Registration Token email to include remaining usage and expiration information.
- Updated the Device Event and Transaction views to include a filter for Unique Uplinks/Downlinks.
- Updated the Device Management API to support the transfer of Devices between accounts.
- Added support for managing lifetime and use-count settings of Device Registration Tokens.
- Updated Path Quality calculation to allow overrides of Base Station height and radius as well as Device height.
- Updated Planning Maps export feature to include the Path Quality, distance, height, and azimuth of the top 3 Base Stations used for Path Quality calculation.
- Added Coverage Layer that displays Network coverage estimates for a given area.
- Updated Path Quality calculation to allow for filtering by Base Station Classification.
- Added Configuration History view for auditing change events.
- Added Swagger documentation for integration APIs.
- Added a workflow to Maps for measuring distance.
December 2020 - Release Notes
- Added support for filtering Devices included in Service Metrics view by Last Heard time.
- Added support for multiple API Keys. API Keys can be generated to support specific functional areas, allowing granular control over access granted.
- Updated Information and Settings for Devices to allow a custom Device Type to be specified.
- Added Duplicate Uplinks count to both heatmap tooltips and table view for the Device RF Statistics.
- Addressed an issue where updates to the Metadata field were not handled properly.
- Added new administrative view for managing API Keys.
- Added support for changing image opacity for Coverage Maps and Custom Layers.
- Added the ability for Developers to configure Firmware Version, Tags, and Metadata fields for their devices.
Application Providers and Developers
- Updated HTTP and MQTT Notifiers to allow forwarding of Firmware Version and Profile Name
October 2020 - Release Notes
- Added a new 'Application Provider - Contracts View' Role that delegates access to Devices scoped by contract. This view provides read-only access for viewing Device performance and troubleshooting Device connectivity.
- Added new API which allows customers to export Application Usage Data.
- Updated the Device export API to allow the user to specify Devices to export.
- Updated Device Maps to display partial results when the Device display limit is exceeded.
- Added new presentation option to allow combining charts in the Operational and Onboarding Summary views.
- Added the ability to configure the Notifier for an Application. An Application Notifier defines the protocol, options, and fields to include when streaming data to a Northbound Endpoint.
- Added support for selecting the time period used when displaying Device Service Metric statistics.
- Updated the Application Details view to include LoRa events for all Devices associated with an Application.
Developers & Application Providers
- Updated HTTP and MQTT Notifiers to allow control over which data fields are included
- Updated all LoRa Events tables to identify late uplinks by presenting their timestamps with italicized lighter text.
- Added the ability to initiate the FUOTA process to Class C devices.
- Added the ability to initiate the FUOTA process to Class B devices.
August 2020 - Release Notes
- Added a new chart to the Device Statistics view for Join activity.
- Added Service Metrics to help characterize Device performance over time. These measure Device activity against 1-, 2-, and 3 day periods with respect to the past 31 days.
- The data is presented in the Map view, on a new tab of the Device Statistics header.
- It can be exported from the Devices Table under Application Details or by using the associated API.
- Updated Notifier payloads to optionally include Device-Type (devType) when available.
- Addressed an issue where downlinks could not be queued via MQTT if the Device's EUI was not normalized.
- Addressed an issue where the Devices Table was either slow or failed to retrieve data.
- Added user management view for managing users within a Customers account.
- Introduced initial support for the LoRaWAN FUOTA 2.0 specification.
- Updated the Base Station create/edit dialog with a control to indicate the requirement of dwell time restrictions.
- Added support for CFList Type 255, allowing Device Join EUI reconfiguration as part of the Join Procedure.
- Corrected an issue where late Join Requests were processed as DevNonce replay events.
- Corrected an issue where uplinks with sequence number 0 were occasionally processed as retransmits.
June 2020 - Release Notes
- Updated all Map views to allow toggling the display of road and point of interest labels.
- Added support for the LoRaWAN FUOTA Specification v2.0.
- Corrected Beacon format to comply with the LoRaWAN 1.0.4 specification.
- Added a channel mask override to Base Station configuration settings to mitigate downlink channel interference while maintaining reception on all available channels.
- Addressed a sorting issue with the PSR, Avg SNR and Avg RSSI columns in the Devices table.
May 2020 - Release Notes
- Enhanced Map support to include access to Custom Layers.
- Improved Devices and Application Devices table export compatibility with Excel. Dates and numbers are automatically recognized as the correct type for sorting.
- Added the ability to filter Devices on a Map by Tag, Application, and Contract.
Addressed an issue where Tag values could not be removed via Device Update.
Added Summary Statistics header to Planning Maps. This header displays number of Planning Entries in a map and the Path Quality distribution.
- Added support for AS923-2 and AS923-3 regional variants.
- Improved the readability of the CFList information in the JoinAccept event.
- Enhanced ADR Engine to support using a subset of channels for a Base Station impacted by local interference.
March 2020 - Release Notes
- Added a new Application Alert that notifies an Application Provider when their Device Management Registration token is about to expire. By default, this Alert will be raised two weeks before the configured expiration date.
- Added the ability to view a Device's Path Quality from the Map.
- Added the ability to create and view Planning Maps allowing users to preview coverage and plan upcoming deployments.
- Added the ability to specify the Client Certificate for MQTT connections.
- Updated the Device Registration workflow to ensure imported files contain unique Application Keys and Device EUIs.
- Addressed an issue where dwell time could not be disabled on an AS923 device.
- Added LoRaWAN version 1.0.4 support.
- Enhanced the LoRa Engine to both temper resending unanswered MAC commands as well as prevent resending NACK'd MAC commands.
- Updated the LoRa Engine to deprecate the frame count gap limit (MAX_FCNT_GAP).
- Addressed an issue where immediate class A downlinks were not getting sent on RX1 even though there was enough time to send the downlink.
- Improved confirmed downlink traceability by allowing only one confirmed Class-B or Class-C downlink to be queued for all devices whose LoRaWAN version is lower than 1.1.x.
- Added the ability for Developers to reset a Gateway's registration, allowing them to resolve common on-boarding issues.
- Added new ‘Show Map’ feature to the Application Devices Table. Selecting 'Show Map' will insert a map below the table and display pins for devices with location data. Device row-selection will auto-center the map and animate the device pin in context.
- Updated the Map Information Dialog to show the estimated location of a Device when its actual location is unavailable.
- Added support for filtering the Application Devices Table based on current row-selection. The URL is updated with the list of selected Device EUIs, allowing for bookmarking.
- Updated the Device Management API and UI to ignore invalid latitude and longitude values.
- Updated the quick information popup in the Devices Table to include Tags and Metadata information.
- Improved the Device Update API to better validate data and return user-friendly errors to help troubleshoot issues.
- Added support for The Things Network's Join Servers. Devices registered within TTN's platform can seamlessly operate under Senet's Network.
- Addressed an issue where Class-A downlinks were not properly delivered to Semtech Packet Forwarders and Basic Stations.
- Added Planning Map support for Proposed Viewsheds with a radius of less than one mile.
- Added support for scoping Application Details views by Contract. Views include Devices, Device Management, and Usage Data. Note: Aggregated data will only be displayed for transactions occurring after this feature release.
- Added support for a new Device Metadata field. This new field allows for storage of custom information about specific Devices (e.g. serial number).
- Added access to Application Usage data via a file download. These files contain detailed usage information for each device and Contract.
- Added new table view which displays aggregate RF Statistics by channel.
- Added support for viewing Device Transactions for all devices without requiring Diagnostics be enabled. Note: This view is intended for troubleshooting recent device activity and should not be considered a complete transaction history.
- Added a Device Management Events view for Applications allowing users to view related audit events.
- Updated the Device Export API to include devices' assigned Device Profile ID.
- Updated the Application Details Dashboard charts to automatically synchronize zoom-level. This allows viewing the same time frame for all charts by changing the zoom-level for one.
- Improved the Device Update workflow to also update devices that have not yet joined the network.
- Updated the Device Export API to support filtering by Contract ID and added a new column for yesterday's Base Station EUIs.
- Added color-coded icons to the RSSI and SNR columns of the Events Table to better visualize signal strength and quality.
- Updated the classification of SNR and RSSI values. SNR values below -13 and RSSI values below -125 are now considered poor (red).
- Addressed an issue where the search/filter was not applied when exporting devices from a table.
- Updated Device Management API to allow contract assignment when Deactivating devices.
- Added support for additional fields in the device map information dialog. It now shows contract, application, tags, and metadata on top of the existing data. There is also the addition of links to the devices location in Google and Bing maps.
- Added support for LoRaWAN Class-B FUOTA.
- Added support for Join-Accept Type-1 CFLists in US915 and AU915.
- Added FUOTA support for RX2 frequencies in EU868, IN865 and AS923.
- Improved the handling of Devices with poor downlink reception by alternating between RX1 and RX2 when responding to uplinks with ADRACKReq set.
- Updated FUOTA support to include STMicro’s Class-B FUOTA implementation.
- Corrected an issue with Class-C downlinks through Semtech’s Packet Forwarder.
- Improved the handling of Devices with poor downlink reception (e.g. ADRACKReq is set) by optimizing the LinkADRReq parameters delivered in subsequent downlinks.
- Addressed a downlink processing error for devices that have not uplinked.
- Addressed an issue where the Gateway Time field of the Join-Accept event reflected the Processed Time instead of the actual Transmit Time.
- Removed a deprecated channel for IN865 from display in the FUOTA dialog.
- Addressed an issue with the background style of the Dashboard.
- Added support for daily aggregated data in the Device Details RF Statistics view. This provides greater visibility into daily trends for Uplinks, SNR and RSSI statistics.
- Added Support for a Device export API.
- Added support for User Accounts with read-only access for Application Providers.
- Increased the Map's Device export capacity to a maximum of 10K Devices.
- Updated Device deactivation workflow to optionally allow assigning a contract.
- Addressed an issue with restoring the Application Device Management and Alert views after reloading the browser.
- Addressed an export issue that occurred when the Device Management Table was sorted.
- Added support for clearing the device downlink queue when enqueuing a new downlink.
- Addressed an issue where PSR would occasionally calculate to 0 for devices located on the edge of service.
All Portal Users
- External access to web-services has been restricted to SenRa's public API.
- Added an Alert Statistics view for Applications.
- Added Northbound support for ActiveMQ Artemis using MQTT.
- Updated Join failure events to include the Join EUI and the registration state of the device.
- Improved data export performance from the Devices table.
- Added failed Join attempt events to the Application's Events view.
- Updated the Application's Devices table to display firmware information.
- Addressed an issue where the Devices with Notifiers table did not sort properly.
- Addressed an issue where devices for an Application could not be viewed and exported correctly.
- Addressed an issue where queued Downlinks could be lost during an MQTT Server fail-over.
- Addressed an issue where the Device Events table did not properly filter Application Downlinks.
- Updated the Developer Portal to ensure deleting a device removes only registration data.
- Addressed an issue with the AS923 maximum downlink packet size calculation.
- Enhanced protection against late-arriving Join Requests, which may occur when a Base Station temporarily loses connectivity and queues receptions.
- Added a new Device Profile setting, LoRa Device Class, that determines the default method for sending downlinks. This simplifies deploying Production Class-C Applications.
- Added Notifier connection errors to the system events table within the Application Details view. These new events aid in troubleshooting northbound interface issues with Application Providers.
Developers and Application Providers
- Corrected an issue where the FPort used for Downlinks was not consistently shown in the events table.
- Improved the error message presented in the event a downlink message cannot be processed.
- Fixed an issue where Portal Device registration was allowed using the EUI of a Device that was already registered.
- The Device Management API now supports a method for activating a single device.
- The Device Management APIs now supports a callback URL for obtaining the results of a bulk operation.
- Devices which have been Activated but have not Joined now support having their properties updated.
- Device Profiles for Devices can now be edited through the "Update Devices" window and API.
- Device Types for Devices can now be provisioned during the Device Registration and Activation process and edited through the "Update Devices" window and API.
Device Maps now support displaying all Devices regardless of last heard time. This feature is accessed from the Device Statistics panel.
- Application Notifiers can now be configured to operate asynchronously. Application Notifiers configured this way will have increased throughput by allowing for multiple simultaneous connections to an Application Provider's end-point.
- Application Notifiers with Batching Support are now configurable with custom batch sizes and intervals.
- Map display attributes like location, zoom level, and layer configuration are now encoded in the browser URL. This allows for easy sharing of maps.
- The Device RF Heatmap views now supports time navigation controls to allow troubleshooting historical events. This control allows traversal of the historical RF data in 1 hour, 6 hour or 1 day increments.
- Device activation performance has been improved by optimizing data integrity checks during processing local application servers.
- Several FUOTA enhancements were implemented including support for EU868 End Devices, UI improvements, and generation of audit events for tracking the FUOTA process.
- The Northbound API now supports the ackDnMsgId field. When present, it indicates a device has acknowledged a specific downlink message ID.
The LoRa engine has been enhanced for users to indicate how the Network Server should send on-demand application downlinks, based on the operational class of the target device. When operating as Class-B or Class-C, the Device's Details > Send Downlink UI will display a Device Class selector. Downlink options include:
- Class-A: Queue the downlink until the next uplink's receive windows are available
- Class-B: Do not queue; send the downlink to the elected base station for transmit on the available next ping slot
- Class-C: Do not queue; transmit immediately.
- Added status events for downlink transmit activity reported by Gateways to improve message traceability.
- Enhanced FUOTA support by adding compatibility with additional end-device stack implementations as well as compliance with EU ISM Duty-Cycle requirements.
- Added a new Security Session event type to the Device Details transactions and events tables. This event indicates a device has processed a Join Accept, derived new session keys, and subsequently uplinked. The event's SeqNo identifies the first uplink received after the Join Accept was sent.
- Application Providers can now see a list of the Device Profiles used by their Devices.
- The Device Profile table can now be viewed in Application Details.
- Added the ability to append, replace or delete Device tags from the Device update UI (using a csv file) and the Device update API (using JSON).
- Added notifier support for the IBM Watson Scalable Application platform.
- Improved the PSR algorithm to better account for devices with an infrequent uplink interval.
- A new REST API was added for sending multicast downlink messages to multiple Base Stations.
- Enhanced the LoRa engine to comply with the FUOTA Interoperability Test suite from Stackforce and Arm Mbed.
- The Device Details view now includes uplink channel utilization heat maps displaying RF Statistics over time.
Application Providers and Developers
- The Map view now provides the ability to visualize a device's predicted Path Quality by drawing vectors to Base Stations providing coverage.
- Device Registration and Activation workflows now support device location and tags.
- The Application Details view now includes a table displaying available contracts.
- The Application Details view now includes the number of devices in the Activated and Registered states.
- Improved the Network Server's handling of uplink re-transmissions.
- Fixed an issue where downlinks to Class-B and -C devices were occasionally scheduled for the same transmit time.
- Fixed an issue where Tags could not be added to Devices.
- The Alert Details views have been redesigned for clarity and consistency.
- The Device Details view is now available for any device across all associated Applications, and the requirement of diagnostics mode to view Device Statistics was removed.
- The Device Profile that governs how the Network Server manages end devices can be assigned as part of the Device registration and activation workflows.
- An Alerts view was added providing visibility of Alerts for Applications.
- Improved usability of Maps with small visual cues: yellow caution icon decorations indicate a data layer is not available to display, while the refresh button wiggles when that action is required to display all available data.
- Device registration for OTAA and ABP now allows users to enter custom application, join server and session keys. This provides greater flexibility for developers whose devices have different network configurations.
- The 'Copy to Clipboard' buttons found in Device dialogs now support the short form Hex and long form Binary Array data formats.
- The Device Details LoRa event tables (Transactions, GPS, Sensor and Events) now persist the expanded/collapsed state of expandable columns.
- Improved handling of downlinks cached by MQTT brokers.
- Corrected an issue where the gateway elected to downlink was occasionally not the optimal candidate based on RF data from the corresponding uplink.
- The LoRa event table now supports a quick filter option. Events can be filtered by: Unique Uplinks, Join Activity, Application Downlinks and ADR Activity
- The Devices table now includes columns to show the application EUI and the last heard from time.
- Device Map Support - A Map view was added which allows Application Providers to manage and visualize devices on a Map.
- Device Grouping Support - Application Providers can now use tags to qualify, group, and filter rows in the Devices table view for all their applications.
- Device Grouping and Location information can now be updated through a CSV import and a REST API using JSON.
- Northbound Interface - Health statistics for the last 7 and 31 days are now available in the Application Details panel.
- Northbound Interface - Azure Event Hub integration using HTTPs is now supported.
- The Streaming API now includes the LoRaWAN Class designation ("A", "B", "C") of the source device in the JSON payload.
- Support was added for Tektelic’s KONA series microcell gateways.
- The device transactions and gateway events tables have been enhanced to include a quick summary window. The window can be displayed by pressing the "i" icon next to the EUI.
- The downlink message queue for a device will be cleared when it is deactivated.
- Northbound API now includes estimated latitude and longitude of devices based on the number and location of gateways receiving their uplinks.
- Notifiers now support including the ACK bit setting from uplinks' frame header, allowing remote applications to verify downlink success.
- Improved presentation of uplinks received in response to confirmed downlinks: the event details of only the first uplink processed will reflect the acknowledged downlink sequence number.
- The join type (OTAA/ABP) of a device is now displayed in the Devices table. The "Join Type" column is hidden by default.
- The Encrypted PDU, App Payload, and Details columns in the Device Details Transactions table may now be expanded and collapsed by clicking an icon in the column header.
- The device registration workflow now allows assignment of configuration profiles, allowing devices to benefit from optimizations encapsulated by the profile immediately after joining the network.
- Profile based ADR management now includes controls over how responsive the Network Server is to changes detected in device behavior. It can be stringent, flexible, or a combination of both. This change allows the Network Server to continually adapt to changing deployment conditions in order to optimize packet and data success.
- The Network Server will now use device uplink data to substantiate equal or better coverage from macro-cell gateways before transitioning devices to expanded channel plans. This prevents negative outcomes by expanding channel plans too quickly when coverage changes.
- Customers may now clear downlinks in-queue with the updated API, improving the level of control in managing devices.
- The Device Details in Portal now shows the encrypted app payload if the decrypted app payload is not available.
- Device registration is now secured with two factor authentication. A user must supply a token emailed to their registered address to complete the action.
- Updated the LoRa engine to support the latest default Rx2-Window parameters for the India ISM Band 865-867MHz.
- SenRa's LoRa Engine has been enhanced to support additional application deployment models. This allows both a single Join-EUI to be associated to different applications, or a single application to be serviced by any number of Join-EUIs.
- Device Details view now includes Security Sessions counter: the number of times a device has successfully joined the network today.
- Corrected an issue where DataRate was not displayed correctly in the Device Transactions table.
- The MQTT Notifier now supports authentication and encryption.
- Corrected an issue with the MQTT Notifier where downlink messages occasionally failed.
- Minor fixes and improvements made to the Portal UI, including search responsiveness, device detail information and charts presentation.
- Improved handling and feedback of TCP Socket Notifiers that are misconfigured or experience connection errors.
- Added support for G+D Mobile Security’s Key Management System (KMS) platform.
- Improved integration with the Yodiwo IoT platform.
- All events are now recorded using the Network Server's time. In previous releases, gateway time was used for events sourced from gateways.
- Corrected an MQTT notifier issue which could cause client connections to be leaked.
- Manual-refresh of Device events and transactions tables no longer causes duplicate rows, and the tables' view-port is maintained on actively selected rows - otherwise it will focus on new entries added by auto-refresh.
- Corrected an issue where more than one email was sent for disabled Notification Targets.
- Improved the presentation and readability of a Device’s channel plan in the Device Details panel.
- Added support for LoRa Class C downlinks
- Corrected an issue where more than one email was sent for disabled Notification Targets.
- Tables now export data in Excel format to improve opening in that application.
- Gateway Details view was added to the Portal which displays summarized event, device, and transaction data.
- Improved initial Portal application load time.
- Data Streaming - Yodiwo IoT platform now supported.
- An e-mail is now sent to a user when a Notification Target has been disabled.
- Device Details Send Downlink PDU interface now supports the correct maximum timeout.
- Device Details view navigation was improved on the mobile version of the Portal.
- The fPort value contained in the Device Details Pending Downlink message now displays correctly.
- Device Details panel includes the LoRa NetID for ABP device.
- Gateway registration panel now blocks attempts to repeatedly click register button.
- Device Downlink panel now supports custom FPort values.
- GPS Map view now properly renders SNR of -1.
- GPS Location fields are now displayed in consistent order (latitude/longitude).
- GPS Map properly resizes to window dimensions.
- Gateway registration now validates latitude and longitude.
May 2017 Rel. 2
- Added support for LoRa Activation By Personalization (ABP)
- Added support for Elsys devices
- Improved presentation of Application EUI and Key in the Edit Device dialog
- Standardized the placement of Map element information
- Packet Success Rate (PSR) now shown as “N/A” for devices whose uplink interval cannot be determined
- Several improvements to mobile version of the site, specifically for use in landscape mode
- Data Streaming - Support for Senet’s Packet Format is correctly reflected in the Edit Device dialog
- Data Streaming - PubNub and Microsoft Azure IoT notification targets can now be configured correctly
- GPS-based data points now display the correct data and may be filtered from view by Gateway
May 2017 Rel. 1
- Significant improvement made to event table performance: load times reduced to 1/10th for large tables.
- Events tables are now searchable.
- LoRa Frame control and MAC Command information are now displayed in event tables.
- RSSI and SNR values are now properly displayed for Join Request events.
- RSSI values are now adjusted to account for negative SNR values.
- Improved display of panels in landscape mode on Mobile.
- Improved scrolling behavior on Mobile.
- Improved performance of UI when changing Dashboard settings.
- GPS map is now properly sized to panel area.
- Gateway operational status now updates after registration.
- Data Streaming - decoded fields are now sent for all Senet Packet formats.
- Added support for Arduino Gateways.
- Added support for GlobalSat LT-100 tracker.
- Added support for Ascoel motion detector and door switches.
- Improved format of Application Keys and Application EUI used for configuring device.
- Devices not heard from in a month or more are displayed in light gray.
- Gateway description is now editable.
- Device and Gateway tables now support multi-row delete.
- Devices not accounted for in the Type list can now be qualified as "Other" Type.
- Users can now register any gateway preloaded with SenRa's software by using the new ‘Generic 8 Channel Gateway’ Type.
- Sequence number displayed in Sensor data panel is now correct.
- SNR and RSSI values are now properly rendered.
- The correct Application EUI is now displayed when registering Application Provider devices.
- Mobile - Improved navigation & rendering for both iOS and Android.
- Mobile - Tables now support horizontal scrolling.
- Mobile - Account management is now available.
- Data Streaming - Updated MyDevices integration to include Senet Packet data when available.
- Data Streaming - Updated ThingSpeak integration to always include LoRa application payload.