TTOG still not listed as online

[davidgs]

This has been going on for a minute but I’m just getting around to dealing with it. The TTOG seems to be properly configured, but it’s not showing up in my dashboard as on-line:

Log:
# CRC_OK: 0.00%# RF packets received by concentrator: 2
### [UPSTREAM] ###
##### 2020-09-14 18:22:20 GMT #####
JSON up: {"stat":{"time":"2020-09-14 18:21:50 GMT","lati":35.69402,"long":-78.77936,"alti":127,"rxnb":2,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":0}}
##### END #####
# GPS coordinates: latitude 35.69402, longitude -78.77936, altitude 127 m
# Valid time reference (age: 1 sec)
### [GPS] ###
# SX1301 time (PPS): 3642347496
### [JIT] ###
# BEACON rejected: 0
# BEACON sent so far: 2007
# BEACON queued: 2010
# TX errors: 0
# RF packets sent to concentrator: 0 (0 bytes)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# PULL_DATA sent: 3 (0.00% acknowledged)
### [DOWNSTREAM] ###
# PUSH_DATA acknowledged: 0.00%
# PUSH_DATA datagrams sent: 1 (155 bytes)
# RF packets forwarded: 0 (0 bytes)
# CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
# RF packets received by concentrator: 2
### [UPSTREAM] ###
##### 2020-09-14 18:21:50 GMT #####

And it looks to be configured correctly:

but my console still shows:

Any ideas??

[descartes (Nick McCloud)]

There is an issue with the console being rather unreliable:

TTN Console not working properly all the time [console] [gateway] [not connected] [no traffic] [application] [no data]

The TTN Console is not working properly all the time The following issues can manifest: Gateway is shown in TTN Console as ‘not connected’ or e.g. ‘last seen 1 days ago’ while the gateway is actually connected. The disadvantage of this is that the TTN Console gateway status is unreliable and that the gateway Traffic cannot be monitored in the console. TTN Console shows no Data for an application and/or its devices, while the application actually does receive data from devices. The disadv…

Use a device to uplink, check your gateway logs, look at the gateway console traffic, look at the device uplinks.

[davidgs]

I have done this. Previously I had 2 gateways, so I powered the other one down (it was working fine, but was indoor-only) and once that one is powered off, I get no connections.

I’m basically trying to run a “Hello World” on an RPiZero. It was able to connect when the indoor gateway is on, but with that powered off, I get:

File "/usr/local/lib/python3.7/dist-packages/rak811/rak811.py", line 401, in join_otaa
raise Rak811EventError(status)
rak811.rak811.Rak811EventError: [Errno 6] Rx2 timeout

There is zero traffic in the gateway logs indicating even an attempt to connect by the client.

[davidgs]

I guess this could be part of the problem

PING us-west.thethings.network (13.66.229.235) 56(84) bytes of data.

--- us-west.thethings.network ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4004ms

whereas:

PING ttn.opennetworkinfrastructure.org (86.119.29.227) 56(84) bytes of data.
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=1 ttl=48 time=112 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=2 ttl=48 time=112 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=3 ttl=48 time=113 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=4 ttl=48 time=114 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=5 ttl=48 time=124 ms

--- ttn.opennetworkinfrastructure.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 112.417/115.480/124.092/4.403 ms

[Jeff-UK]

The TTN back end NS’s are behind load balancers (AWS) so ping doesnt work, am afraid those results dont help you!

[kersing (Jac Kersing)]

@davidgs

There is zero traffic in the gateway logs indicating even an attempt to connect by the client.

If the gateway logs do not list any valid LoRaWAN packets being received you should:

1. Check the frequency plan. Is your gateway listening at the frequencies your node transmits?
2. Check antenna connectors and cable and make sure you connected to right antenna to the right connector. TTOG has multiple connectors and you need to use the right one for the LoRaWAN antenna.
3. Make sure to have the node antenna at least 12 feet away from the gateway antenna. Larger distance is better.

[davidgs]

Sorry it’s taken me a minute to get back to this. I was taking the time to properly install it outside, with the antenna on. proper mast, etc. That’s all done. The gateway now shows up as on-line in the TTN Console.

Success! Nope!

I still cannot send data through that node. I have a RAK indoor LoRA access point, and when that is turned on, my LoRA PHAT on my RPi Zero can send data via that gateway. When I turn that gateway OFF, and attempt to use the TTOG, I cannot send data. I get the message:
Join: at+recv=6,0,0
2020/09/30 18:27:47 failed to send: ERROR-5
And no messages are seen in the log on the TTOG.

I’m really at my wits’ end here!

[cslorabox]

@davidgs

hen I turn that gateway OFF, and attempt to use the TTOG, I cannot send data. I get the message:
Join: at+recv=6,0,0

Turning a gateway off is not valid reason to do a re-join. Really you should just about never re-join.

Get it running with the working gateway and then monitor to see if the other gateway is also reporting signals.

If it isn’t, get gateway specific raw debug output and see what is going on with it.