TTIG "not connected"

Hi All,

I have a very strange problem that may be related to this. My TTI Indoor Gateway, eui-58a0cbfffe802629, only reports a momentary connection when I reboot it. Then it will time out and get marked not connected. My applications are still reporting traffic through that particular gateway on TTN Console and the stats display on TTN mapper. TTN console never sees gateway traffic. This was not always the case, my stats are stuck at Received Messages 30318 and Transmitted Messages 3199. This began a couple of weeks ago. Nothing that I can do at my end resolves the problem. I have tried a factory default, connection to other TTN routers throughout the world. I am normally connected to ttn-router-us-west since I am located in California USA.

I see many similar reports that go back to 2019 but no reports of the actual cause or a solution.
There is some discussion comments that go like this, " If you invest some time you can read the BasicStation back-end protocol is not supported by TTN Community Network V2. It will be by TTN V3."
and this,

"Reason:
As some of you might know, our V2 stack does not support the new BasicStation protocol and hence we have a temporary/experimental BasicStation-Bridge that bridges the TTIG to our V2 routers. This bridge is functional but breaks at scale which is what’s happening here). I have added some load-balancing in the backend which should keep it functional.

In the next few weeks, we will be replacing this bridge with a native, highly scalable component which will ensure that these kinds of outages don’t happen." – July 2019.

Is there a back end outage to the BasicStation-Bridge? Or a bug from a recent update?

This is a real problem if you are using TTN Mapper and you need to reboot your gateway every 5 days to prevent its deletion from the map.

Did you see the post above yours?

I do. I am really wondering if there is something here that needs more attention than just the TTN console. Is TTN Mapper just pulling its data from TTN Console via the API? Is the problem related to the new protocol used with the Indoor Gateway? Is it the TTN Console? Is there something that I might have missed that I could do to fix this? Please remember that I saw a similar discussion a year ago so I am really trying to see if I missed something at my end. Any help and advice would be welcome. Thanks.

No there is not. There are known issues with gateway state in the console which are not related to the protocol used to connect the gateway to the back-end.
TTN Mapper currently relies on the same data set because querying the status of all known (to TTN Mapper) gateways takes too much time. (Search the forum and you will find messages concerning this.)

You can head over to the TTN slack #ops channel and shout out hoping someone will be able to reset whatever isn’t working right.

Thank you for the suggestion. I posted the request.

Please do not expect a response - it’s been made clear (above and all over other forum posts) that this is not going to be fixed.

1 Like

Not going to ever be fixed – Or is the expectation that TTN V3 is the fix?

It won’t be broken in v3 but it may be different!

We have a known issue related to our v2 “NOC” service that sometimes shows online gateways as offline. We are not going to fix this issue.

Another known issue is that Basic Station gateways experience websocket timeouts. This is fixed in the new 2.0.4 and 2.0.5 firmware versions that are currently being tested. Maybe @KrishnaIyerEaswaran2 can comment on this.

And as @descartes just wrote: in v3 things will be different.

3 Likes

@htdvisser, @johan
It will be nice to have available a brief, easy readable introduction to V3, with a comparison between V2 and V3, so users can get an idea of what V3 will mean for them in practice and what they would need to do to prepare for it. Without having to do a deep dive and read all V3 tech specs first.

Does such a document currently exist?

https://thethingsstack.io/latest/getting-started/migrating-from-v2/major-changes/ would be a good place to start.

1 Like

Hello, My eui-58a0cbfffe80294b TTIG-868 disconnects also after one hour, and becomes not visible on TTNmapper. Best reg, Peter

A post was split to a new topic: Gateway is active, but not shown on community map

Hello, I have exactly the same problem with a TTIG gateway, how could it be solved?
This is my serial log:

1970-01-01 00:00:02.150 [SYS:INFO] FSCK found section marker A0
1970-01-01 00:00:02.156 [SYS:INFO] FSCK section A: 22 records, 5960 bytes used, 1018040 bytes free
1970-01-01 00:00:02.622 [SYS:INFO] FSCK section A followed by erased flash - all clear.
1970-01-01 00:00:02.636 [any:INFO] HW pipe bound with fd=0
1970-01-01 00:00:02.638 [any:INFO] AIO registered for HW pipe &aio=0x3ffeea30

