Iotedge Lorawan Starterkit Versions Save

Sample implementation of LoRaWAN components to connect LoRaWAN antenna gateway running IoT Edge directly with Azure IoT.

v2.2.2

6 months ago

New features

  • Update IoT Edge version
  • Decouple the IDevice interface from the Microsoft.Azure.Devices namespace

Bugfixes

  • Fix test device provisioning

Misc

Assets

  • LoRaWaN Network Server image: loraedge/lorawannetworksrvmodule:2.2.2
  • BasicsStation Module image: loraedge/lorabasicsstationmodule:2.2.2
  • Azure Functions zip file can be downloaded from section below
  • Discovery service zip file can be downloaded from section below
  • LoRaWan CLI provision tool can be downloaded from section below
  • Azure ARM template can be downloaded from section below

v2.2.1

1 year ago

New features

  • Class B Beaconing support (#1906)
  • AU915 frequency support (#1907)
  • Release workflow (#1942)

Bugfixes

  • Fix EU868 concentrator twin documentation (#1919)
  • Changed verbosity of the HTTP communication in logs (#1916)

Misc

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

Assets

  • LoRaWaN Network Server image: loraedge/lorawannetworksrvmodule:2.2.1
  • BasicsStation Module image: loraedge/lorabasicsstationmodule:2.2.1
  • Azure Functions zip file can be downloaded from section below
  • Discovery service zip file can be downloaded from section below
  • LoRaWan CLI provision tool can be downloaded from section below
  • Azure ARM template can be downloaded from section below

v2.2.0

1 year ago

New features

  • #1746: Running LoRaWAN Network Server decoupled from IoT Edge
  • #1780: arm64v8 support
  • #1807, #1810: AS923 Arduino examples and Documentation

Breaking Changes

Bugfixes

  • #1711: Remove unused DevEUI that breaks deserialization
  • #1728: Fix restart of the Basic Station Docker container
  • #1729: Don't use rx1droffset during join accept
  • #1776: Redis cache not properly updated because of IoT Hub query results delay
  • Various additional fixes covered in v2.1.0 <-> v2.2.0

Assets

LoRaWAN Network Server image: loraedge/lorawannetworksrvmodule:2.2.0 BasicsStation Module image: loraedge/lorabasicsstationmodule:2.2.0 Azure Functions zip file can be downloaded from section below Discovery service zip file can be downloaded from section below

v2.1.0

2 years ago

New Features

Breaking Changes

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

Quality Improvements

Bugfixes

Assets

v2.0.0

2 years ago

New Features

  • 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 LoRaWAN Network Server 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

Breaking changes

More information on breaking changes introduced with this release can be found in 'Release Notes'

Assets

v1.0.7

2 years ago

This is a minor release providing mostly bug fixes and correcting the dev workflow. For a more detailed view, please look at the

v1.0.6

2 years ago
  • This release fixes a number of bugs. We also upgrade IoT Edge to 1.2.2, as this is a new major iot edge version, some operation need to be done on the edge, please follow those instructions to upgrade to iot edge 1.2.x.
  • Release the beta version of the "universal decoder" that surface all decoders present on the ttn repo. This universal decoder is not yet included in the standard deployment, if you want to use it please follow instruction on this md file

Improvements

  • Upgrade IoT Edge to 1.2.2 (#290)
  • Add universal decoder supporting all TTN device decoders (#303)

Bug Fix

  • Revert faulty null Check (#280)
  • Fix invalid logs when joining (#260)
  • Fix occasional device disconnection (#292)
  • Fix Poisonous message causing network server to crash (#293)

v1.0.5

3 years ago

This release fix a bug on the Key Manager Azure function. Updates on the redis cache will be performed much more reliably after this update.

Improvements

  • Upgrade IoT Edge to 1.0.10 (#263)
  • Improvements in docs and guides (#254) (#261)

Bug Fix

  • Fix Azure function background worker bug (#259)
  • Improve logging (#260)
  • Fix a bug on Azure functions that sometimes prevented it to operate correctly following a deployment (#280)
  • Fix Error in cli tool bug due to package downgrade (#271)

v1.0.4

3 years ago

This minor release focus in improving the stack resiliency and upgrade dependencies to latest versions.

Improvements

Upgrade IoT Edge to 1.0.9.4 (#250) Upgrade All dependencies to .NET 3.1 (#240) (#248) Upgrade Microsoft.Azure.Devices to 1.21.0 (#240) Upgrade Microsoft.Azure.Devices.Client to 1.26.0 (#240)

Bug Fix

Fix Default RX2 frequency parsing that prevented frequencies other than US/EU to be implemented (#239)

v1.0.3

4 years ago

This minor release focus in improving the stack resiliency and upgrade dependencies to latest versions.

Improvements

  • Upgrade IoT Edge to 1.0.9
  • Upgrade Microsoft.Azure.Devices to 1.20.1
  • Upgrade Microsoft.Azure.Devices.Client to 1.25.0
  • Improve End to End tests resiliency

Bug Fix

  • Fix multigateway C2D scenario where second gateway would abandon message instead of simply dropping it