Cannot send Downlink data from thingsboard to TTI

Hi,

I can send uplink data from TTI cloud console to ThingsBoard by using MQTT integration.
But I am facing a problem of downlink data from thingsboard to TTI .
Downlink converter payload data is queuing in the ThingsBoard Integration, but it cannot proceed to TTI cloud.
Uplink

message in TB integration
{
“topic”: “v3/iot-controller-application@agb-iot-tti/devices/eui-24e124445d080814/up”,
“payload”: {
“end_device_ids”: {
“device_id”: “eui-24e124445d080814”,
“application_ids”: {
“application_id”: “iot-controller-application”
},
“uplink_message”: {
“f_port”: 85,
“f_cnt”: 5,
“frm_payload”: “AwAABAAABQAABgAABwEACAEB”,
“decoded_payload”: {
“gpio_in_1”: “off”,
“gpio_in_2”: “off”,
“gpio_in_3”: “off”,
“gpio_in_4”: “off”,
“gpio_out_1”: “NC”,
“gpio_out_2”: “NO”
}
}
}
Downlink

message in TB integration
{
“topic”: “v3/iot-controller-application@agb-iot-tti/devices/eui-24e124445d080814/down/push”,
“payload”: {
“downlinks”: [{
“f_port”: 2,
“confirmed”: false,
“frm_payload”: {
“fport”: 2
},
“priority”: “HIGHEST”
}]
}
}

the above downlink cannot proceed to my TTI cloud downlink queue.
My gateway is milesight UG 63
Milesight UC 300 IoT controller
I really hope for help to solve my issue.
Khu khu

This isn’t right - perhaps check the docs!

Not really relevant - they all work to the same spec - but what would be super extra brilliant to know is what device you are using as that speaks to the format.

Please review your formatting of your post - you can edit it with the pencil tool after you’ve posted.

OK. I will update it.

What device!!!

Milesight UC 300 IoT controller
Here are download queue in TTI console
{
“name”: “ns.down.data.schedule.attempt”,
“time”: “2023-11-09T09:58:28.972970329Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “eui-24e124445d080814”,
“application_ids”: {
“application_id”: “iot-controller-application”
},
“dev_eui”: “24E124445D080814”,
“join_eui”: “24E124C0002A0001”,
“dev_addr”: “27037069”
}
}
],
“data”: {
@type”: “type.googleapis.com/ttn.lorawan.v3.DownlinkMessage”,
“raw_payload”: “YGlwAyeDCAACFQHGTaQv”,
“payload”: {
“m_hdr”: {
“m_type”: “UNCONFIRMED_DOWN”
},
“mic”: “xk2kLw==”,
“mac_payload”: {
“f_hdr”: {
“dev_addr”: “27037069”,
“f_ctrl”: {
“adr”: true
},
“f_cnt”: 8,
“f_opts”: “AhUB”
},
“full_f_cnt”: 8
}
},
“request”: {
“downlink_paths”: [
{
“uplink_token”: “CiIKIAoUZXVpLTI0ZTEyNGZmZmVmNTU0NGESCCThJP/+9VRKEJXf4hQaDAjE2rKqBhDZkbGMAiCIvLejou8F”
}
],
“rx1_delay”: 5,
“rx1_data_rate”: {
“lora”: {
“bandwidth”: 125000,
“spreading_factor”: 7,
“coding_rate”: “4/5”
}
},
“rx1_frequency”: “923400000”,
“rx2_data_rate”: {
“lora”: {
“bandwidth”: 125000,
“spreading_factor”: 10,
“coding_rate”: “4/5”
}
},
“rx2_frequency”: “923200000”,
“priority”: “HIGHEST”,
“frequency_plan_id”: “AS_923”
},
“correlation_ids”: [
“gs:uplink:01HESR9MYK4M1GSER5ZV1JYQ8Y”,
“ns:downlink:01HESR9NBCZW0QV4ME97AZZJYH”,
“ns:transmission:01HESR9NBCEDHAG5MQV7CAXDVH”
]
},
“correlation_ids”: [
“gs:uplink:01HESR9MYK4M1GSER5ZV1JYQ8Y”,
“ns:downlink:01HESR9NBCZW0QV4ME97AZZJYH”,
“ns:transmission:01HESR9NBCEDHAG5MQV7CAXDVH”
],
“origin”: “ip-10-21-7-80.ap-southeast-2.compute.internal”,
“context”: {
“tenant-id”: “CgthZ2ItaW90LXR0aQ==”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“unique_id”: “01HESR9NBCN09WVRBKAS0KTM59”
}

Ah, I can see that now, which is why clear formatted spaced posts are so important.

If you have your own instance, do you not have a support option as well??

I do not understand what do you mean?
You ask me about technical support from TTI?
There is no any technical support for me, I am a new learner of TTI and thingsboard platform by reading document and try step by step.

You have an instance called agb-iot-tti so you are not using the community (TTN) edition.

If you have a private instance, did you subscribe to support?

Subscribing to a support plan is not related to how much you know, it’s about your choices when you registered - if you have support, TTI can help you. If you don’t, then it’s just whatever we can figure out here.

Hopefully in the meanwhile you’ve sorted out your JSON payload!

Thank you for your well explanation. If so, I will try to contact technical support team or open a ticket.

Or you could just read the docs and make the JSON format correct!

Yes, I have check the document, and I tried to fix the JSON format.
I take a reference here.
ThingsBoard | The Things Stack for LoRaWAN (thethingsindustries.com)

Sincerely I do not have enough skill in writing code.
In my tti instance, Uplink payload formatter is processing well.
I think I have problem in downlink formatter encoderDownlink(input)
I read reference, I think, it is depending on the user background skills to make code modification.

</>
function encodeDownlink(input) {
return {
bytes: ,
fPort: 1,
warnings: ,
errors:
};
}

function decodeDownlink(input) {
return {
data: {
bytes: input.bytes
},
warnings: ,
errors:
}
}
</>

will it be possible to make your post more readable

if you post code or any text from debug use the </> tool in the post editor please

Ok, noted it.