Device activation without an uplink


I have a problem with the activation of a commercial Class-A Lora Node.
The Join process works fine and is ansewered with a Join Accept.
The device activation in loraserver_ns is done.

In topic topic I have learned that the activation needs an additional uplink from the node with payload data for the loraserver_as.

Now the problem is that the LoRa Node first had to be configured over the air, before it can send an uplink to the application (it means an uplink with payload data).
But the configuration can not be started bacause the downlink queue of loraserver can not be filled without an activation of the device.

I can start a so called configuration mode on a node. In this configuration mode the node sends an uplink WITHOUT payload data for 10 Minutes. This Uplink fame do not lead to activation in Application Server (I think because there is no payload within this frame).

Logs below:
appserver_1 | time=“2019-06-28T11:02:21Z” level=info msg=“integration/mqtt: data-down payload received” topic=application/1/device/70b3d5e75e006862/tx
appserver_1 | time=“2019-06-28T11:02:21Z” level=warning msg=“creating insecure network-server client” server=“loraserver:8000”
loraserver_1 | time=“2019-06-28T11:02:21Z” level=info msg=“finished unary call with code OK” grpc.code=OK grpc.method=GetNextDownlinkFCntForDevEUI grpc.service=ns.NetworkServerService grpc.start_time=“2019-06-28T11:02:21Z” grpc.time_ms=1.45 peer.address=“” span.kind=server system=grpc
appserver_1 | time=“2019-06-28T11:02:21Z” level=info msg=“finished client unary call” grpc.code=OK grpc.method=GetNextDownlinkFCntForDevEUI grpc.service=ns.NetworkServerService grpc.time_ms=2.527 span.kind=client system=grpc
appserver_1 | time=“2019-06-28T11:02:21Z” level=error msg=“handle data-down payload error: enqueue downlink device-queue item error: get last device-activation error: object does not exist” application_id=1 dev_eui=70b3d5e75e006862

Can someone give me a solution for that vicious circle.

Thanks in advance.

1 Like

If this is the case, please create an issue at :slight_smile:

Issue 408 solved my Problem with the activation of the device.

Thanks for your help.


1 Like