1970-01-01 00:00:00.006 [SYS:DEBU] ======= VER ======
1970-01-01 00:00:00.008 [SYS:DEBU] Station Version 2.0.0(minihub/debug)
1970-01-01 00:00:00.010 [SYS:DEBU] Version Commit e17c5af
1970-01-01 00:00:00.014 [SYS:DEBU] Station Build 2018-12-06 09:30:37
1970-01-01 00:00:00.020 [SYS:DEBU] Firmware Version 2.0.0
1970-01-01 00:00:00.025 [SYS:DEBU] FW Flavor ID semtech0
1970-01-01 00:00:00.031 [SYS:DEBU] Model minihub
1970-01-01 00:00:00.036 [SYS:DEBU] ======= SYS ======
1970-01-01 00:00:00.041 [SYS:DEBU] CPU Freq 80 / 80000000 / 80000000
1970-01-01 00:00:00.049 [SYS:DEBU] Random Number 1565773158
1970-01-01 00:00:00.053 [SYS:DEBU] Reset cause 0
1970-01-01 00:00:00.058 [SYS:DEBU] Booting USER_BIN 1
1970-01-01 00:00:00.063 [SYS:DEBU] FW start addr 0x00001000
1970-01-01 00:00:00.069 [SYS:DEBU] SDK version 2.0-dev(9ec59b5)
1970-01-01 00:00:00.075 [SYS:DEBU] Free Heap Startup 56160 bytes
1970-01-01 00:00:00.081 [SYS:DEBU] ======= MFG ======
1970-01-01 00:00:00.086 [SYS:DEBU] SN TBMH100915003682
1970-01-01 00:00:00.092 [SYS:DEBU] MTIME 2020-04-24 09:48:49
1970-01-01 00:00:00.098 [SYS:DEBU] PERSO_HASH 0xf22aa5bf
1970-01-01 00:00:00.108 [SYS:DEBU] AP_PW 9FD3oqHn
1970-01-01 00:00:00.110 [SYS:DEBU] AP MAC 58:A0:CB:80:31:72
1970-01-01 00:00:00.115 [SYS:DEBU] EUI 58-A0-CB-FF-FE-80-31-72
1970-01-01 00:00:00.122 [SYS:DEBU] STA MAC DC:4F:22:64:89:5B
1970-01-01 00:00:00.128 [SYS:DEBU] ======= CRD ======
1970-01-01 00:00:00.136 [SYS:DEBU] [cups] auth=3 -> https://mh.sm.tc:7007
1970-01-01 00:00:00.140 [SYS:DEBU] type=0 -> /s2/cups.trust
1970-01-01 00:00:00.145 [SYS:DEBU] type=2 -> /s2/cups.key
1970-01-01 00:00:00.152 [SYS:DEBU] [cups-bak] - not available
1970-01-01 00:00:00.159 [SYS:DEBU] [cups-boot] auth=3 -> https://mh.sm.tc:7007
1970-01-01 00:00:00.168 [SYS:DEBU] type=0 -> /s2/cups-boot.trust
1970-01-01 00:00:00.170 [SYS:DEBU] type=2 -> /s2/cups-boot.key
1970-01-01 00:00:00.176 [SYS:DEBU] [tc] - not available
1970-01-01 00:00:00.181 [SYS:DEBU] [tc-bak] - not available
1970-01-01 00:00:00.187 [SYS:DEBU] [tc-boot] - not available
1970-01-01 00:00:00.190 [SYS:DEBU] ======= MEM ======
data : 0x3ffe8000 ~ 0x3ffe8cd8, len: 3288
rodata: 0x3ffe8ce0 ~ 0x3ffe8f70, len: 656
bss : 0x3ffe8f70 ~ 0x3fff0420, len: 29872
heap : 0x3fff0420 ~ 0x40000000, len: 64480
1970-01-01 00:00:00.210 [SYS:DEBU] ==================
1970-01-01 00:00:00.221 [SYS:DEBU] Start WiFi Scan
1970-01-01 00:00:01.215 [SYS:DEBU] Free Heap: 55432 (min=55056) wifi=0 mh=1 cups=0 tc=0
1970-01-01 00:00:02.218 [SYS:DEBU] Free Heap: 55240 (min=55056) wifi=0 mh=1 cups=0 tc=0
scandone
1970-01-01 00:00:02.646 [SYS:DEBU] mh_scanDoneCB: status=0
1970-01-01 00:00:02.648 [SYS:DEBU] SSID | CH @ RSSI | auth | b/g/n | wps
1970-01-01 00:00:02.650 [SYS:DEBU] EPEAS | ch-01@-72 dBm | auth=3 | 1/1/1 | 0
1970-01-01 00:00:02.657 [SYS:DEBU] EPEAS_GUEST | ch-01@-72 dBm | auth=3 | 1/1/1 | 0
1970-01-01 00:00:02.665 [SYS:DEBU] Proximus-Home-6AC0 | ch-01@-83 dBm | auth=3 | 1/1/1 | 1
1970-01-01 00:00:02.673 [SYS:DEBU] Proximus Public Wi-Fi | ch-01@-81 dBm | auth=0 | 1/1/1 | 0
1970-01-01 00:00:02.682 [SYS:DEBU] Things-Gateway-001EC03B4145 | ch-06@-40 dBm | auth=3 | 1/1/1 | 0
1970-01-01 00:00:02.690 [SYS:DEBU] EPEAS | ch-11@-57 dBm | auth=3 | 1/1/1 | 0
1970-01-01 00:00:02.699 [SYS:DEBU] EPEAS_GUEST | ch-11@-56 dBm | auth=3 | 1/1/1 | 0
1970-01-01 00:00:03.221 [SYS:DEBU] Free Heap: 55816 (min=55016) wifi=0 mh=2 cups=0 tc=0
1970-01-01 00:00:03.224 [SYS:DEBU] WiFi connecting to ‘EPEAS_GUEST’
1970-01-01 00:00:03.226 [SYS:DEBU] Setting up hostname: MiniHub-803172
1970-01-01 00:00:03.231 [SYS:INFO] DHCP is not started. Starting it…
1970-01-01 00:00:04.224 [SYS:DEBU] Free Heap: 55816 (min=55016) wifi=1 mh=3 cups=0 tc=0
1970-01-01 00:00:05.227 [SYS:DEBU] Free Heap: 55816 (min=55016) wifi=1 mh=3 cups=0 tc=0
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 5
pm open phy_2,type:2 0 0
cnt

