@UdLoRa is right: this single channel forwarder (sometimes called a “gateway”, but it really isn’t) does not support downlinks, hence cannot be used for OTAA.
Too bad the 2017 tutorial does not mention that. It even writes “If the TTN registrations and pairing successful, then we will be able to see all the uplinks/downlinks on TTN interface” but I really think that’s false, as it uses git clone https://github.com/tftelkamp/single_chan_pkt_fwd.git while that repository clearly states:
Please note this repository is deprecated, and the code is not up-to-date to use on The Things Network.
…
Not (yet) supported:
- …
- downstream messages (tx)
TTN will know that this forwarder does not support downlinks, as it never polls TTN for commands for such downlinks. So, for future readers, I wonder if there’s really no error message to be seen in TTN Console:
-
Please click the OTAA Join Requests in the gateway’s Traffic page, and see if there’s any error? Please carefully read the “trace” part as well.
-
Please see if the application’s or node’s Data page shows the Join Request as well? And if yes, please tell us if clicking that shows any errors?
Screenshots are appreciated! It might be something like described in Activation not valid - no gateways available.
So, this single channel forwarder can only be used for testing with ABP, not with OTAA.