Give it a year …
Probably always has in all this murk, but hard to tell.
2C-F7-F1 is registered to Seeed so that makes sense.
But that doesn’t mean the JoinEUI or AppKey are OK.
1 Like
hmm… it really should´t be. This is what I get when I do a Get request, and is exactly the same that I put in the console. (i have hidden the app key)
{
"code": "0",
"data": {
"nodeEui": "2CF7F12032400078",
"deviceCode": "4661481BA5F27EBD",
"lorawanInformation": {
"dev_eui": "2CF7F12032400078",
"app_eui": "8000000000000009",
"app_key": "hidden"
}
}
}
I also attached a small variant of the json file. It´s the same that repeats itself, but I wonder about the network failure that it states.
Your failure to post the JSON in a format that can be read without a download plus all the to’ing & fro’ing and you turning off your gateway for no apparent reason is beginning to hit all the troll alerts on the Discourse admin panel.
If these are what you are getting, this is your web browser losing the connection to the TTN console - it restores itself automatically and only shows that your internet connection isn’t great. It has little to do with the issue at hand.
Either turn on your gateway and show us a join request or get near one - but please stop posting random things that won’t move this thread forward.
I am sorry that I don´t have the competense to answer you just the right way you want Nick. If you have´nt noticed I am quite a noob when it comes to LoraWAn and this forum. What i do have is a competanse in treating people with a proper politeness. Now please don´t bother with my stupid questions anymore, I have had proper help so far from other people in the forum.
We have asked you to give us the JSON for a Join Request inline, not as an attachment, several times now. You’ve shown you can put JSON in to a post. But we’ve made scant progress to seeing a Join Request and you keep attaching largish files that don’t provide the information to help you. It’s not impolite to say that you are not answering our questions that seek to help YOU, it’s trying to move this along entirely for your benefit.
And I appreciate the fact that you are trying to help me, I really do and NOW I think I understood what you were asking.
{
"name": "js.join.accept",
"time": "2022-08-07T16:39:32.128851420Z",
"identifiers": [
{
"device_ids": {
"device_id": "eui-2cf7f12032400078",
"application_ids": {
"application_id": "tempsagene"
},
"dev_eui": "2CF7F12032400078",
"join_eui": "8000000000000009",
"dev_addr": "260B0E68"
}
}
],
"correlation_ids": [
"rpc:/ttn.lorawan.v3.NsJs/HandleJoin:01G9WJT3GX9VV40X38H51BSYEP"
],
"origin": "ip-10-100-6-236.eu-west-1.compute.internal",
"context": {
"tenant-id": "CgN0dG4="
},
"visibility": {
"rights": [
"RIGHT_APPLICATION_TRAFFIC_READ"
]
},
"unique_id": "01G9WJT3H0CB0KSNJ80FP51C4Q"
}
Close, but not a Join Request. The one before this console line.
Well there are really only 3 thing required to be configured between the Node and the End Device in the console.
- AppEUI/DevEUI/AppKey (Order need to be correct, LSB/MSB)
- Frequency plan
- LoRaWAN version/Regional Parameters version
4.You need to take heed not to overload the RX on the Gateway or the Node, thus the 10m plus and brick wall separation.
Yes there are 1000 other things can be messed up, but what I have seen, these are the 3 common things, especially with over the counter nodes.
Ok, 11th time is the charm… 
{
"name": "js.join.accept",
"time": "2022-08-08T13:59:40.649445383Z",
"identifiers": [
{
"device_ids": {
"device_id": "eui-2cf7f12032400078",
"application_ids": {
"application_id": "tempsagene"
},
"dev_eui": "2CF7F12032400078",
"join_eui": "8000000000000009",
"dev_addr": "260BB67F"
}
}
],
"correlation_ids": [
"rpc:/ttn.lorawan.v3.NsJs/HandleJoin:01G9YW23V1PDKZ5PB3W97X2NE3"
],
"origin": "ip-10-100-5-104.eu-west-1.compute.internal",
"context": {
"tenant-id": "CgN0dG4="
},
"visibility": {
"rights": [
"RIGHT_APPLICATION_TRAFFIC_READ"
]
},
"unique_id": "01G9YW23V9JDMP91TGE6XSXDQB"
}
Still a big no. It’s the Join Request, like I’ve said several times, including 20h’s ago - that’s almost a day you’ve not made progress now:
Well, somehow it suddenly went online, and I am not sure why… It´s going to be exciting to see if the device stays online. And during the last 20 hours I have been sleeping and been to work, so not able to work on the 24 hours a day.
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 …