Wio Tracker 1110 TTS Uploading Issues

Products & Technology Wio Series
#1

Hello, I have a wio tracker 1110 that I have connected to the tts. I believe I have followed the tutorial correctly, however I am not getting a successfully processed data message or any of the measurements in the Event details. I have also attached what I get in the Event details

Any help would be greatly appreciated, thank you!

`{
“name”: “as.up.data.forward”,
“time”: “2024-09-03T03:02:06.999122738Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “wio-1”,
“application_ids”: {
“application_id”: “wio-main-1”
},
“dev_eui”: “XXX”, # I have removed these
“join_eui”: “XXX”,
“dev_addr”: “XXX”
}
}
],
“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.ApplicationUp”,
“end_device_ids”: {
“device_id”: “wio-1”,
“application_ids”: {
“application_id”: “wio-main-1”
},
“dev_eui”: “XXX”,
“join_eui”: “XXX”,
“dev_addr”: “XXX”
},
“correlation_ids”: [
“gs:uplink:01J6TXA5P58VKEYAZ4YT8GWV2A”
],
“received_at”: “2024-09-03T03:02:06.995282068Z”,
“uplink_message”: {
“session_key_id”: “AZG1uS7miZdHbEF6bm7t7g==”,
“f_port”: 199,
“f_cnt”: 34,
“frm_payload”: “FwErBwAAEA==”,
“decoded_payload”: {
“err”: 0,
“messages”: [
{
“fport”: 199,
“payload”: “17012b07000010”
}
],
“payload”: “17012b07000010”,
“valid”: true
},
“rx_metadata”: [
{
“gateway_ids”: {
“gateway_id”: “exata-hub”,
“eui”: “0016C001F156AE64”
},
“timestamp”: 3879200450,
“rssi”: -39,
“channel_rssi”: -39,
“snr”: 10.5,
“frequency_offset”: “-236”,
“uplink_token”: “ChcKFQoJZXhhdGEtaHViEggAFsAB8VauZBDCzd+5DhoMCK742bYGEMiS7PcCINDL9ZLz5AQ=”,
“channel_index”: 2,
“received_at”: “2024-09-03T03:02:06.788203848Z”
}
],
“settings”: {
“data_rate”: {
“lora”: {
“bandwidth”: 125000,
“spreading_factor”: 7,
“coding_rate”: “4/5”
}
},
“frequency”: “904300000”,
“timestamp”: 3879200450
},
“received_at”: “2024-09-03T03:02:06.789967144Z”,
“consumed_airtime”: “0.056576s”,
“network_ids”: {
“net_id”: “000013”,
“ns_id”: “EC656E0000000182”,
“tenant_id”: “ttn”,
“cluster_id”: “nam1”,
“cluster_address”: “nam1.cloud.thethings.network”
}
}
},
“correlation_ids”: [
“gs:uplink:01J6TXA5P58VKEYAZ4YT8GWV2A”
],
“origin”: “ip-10-101-4-41.us-west-1.compute.internal”,
“context”: {
“tenant-id”: “CgN0dG4=”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“unique_id”: “01J6TXA5WQFSCTQYMB8DBFWM86”
}``

#2

have you tried connecting to the Seeed SenseCap Dashbord?

#3

I have tried and done that already. I was able to get the information there initially, but haven’t been able to/tried since I started trying to connect to TTS

#4

i think you got a setting wrong… sometimes you have to completely reset the install… its kinda a pain

#5

I have tried completely resetting the install as well. Is it at all possible the issue is from the way the gateway was setup? I’m using a RAK 5146 pi hat

#6

I am using the SenseCAP M2

#7

Hmm, I’ll have to do some more testing I guess. I did double check the LoRa frequency region. Maybe worth resetting the gateway and trying again

Thanks for the help though

#8

After further testing, I believe the issue lies in the custom Javascript payload formatter that is provided here: Connect to TTN | Seeed Studio Wiki

If anybody has any ideas, it would be greatly appreciated. Thanks

1 Like
#9

Hi @Victor ,

TTS receives uplink,

“f_port”: 199,
“f_cnt”: 34,
“frm_payload”: “FwErBwAAEA==”,

Here is the decoded version in payload formatter.

“decoded_payload”: {
“err”: 0,
“messages”: [
{
“fport”: 199,
“payload”: “17012b07000010”
}
],
“payload”: “17012b07000010”,
“valid”: true
},

The wiki code does not seem to be executing messageAnalyzed() since the fport is 199. :thinking:

1 Like
#10

Ah thank you, that makes sense. I think I saw others on the forum having the same issue as well.

Anybody know how to fix this issue?