connected with EPEAS_GUEST, channel 11
dhcp client start…
1970-01-01 00:00:06.230 [SYS:DEBU] Free Heap: 54800 (min=53288) wifi=1 mh=3 cups=0 tc=0
ip:172.16.30.10,mask:255.255.255.0,gw:172.16.30.1
1970-01-01 00:00:07.234 [SYS:DEBU] Free Heap: 54800 (min=53288) wifi=5 mh=3 cups=0 tc=0
1970-01-01 00:00:07.244 [CUP:INFO] Stopping TC and starting CUPS
1970-01-01 00:00:07.246 [CUP:INFO] Starting a CUPS session
1970-01-01 00:00:07.254 [CUP:INFO] Connecting to CUPS … https://mh.sm.tc:7007 (try #1)
1970-01-01 00:00:07.265 [any:INFO] cert. version : 1
serial number : 01
issuer name : CN=Root CA, OU=TrackCentral (ez5Cj0eN), O=TrackNet.io, C=CH
subject name : CN=Root CA, OU=TrackCentral (ez5Cj0eN), O=TrackNet.io, C=CH
issued on : 2018-11-22 10:23:38
expires on : 2024-11-20 10:23:38
signed using : ECDSA with SHA256
EC key size : 256 bits
1970-01-01 00:00:07.291 [AIO:INFO] cups has no cert configured - running server auth and client auth with token
1970-01-01 00:00:07.349 [CUP:VERB] Retrieving update-info from CUPS https://mh.sm.tc:7007
1970-01-01 00:00:13.892 [SYS:DEBU] Free Heap: 26152 (min=26152) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:14.897 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:15.901 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:16.905 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:17.909 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:18.912 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:19.916 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:20.920 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:21.924 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:22.928 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:23.932 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:24.936 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:25.941 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:26.945 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:27.949 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:28.953 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:29.958 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:30.962 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:31.965 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:32.969 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:33.973 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:34.977 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:35.981 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:36.985 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:37.989 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:38.998 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:40.002 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:41.006 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:42.010 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:43.014 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:44.018 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:45.022 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:46.026 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:47.030 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:48.034 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:49.038 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:50.041 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:51.045 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:52.049 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:53.054 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:54.058 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:55.061 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:56.065 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:57.071 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:58.075 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:00:59.079 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:00.083 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:01.087 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:02.091 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:03.095 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:04.099 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:05.103 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:06.107 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:07.111 [SYS:DEBU] Free Heap: 32888 (min=25936) wifi=5 mh=7 cups=1 tc=0
1970-01-01 00:01:07.348 [CUP:ERRO] CUPS timed out
1970-01-01 00:01:07.355 [SYS:INFO] sys_inState - Ignoring state transition: 5
1970-01-01 00:01:07.358 [CUP:INFO] Interaction with CUPS failed - retrying in 1m
1970-01-01 00:01:07.360 [TCE:INFO] Starting TC engine
1970-01-01 00:01:07.365 [TCE:ERRO] No TC URI configured
1970-01-01 00:01:07.376 [TCE:INFO] INFOS reconnect backoff 0s (retry 0)
1970-01-01 00:01:07.379 [TCE:ERRO] No TC URI configured
1970-01-01 00:01:07.381 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
1970-01-01 00:01:08.115 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:09.118 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:10.121 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:11.130 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:12.134 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:13.137 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:14.140 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:15.144 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:16.147 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:17.151 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6
1970-01-01 00:01:17.382 [TCE:ERRO] No TC URI configured
1970-01-01 00:01:17.384 [TCE:INFO] INFOS reconnect backoff 20s (retry 2)
1970-01-01 00:01:18.154 [SYS:DEBU] Free Heap: 47704 (min=25936) wifi=5 mh=7 cups=-3 tc=6

