Strange recurrent downlink

A strange downlink is continuously scheduled from the network server, which doesn’t allow the node to correctly send data, so there are many missing packets until the sensor node performs the OTA join again. The payload is always different, here an example:

DADC80DB7911538921C8E4F34A8966DC0B4450820665861CDB32A3BD753B9494BB313A8F36

I cannot understand if the first byte is the command ID. What command is 0xDA?