Downlink seems to not work


I’m still quite fresh to LoRaWan and managed to get 1 device working (don’t ask me how ;-). Now I try a second one but keep getting error messages. My Setup:

  • Lorix One gateway, registered in TTN V3
  • First device, draginoLSN50 v2-D20, sends data, payload was able to show correct temperatur
  • Second device, same model, is not able to join. Join request works, but downlink error
  • Third device, dragino GPS tracker is not even able to send join request

As you can see, I’m currently running out of the box HW just to get first experience but I’m encountering more troubles as I was expecting. I do everything on stack V3 to avoid an upcoming migration. I’m also using the web-interfaces, not yet ready to dig into lower level API’s.


Device 1:

  • I receive everything in the application, payload works as expected
  • After receiving the uplink, I get an entry: Schedule data downlink for transmission
  • Directly after I get an error: Failed to schedule
  • I don’t see these entries ending on the gateway

Device 2:

  • I receive a proper join request
  • I get an entry schedule join-accept for transmission
  • Directly followed by failed to schedule

Device 3:


  • uplink message in gateway
  • forward uplink message
  • Drop uplink message with: “MIC mismatch”
  • I believe that I entered everything correct, but would I find out

Example error message:

  "name": "",
  "time": "2021-02-13T13:39:23.633781014Z",
  "identifiers": [
      "device_ids": {
        "device_id": "orcanet-lora-temp1",
        "application_ids": {
          "application_id": "orcanet-test"
        "dev_eui": "A84041F61182663C",
        "join_eui": "31C32A55A17F67DE"
  "data": {
    "@type": "",
    "namespace": "pkg/gatewayserver",
    "name": "schedule",
    "message_format": "failed to schedule",
    "correlation_id": "f196c9d7d25e482ca188a364eface1c8",
    "code": 10,
    "details": [
        "@type": "",
        "path_errors": [
            "namespace": "pkg/gatewayserver",
            "name": "not_connected",
            "message_format": "gateway `{gateway_uid}` not connected",
            "attributes": {
              "gateway_uid": "orcanet-lorawan1@ttn"
            "code": 5
  "correlation_ids": [
  "origin": "",
  "context": {
    "tenant-id": "CgN0dG4="
  "visibility": {
    "rights": [
  "unique_id": "01EYDSW4BHXY0R4V5GJBEFE4BJ"

The V3 backend seems to think your gateway is offline and can be used for a downlink. This is not node related.

What is the keepalive_interval of your gateway set to?

This points to incorrect AppKey. Check you didn’t mix up characters. You would not be the first to use 8 where B should be used or vice versa.

PS, next post please format large text dumps for readability.

1 Like

Thanks for your replay. Regarding keepalive_interval, couldn’t find this setting on the Gateway. What I noticed is the fact, that the application tries the downlink message, but the Gateway in V3 doesn’t get it? I would expect, that the Gateway would show it in the live data?

Also noticed the the documentation for the LorixOne is outdated as they delivered it with a new OS version which changed many things, will ask back with the vendor next week

Regarding the second issue (MIC mismatch) I will try to reconfigure the device, the label is very bad to read, so I might try diferent combinations 8 <> B. Thanks for the hint.

Try taking a picture with a mobile phone and zooming in.

That is consistent with V3 considering the gateway being off-line. You wouldn’t deliver data for transmission to an offline gateway.