Bug: Empty device twin configuration when creating a AU915 gateway

[adcoly]

Expected Behavior

When I create a gateway, I retrieve this one in the Azure device list and its device twin should have a complete radio configuration based on the selected region.

Current Behavior

I'm trying to create a concentrator in AU915 (with one of its Frequency Sub-Band) and when I'm heading to its twin in Azure, there is no radio configuration.

(Update: After some verification, it's doing the same for each AS and AU configuration, but CN, US & EU are still working well)

Context (Environment)

Portal version: 4.13.1.169
LoRaWAN Stack version: 2.1.0

Logs

Twin of my concentrator:

{
    "deviceId": "002244FFFE6688AA",
    "etag": "AAAAAAAAAAQ=",
    "deviceEtag": "MzgwODUxNjQ2",
    "status": "disabled",
    "statusUpdateTime": "0001-01-01T00:00:00Z",
    "connectionState": "Disconnected",
    "lastActivityTime": "0001-01-01T00:00:00Z",
    "cloudToDeviceMessageCount": 0,
    "authenticationType": "sas",
    "x509Thumbprint": {
        "primaryThumbprint": null,
        "secondaryThumbprint": null
    },
    "modelId": "",
    "version": 5,
    "tags": {
        "deviceName": "Test AU 915",
        "loraRegion": "AU_915_928_FSB_1",
        "deviceType": "LoRa Concentrator"
    },
    "properties": {
        "desired": {
            "$metadata": {
                "$lastUpdated": "2023-06-28T07:26:43.246794Z",
                "$lastUpdatedVersion": 3
            },
            "$version": 3
        },
        "reported": {
            "$metadata": {
                "$lastUpdated": "0001-01-01T00:00:00Z"
            },
            "$version": 1
        }
    },
    "capabilities": {
        "iotEdge": false
    }
}

Additional Information

Concentrator in the portal: