Release Notes

v2.2.1

From now on the ARM template and the LoRaWan device provisioning CLI will be provided in the Starterkit releases
The infrastructure generation part has been fully updated to up-to-date services and product versions.

#1794: Application Insights is now requiring a connection string instead of instrumentation key. Make sure that, when updating to this version, the APPLICATIONINSIGHTS_CONNECTION_STRING is set instead of obsolete APPINSIGHTS_INSTRUMENTATIONKEY. More information on how to migrate from Application Insights instrumentation keys to connection strings on the official Azure documentation.

Increase scalability for multi-gateway scenarios. This eliminates several disadvantages in a multi-LNS deployment scenario. See ADR - 010. LNS sticky affinity over multiple sessions.
Standalone discovery service for dynamic LNS discovery. See ADR - 009. LoRaWAN Network Server (LNS) discovery.
LoRaBasicsStationModule updated to Basics Station v2.0.6:
- Support for SX1302 (configurable via "CORECELL" parameter)
- Adjustable log level (configurable via "LOG_LEVEL" parameter)

#1576: The default deduplication strategy is now "Drop" instead of "None". More information found in the decision record.

#1573: Handling ObjectDisposedException and other exceptions by recreating the DeviceClient.
#1564: Throttling disposal of DeviceClients.
#1540: Observe unobserved tasks.
#1462: Tracing of AMQP/MQTT dependencies to IoT Hub in Application Insights.
We enforce stricter naming conventions.
We change the way we make HTTP requests to conform with how to make HTTP requests using IHttpClientFactory in ASP.NET Core.
When using the quickstart template, we now deploy a Workspace-based Application Insights instance instead of a classic Application Insights.

Support for LoRa Basics™ Station LNS Protocol (v2.0.5)
Support for LoRa Basics™ Station CUPS Protocol (v2.0.5) for credential management and firmware upgrade
LoRaWAN Network Server and Basics™ Station can be decoupled, allowing the possibility to connect multiple concentrators on a single LoRaWAN Network Server instance
Support for running LNS on a separate Edge or Cloud device
Support for secure communication between LoRaWAN Network Server and Basics™ Station
Support for running LoRaWAN Network Server on Azure IoT Edge for Linux on Windows
Regional support for AS923 and CN470 (Regional Parameters v1.0.3rA and RP002-1.0.3 revisions)
Observability:
- Integration with Azure Monitor
- Exposing a Prometheus endpoint for metrics scraping
- Collection of metrics for edgeAgent and edgeHub modules with Metrics collector module

Introduction of LoRaWAN Primitives and refactoring of existing code to make wide use of those
Upgrade to .NET 6 (LTS version)
Upgrade container base images to Debian 11
Improvements in E2E CI, continuously testing multiple scenarios and authentication modes

Deprecated support for Packet Forwarder (upgrade instructions)
Upgrade to RaspberryPi OS based on Debian 11.0 Bullseye (upgrade instructions)
Infrastructure changes:
- New storage containers for CUPS credentials management and firmware upgrade (more in related ADRs)
- A Log Analytics workspace is required for integrating with metrics collector (more in related ADRs)
- Azure Functions runtime upgrade to v4

when updating from v2.0.0-alpha
- Certificate Validation: In addition to validating the thumbprint, it also validates that the chain of trust is correct. See instructions here

Release notes of all previous release can be found on the Release page on the repository:

Last update: 2022-11-08
Created: 2022-01-31