Tago/TTI Downlink issue - Payload changed

Hi, Looking for anyone who can help on what seems to be a silly issue, but I am stuck.

I am using TagoIO connected to TTI private network to control a Milesight UC1114 Remote IO device.

When sending downlink commands, I can message from TTI without issue. eg 090100ff closes one of the relay switches.

When I try and do the same thing from Tago to TTI, the json message seems ok (I get “frm_payload”: “090100ff”,) however the actual downlink payload is “D3DD35D347DF” which obviously is ignored by device.

Can anyone point me in the right directions to fix this?

Regards
Dayne

{
“name”: “as.down.data.forward”,
“time”: “2021-04-05T15:04:37.043648943Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “insideuc1114”,
“application_ids”: {
“application_id”: “canso-test”
}
}
}
],
“data”: {
@type”: “type.googleapis.com/ttn.lorawan.v3.ApplicationDownlink”,
“f_port”: 1,
“frm_payload”: “090100ff”,
“priority”: “NORMAL”,
“correlation_ids”: [
“as:downlink:xxxxxxx”
]
},
“correlation_ids”: [
“as:downlink:xxxxxxxxx”
],
“origin”: “ip-10-22-7-252.us-west-1.compute.internal”,
“context”: {
“tenant-id”: “xxxxxx”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“authentication”: {
“type”: “Bearer”,
“token_type”: “APIKey”,
“token_id”: “xxxxx”
},
“remote_ip”: “100.25.118.118”,
“user_agent”: “axios/0.20.0”,
“unique_id”: “xxxxxxxx”
}

  • rrow_downward

09:04:37

Successfully scheduled data downlink for transmission on Gateway Server

DevAddr

2609D304

  • arrow_downward

09:04:37

Schedule data downlink for transmission on Gateway Server

DevAddr

2609D304

FPort

1

MAC payload

ABC5DB393B86

  • arrow_downward

09:04:37

Forward downlink data message

FPort

1

Payload

D3DD35D347DF

  • arrow_downward

09:04:37

Receive downlink data message

FPort

1

Payload

D3DD35D347DF

Hi Dayne,
We had noticed the same issue with downlinks for TTI. We are investigating this issue and I’ll return to you soon.

1 Like

I seem to have got past this on one example anyway. TTI doesn’t seem to like the ff at the end. Prior it was accepting it directly in the TTI messaging console, but now instead of 09 01 00 ff, it wants 09 01 00, and this also works sending from Tago.

Don’t ask me why, but it is working today.