You should then see the decoded data in the application console.
What is in that json? You can see the gateways the devices are using.
Well, I a bit scared of giving you the wrong bit, but here goes nothing. āPacketbrokerā may be the GW it uses?
{
"name": "ns.up.data.process",
"time": "2022-08-08T16:27:23.132506458Z",
"identifiers": [
{
"device_ids": {
"device_id": "eui-2cf7f12032400078",
"application_ids": {
"application_id": "tempsagene"
},
"dev_eui": "2CF7F12032400078",
"join_eui": "8000000000000009",
"dev_addr": "260B0946"
}
}
],
"data": {
"@type": "type.googleapis.com/ttn.lorawan.v3.UplinkMessage",
"raw_payload": "QEYJCyaABQACTVAik8KlwEfhkoLcKg==",
"payload": {
"m_hdr": {
"m_type": "UNCONFIRMED_UP"
},
"mic": "koLcKg==",
"mac_payload": {
"f_hdr": {
"dev_addr": "260B0946",
"f_ctrl": {
"adr": true
},
"f_cnt": 5
},
"f_port": 2,
"frm_payload": "TVAik8KlwEfh",
"full_f_cnt": 5
}
},
"settings": {
"data_rate": {
"lora": {
"bandwidth": 125000,
"spreading_factor": 12
}
},
"coding_rate": "4/5",
"frequency": "867300000"
},
"rx_metadata": [
{
"gateway_ids": {
"gateway_id": "packetbroker"
},
"packet_broker": {
"message_id": "01G9Z4GJD1NF40M3T82M8D8011",
"forwarder_net_id": "000013",
"forwarder_tenant_id": "ttnv2",
"forwarder_cluster_id": "ttn-v2-legacy-eu",
"forwarder_gateway_eui": "C0EE40FFFF297392",
"forwarder_gateway_id": "eui-c0ee40ffff297392",
"home_network_net_id": "000013",
"home_network_tenant_id": "ttn",
"home_network_cluster_id": "eu1.cloud.thethings.network"
},
"rssi": -112,
"channel_rssi": -112,
"snr": -6.5,
"location": {
"latitude": 59.902731,
"longitude": 10.741787,
"altitude": 62
},
"uplink_token": "eyJnIjoiWlhsS2FHSkhZMmxQYVVwQ1RWUkpORkl3VGs1VE1XTnBURU5LYkdKdFRXbFBhVXBDVFZSSk5GSXdUazVKYVhkcFlWaFphVTlwU2xkaVIzQTFWRlZzTUZwSVRqTlBTRVpaV2xab2FVbHBkMmxrUjBadVNXcHZhVTU2U2toVWVscE1WakpzY0ZSWVRURlJNVXB4VTBad01FMVdPSGRhZVVvNUxtaGpTM0ZKY1RSdWRFMXVkVGc0Y0VKQk1rTTBYMEV1VTB3M1NtMWplVGcwWXpsbGJsaEpNQzVMUW5JdE5XUlVSRmx6Y2t3d1puUkthREp6Vm00ek5WUk1WVkY1T0hoU1ZreFdPVTlyYjFkamJtWTRNbXBDYURBMk5YRkdUVEkyTmtwV2RUSnhTalV4VW5aelFrbHVhR2hyTWxKZlFrOUJSMDltYUhVd1FqTmxjbXBXZFZWclZuZHFWMkpKT1dFeVUwbGljbTVuZWxSa2RXbHdNMkUxY1ROcGVFcHNRekV5TFhWTloxaDRaVkpFZFZoUlRWaG5SVXBEVmtwMVNXSk1PRko2VDFCVVIycEpVVjlFWkdkcFNHb3pRUzU2WWpaS2JYTklOVWRFY2s1Q1VVWnZOMnRUUm5abiIsImEiOnsiZm5pZCI6IjAwMDAxMyIsImZ0aWQiOiJ0dG52MiIsImZjaWQiOiJ0dG4tdjItbGVnYWN5LWV1In19",
"received_at": "2022-08-08T16:27:22.911388237Z"
}
],
"received_at": "2022-08-08T16:27:22.928433299Z",
"correlation_ids": [
"ns:uplink:01G9Z4GJDGNZG5ZAN7K1TYBK52",
"pba:conn:up:01G9YK8055Q7PAJ77WG4ZEF157",
"pba:uplink:01G9Z4GJD1NF40M3T82M8D8011",
"rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01G9Z4GJDG4CRAJ3DR1BFP5Q1G"
],
"device_channel_index": 4,
"consumed_airtime": "1.482752s"
},
"correlation_ids": [
"ns:uplink:01G9Z4GJDGNZG5ZAN7K1TYBK52",
"pba:conn:up:01G9YK8055Q7PAJ77WG4ZEF157",
"pba:uplink:01G9Z4GJD1NF40M3T82M8D8011",
"rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01G9Z4GJDG4CRAJ3DR1BFP5Q1G"
],
"origin": "ip-10-100-5-248.eu-west-1.compute.internal",
"context": {
"tenant-id": "CgN0dG4="
},
"visibility": {
"rights": [
"RIGHT_APPLICATION_TRAFFIC_READ"
]
},
"unique_id": "01G9Z4GJKWMF7P9DEEFRJ6RH9E"
}
Great you have your node up and connected via a gateway that is on V2 that still needs to migrate to V3.
That gateway is in Oslo harbor, you can see itās latitude and longitude, the SF is a bit high but you are most probably some distance from it.
1 Like
Now what documentation or steps did you follow to set it up on TTN? I cant see much doc around this, to set it up on TTN.
Itās all rather simple - we ask for something like Join Request, you provide something that says Join Request in it.
As @Johan_Scheepers says, you must be some distance from this gateway, so wondering why you have yet to turn on your own gateway.
The āForward uplink data messageā is more informative - as.up.data.forward - than ns.up.data.process
The āPacketbrokerā links various LoRaWAN networks together - see https://www.thethingsindustries.com/docs/getting-started/packet-broker/
Thanks, well my GW is on, but disconnectedā¦ aaand I suspect it never has registered to TTN properly. As stadet by Johan, the documentation on this is very poorā¦ So thats my next issueā¦ To get the GW up&running. 
And yes, the GW in Oslo harbor is quite far from where I am, and there are GW closer, but they seem to not reach very long.
BTW, what may have got this working is that I had to remove the sensor from the Sensecap portal: SENSECAP. I got a mail from their support that mentioned this. I have asked for an explanation why, and are awaiting their response.
Just to clarify, youāre saying that the documentation for taking a Raspberry Pi based Helium Browan/MerryIOT Hotspot Miner V1 and converting it to a normal gateway and setting it up for TTN is poor?
Where did you find those docs?
And @Johan_Scheepers was referring to the SenseCap device, not the gateway.
The devil is in the detail here!
Yes, the documentation from Browan/MerryIOT is not very good when it comes to TTN and LW. I found some on their website and youtube.
You sure that Johan was referring to de device? The docs on the device is quite good (although it has a few flaws like the fact that you cant register the device on both TTN and their own console.)
Pretty sure, but he can confirm. Itās not like weād go looking for docs on turning a Helium gateway in to a proper one. To that end I think you lost the irony in the comment about exactly that - mostly people are keeping their miners going hoping to strike it rich one day ā¦