Gateway not receiving packets. What could be the problem?

End Devices (Nodes)
1

I’m unable to connect my sensors to my gateway. Sometimes the TTN live data displays an accepted join request for the sensor and in very rare circumstances I actually get a reading displaying temperature and humidity (what my sensor does), but most of the times I can’t get a reading and it disconnects very easily even tough the sensors are just a couple of meters away from the gateway. Looking at my gateway log I couldn’t find anything other than it not acknowledging the sensor packets. What could be wrong?

Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ ################## Report at: 2022-01-24 19:10:58 UTC ##################
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ ### [UPSTREAM] ###
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # RF packets received by concentrator: 2
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # RF packets forwarded: 2 (46 bytes)
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # PUSH_DATA datagrams sent: 2 (491 bytes)
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # PUSH_DATA acknowledged: 0.00%
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ ### [DOWNSTREAM] ###
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # PULL_DATA sent: 1 (0.00% acknowledged)
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # RF packets sent to concentrator: 0 (0 bytes)
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # TX errors: 0
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # BEACON queued: 0
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # BEACON sent so far: 0
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # BEACON rejected: 0
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ ### [PPS] ###
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: REPORT~ # SX1301 time (PPS): 1263325310
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: INFO: [jit] queue is empty
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: INFO~ ### [GPS] ###
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: INFO~ # GPS sync is disabled
Mon Jan 24 19:10:58 2022 daemon.info lora_pkt_fwd[13420]: INFO~ ##### END #####
2

They don’t…this is LoRaWAN not WiFi. A gateway just passes on messages it hears from any node it hears in range. A node just broadcasts and any gw in range will pass the message on to the Network Server.

So data sometimes suggests your or another gw in range picks up the nodes message and sends it through, suggesting the node is registered correctly with the NS.

You now need to establish if the received messages (ever) come via your gw or via another at a distance.

It’s likely your node is shouting at the gw and vice verse,so get some distance between them… 5-10m and pref with an absorber (a wall) in between them and see if they start to behave…

4

Hi. Thanks for your response. Looking at TTN Mapper it appears I have the only gateway in my region so another gateway shouldn’t be a problem. When I successfully connected a sensor and got a reading, the connection closed when I distanced the sensor just how you describe it and the sensor never has connected when distanced. Could I have an interference problem? I’m in a manufacturing plant where we use radios to communicate, also cellular data has a hard time reaching this place. I don’t know if that information is relevant to the problem but it looks I’m running out of options.