Thanks

I haven’t put a serial output on mine, but I would expect the date & time to be correct if it was on WiFi.

But you should also consider:

I have a gateway that is forwarding packet with a status not connected. eui-e58a0cbfffe8027d
http://noc.thethingsnetwork.org:8085/api/v2/gateways/eui-e58a0cbfffe8027d
returns message
{“error”:“status not found”,“message”:“status not found”,“code”:5}

The SSL cert on the checking link has probably expired. I deleted the http(s) and have information from a Gateway that has status not connected.
http://noc.thethingsnetwork.org:8085/api/v2/gateways/eui-58a0cbfffe8027c4 provides information
{“timestamp”:“2020-11-12T06:20:44.929881175Z”,“location”:{},“frequency_plan”:“EU_863_870”,“platform”:“minihub - Firmware 2.0.0 - Protocol 2”,“gps”:{},“time”:“1605162044929881175”}

The failure of gateways correctly register is frustrating as am making R&D with a view to large roll-out of LoRaWAN devices and replacing traditional modem comms in both water data loggers and electric meters.

Is that EUI a typo? There shouldn’t be an ‘e’ in front of the 58. Did you use the right eui while registering?

Definitely a typo.
indoor gateways gateways Nov 2020 indoor gateways gateways Nov 2020

2 out of 4 gateways not registered on the Things Network (although sending data packets)

If the gateways are forwarding packets you might have encountered the issue that the console does not always correctly reflect the gateway connection state. Another option is a typo in the EUI when registering it. Unregistered gateways will forward data.
For instance your Washington2 gateway id doesn’t look right.