We recommend re-deploying your solution based on the 1.0.1 release if you have been working with a pre-release version. If you prefer to update your existing installation, the following lists describes the required steps.
Go to your solution's Azure IoT Hub and under IoT Edge, select eacu of your gateways. Select Set Modules and configure the two deployment modules LoRaWanNetworkSrvModule and LoRaWanPktFwdModule. Make sure, the following image URIs are configured:
| Deployment Module | Image URI |
|---|---|
| LoRaWanNetworkSrvModule | loraedge/lorawannetworksrvmodule:1.0.1 |
| LoRaWanPktFwdModule | loraedge/lorawanpktfwdmodule:1.0.1 |
If you have manually deployed the Azure Function, re-deploy the updated version of the Azure Function Facade as outlined here if you have a previous version of this Azure Function running.
If you have deployed the solution and with it the Azure Function through the Azure Resource Manager template, you will see an App Setting in the function with the name "WEBSITE_RUN_FROM_ZIP". Update it's value to:
https://github.com/Azure/iotedge-lorawan-starterkit/releases/download/v1.0.1/function-1.0.1.zip
Edit the Function's Application settings and make sure the FUNCTIONS_EXTENSION_VERSION App setting is set to ~2.
If during a previous upgrade you manually set it to 2.0.12342.0, please change it back to ~2.
| App Settings Name | Value |
|---|---|
| FUNCTIONS_EXTENSION_VERSION | ~2 |
Make sure the IoT Hub and Redis connection strings are properly configured in the function.
If you have manually deployed the Azure Function, re-deploy the updated version of the Azure Function Facade as outlined here if you have a previous version of this Azure Function running.
If you have deployed the solution and with it the Azure Function through the Azure Resource Manager template, you will see an App Setting in the function with the name "WEBSITE_RUN_FROM_ZIP". Update it's value to:
https://github.com/Azure/iotedge-lorawan-starterkit/releases/download/v1.0.0/function-1.0.0.zip
Edit the Function's Application settings and change the FUNCTIONS_EXTENSION_VERSION App setting from ~2 to 2.0.12342.0
| App Settings Name | Value |
|---|---|
| FUNCTIONS_EXTENSION_VERSION | 2.0.12342.0 |
Make sure the IoT Hub and Redis connection strings are properly configured in the function.
We highly recommend running the latest version of the IoT Edge runtime containers on your gateway to Version 1.0.6. The way that you update the IoT Edge agent and IoT Edge hub containers depends on whether you use rolling tags (like 1.0) or specific tags (like 1.0.2) in your deployment.
The process is outlined in detail here.
Furthermore, make sure, the following environment variables are set for your Edge hub container:
mqttSettings__enabled: false
httpSettings__enabled: false
TwinManagerVersion: v2
You do this by clicking "Set Modules" → "Configure advanced edge runtime settings" on your IoT Edge device in Azure IoT Hub.
Make sure the DevAddr of your ABP LoRa devices starts with "02": Due to addition of NetId support in this pre-relese, ABP devices created by the template prior to 0.4.0-preview (and all devices with an incompatible NetId in general) will be incompatible with the 0.4.0-preview. In this case, make sure the DevAddr of your ABP LoRa devices starts with "02".
Re-deploy the updated version of the Azure Function Facade as outlined here if you have a previous version of this Azure Function running.
Make sure the IoT Hub and Redis connection strings are properly configured in the function.
We highly recommend running the latest version of the IoT Edge runtime containers on your gateway (Version 1.0.5 at the time of writing). The way that you update the IoT Edge agent and IoT Edge hub containers depends on whether you use rolling tags (like 1.0) or specific tags (like 1.0.2) in your deployment.
The process is outlined in detail here.
Re-deploy the updated version of the Azure Function Facade as outlined here if you have a previous version of this Azure Function running.
Make sure the IoT Hub and Redis connection strings are properly configured in the function.