@paul-thornton Thanks, this worked! I figured out that the same addition 'region=LoRa.EU868' is needed at 4 locations in nanogateway.py: around line 169, 263, 355, and 378. I still have a problem with the downlink not getting to the node (without giving any error message). This may be a timing problem: Only in one instance, the TTN website indicated that the node confirmed receipt of the downlink. In all other cases, no such confirmation was received. Let me investigate that further first.

@robert-hh Thanks for your reply. Yeah exactly I am talking about repeater. Just let me know once they develop this part. Till then I will try to do by myself.

@rubencg195 The pull/push ack messaage show the communication via Internet to the TTN server. Independent of that, the LoRa device is always listening, except when it is sending itself. But that would only happen after an uplink message has been send and it was told by the server so deliver a downlink message. It might only happen, that if there are many nodes around sending, then the gateway may have started to listen to another message. A few notes. always use the software from the git repository. Do not copy it form the documentation. Use the latest firmware version with the software from the git repository. The nanogateway is listening on a single channel only. If you do not configure the node accordingly, the node will send on different channels. The examples for abp_node and otaa_node shoudl cater for that. Besides that, I have a comibinatin of a LoPy as nano-gateway and FiPy as nodes running, and they never seem to miss a packet.

@bed Yes, approach it step by step. First check the RF connection witrh the simple examples, which are tricky too. Then try ABP join, since that does not need downlink messages. After that go for OTAA join. There is indeed a problem with DRl 0 in the official 1.17.3.b1 revision, see https://github.com/pycom/pycom-micropython-sigfox/commit/ae3a294c40026433dbdac3e08da788b2b4c4dfdb, but that should not affect here.

@jmarcelino Thank you that appears to be correct! I get my push and pull acks now.

This looks like the example from 5.3.6 rather than 5.3.4 You can get the most up2date version from our GitHub repository. The easiest way is to download an archive of the most recent version and then open the directory examples/lorawan-nano-gateway/ in either Visual Studio Code or Atom, modify config.py and upload the code to the board.

@dylan Instant connection, I left my Gateway on The Things Network as the meshed router, but changed the server in my config.py to router.au.thethings.network. Thank you :).

@berni I would like to add my name to the list of people having the same problem with join issues. Incidentally I have another Node using an Arduino LoRaWan shield on the same nano gateway that joins successfully every time so I would tend to exclude noise issues with the Pycom OTAA / Nano Gateway example. It looks like software or firmware issues in the node to me. Hope this helps.

Dear Emmanuel, As i mentioned in my reply about a month ago, i could get it working when shifting the frequency a bit. Not sure what is causing it, but then communication could be established as well for uplink, downlink message as join requests.