Unable to join ttn. Gateway receive the message

[italocjs]

I have been trying to get a working connection from a end node to TTN for a couple of days without any success, The gateway i have set up is working and i can see the RX event from the node (i can also see it on the TTN gateway page) but it seems that the message gets lost there, it never reaches the application and register the device. Any ideas?

Frequencies and keys have been checked dozens of times.

Gateway screenshot: https://user-images.githubusercontent.com/9244531/144599390-aa7c5e42-b564-4347-b348-9f81f5b1f63e.png

Device screenshot: https://user-images.githubusercontent.com/9244531/144599401-4d6ddeed-b00c-4276-a4bc-386638b4a0fe.png

Config screenshot:

I have also tried over 5 different libraries, all with the same result (no success on join).

[Jeff-UK]

@italocjs

for a couple of days without any success

@italocjs

tried over 5 different libraries

Which ones have you tried - source of library, stock builds or have you changed/modified
Which hardware? Pictures show V3 registration/data - was it ever set up on V2 - which effectively was put to rest ‘a couple of days ago’!

[cslorabox]

What type of gateway is “esp-01-gate-italo” ?

Does the app key exactly match?

[descartes (Nick McCloud)]

@cslorabox

What type of gateway is “esp-01-gate-italo” ?

Good spot!

To cut to the chase, are you using a Single Channel Packet Forwarder? If so, they cause issues for both the developer (as you’ve found) and for the community and are not supported on TTN. See:

Single Channel Packet Forwarders (SCPF) are obsolete and not supported

Single channel packet forwarders are obsolete and are not supported Single Channel in this article refers to both Single Channel and Dual Channel devices (and any variations thereof). Single Channel Packet Forwarders are not LoRaWAN compliant gateways. They negatively impact proper operation of gateways and end devices (nodes) in their area which means they negatively impact The Things Network and its users, but they also impact other LoRaWAN operators. Not only now, but also in the future w…

[bluejedi]

Without any details about your hardware, LoRaWAN library and software/sketch it will be difficult to provide any meaningful help.

@italocjs

I have also tried over 5 different libraries, all with the same result (no success on join).

What exactly have you tried?

[italocjs]

Nailed it. i was trying to use a single channel fowarder to start tinkering with LoRaWAN.
This is for sure the issue, as they are not supported on TTN.

Question, all server have “banned” this type of gateway? or is there any which i could use at least while i’m waiting to receive a lora gateway?

[cslorabox]

@italocjs

Question, all server have “banned” this type of gateway? or is there any which i could use at least while i’m waiting to receive a lora gateway?

You can run a private server, but you’ll find almost no support resources for difficulties encountered - both difficulties unique to single-channel hacks that violate the LoRaWAN spec, and also ordinary difficulties encountered in the context of such hacked up implementations.

Also, you need a LoRaWAN gateway - “LoRa Gateway” is sometimes used as an euphemism for commercial versions of precisely the sort of unwise node-pretending-to-be-a-gateway lashup that you already have. You need something with an sx1301, sx1302, sx1303 or sx1308 in it, and it needs to be for the frequency band used in your location (probably EU868)

[bluejedi]

@italocjs

or is there any which i could use at least while i’m waiting to receive a lora gateway?

No, there isn’t. SCPF are not LoRaWAN gateways because not LoRaWAN compliant. A LoRaWAN network server is not going to change that.

You can make use of any TTN gateway in your neighbourhood for your node, if there is any within reach. If not available you will just have to be patient until your own LoRaWAN gateway arrives.