Data downlink in logs after each uplink

In the logs for each device, I see a ‘Schedule data downlink’ message after each ‘Forward uplink’ message. Why is this? I am not scheduling any downlink. What is this downlink message?

Here is the detailed log message:

{
  "name": "ns.down.data.schedule.attempt",
  "time": "2023-03-03T00:45:28.570497723Z",
  "identifiers": [
    {
      "device_ids": {
        "device_id": "eui-ff00000000004941",
        "application_ids": {
          "application_id": "bluebot-meter-alpha"
        },
        "dev_eui": "FF00000000004941",
        "join_eui": "7538904770366680",
        "dev_addr": "260901C1"
      }
    }
  ],
  "data": {
    "@type": "type.googleapis.com/ttn.lorawan.v3.DownlinkMessage",
    "raw_payload": "YMEBCSaKaWwDEAAAcQMQAP8BVH0BuQ==",
    "payload": {
      "m_hdr": {
        "m_type": "UNCONFIRMED_DOWN"
      },
      "mic": "VH0BuQ==",
      "mac_payload": {
        "f_hdr": {
          "dev_addr": "260901C1",
          "f_ctrl": {
            "adr": true
          },
          "f_cnt": 27753,
          "f_opts": "AxAAAHEDEAD/AQ=="
        },
        "full_f_cnt": 27753
      }
    },
    "request": {
      "downlink_paths": [
        {
          "uplink_token": "CiYKJAoYZXVpLWE4NDA0MWZkZmUyNDA2MzktbmV3EgioQEH9/iQGORDJjY2wARoLCKiGhaAGEP/+9UwgqIKy5t/KuwE="
        }
      ],
      "rx1_delay": 5,
      "rx1_data_rate": {
        "lora": {
          "bandwidth": 500000,
          "spreading_factor": 9,
          "coding_rate": "4/5"
        }
      },
      "rx1_frequency": "926900000",
      "rx2_data_rate": {
        "lora": {
          "bandwidth": 500000,
          "spreading_factor": 12,
          "coding_rate": "4/5"
        }
      },
      "rx2_frequency": "923300000",
      "priority": "HIGHEST",
      "frequency_plan_id": "US_902_928_FSB_2"
    },
    "correlation_ids": [
      "gs:conn:01GSV6TB3RBC4ZRQ4XTA2K5YEW",
      "gs:up:host:01GSV6TB8247BNV5SNBQDYSHA8",
      "gs:uplink:01GTJEWN71B09ND7K9SX9RAJ8V",
      "ns:downlink:01GTJEWNKT7ZN2GDCVC8693FM2",
      "ns:transmission:01GTJEWNKTT1Z0FXZK5ARVR709",
      "ns:uplink:01GTJEWN72ZTRET5K8NQXPGKNP",
      "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01GTJEWN71N4FAT9V6BHK65ME1"
    ]
  },
  "correlation_ids": [
    "gs:conn:01GSV6TB3RBC4ZRQ4XTA2K5YEW",
    "gs:up:host:01GSV6TB8247BNV5SNBQDYSHA8",
    "gs:uplink:01GTJEWN71B09ND7K9SX9RAJ8V",
    "ns:downlink:01GTJEWNKT7ZN2GDCVC8693FM2",
    "ns:transmission:01GTJEWNKTT1Z0FXZK5ARVR709",
    "ns:uplink:01GTJEWN72ZTRET5K8NQXPGKNP",
    "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01GTJEWN71N4FAT9V6BHK65ME1"
  ],
  "origin": "ip-10-22-4-213.us-west-1.compute.internal",
  "context": {
    "tenant-id": "Cg1ibHVlYm90LWFscGhh"
  },
  "visibility": {
    "rights": [
      "RIGHT_APPLICATION_TRAFFIC_READ"
    ]
  },
  "unique_id": "01GTJEWNKT8S83Q5395Z1CV7D1"
}

Can anyone give me insight on this? I’d like to understand this part of things stack, as I believe it may be affecting our deployment.

Is there a reason no one has responded, like this is a stupid question? This appears to be some MAC commands things stack is sending to the device… why though?

It is a mac payload, what is your node not doing?

Have searched the forum? TTN attempts to push settings which your node needs to confirm. If it doesn’t you have either selected a wrong LoRaWAN version for you device or your devices LoRaWAN implementation is not standards compliant and it needs to be fixed.