I’ll be very interested in your results @jvbelle , I only have one and it’s my home (dev) gateway so I’m less inclined to experiment with it (I have enough yaks to shave as it is).
Good luck!
1 Like
No luck over here. Its been a really bad experience using the Laird/TTN combo with basics station. First off, the upgrades/downgrades are really a pain to do correctly. Second, configuring the gateway is also not very convienent using the web config tool of the gateway. Logging is very limited in the UI.
I have tried the most recent tutorial from laird:
https://www.lairdconnect.com/documentation/application-note-setting-basics-station-ttn
But with no success. I cant get my Laird RG186 gateway connected to TTN by using basic station.
Does anybody have tips for me?
One concern of my: does ws port 443 go through my firewall?
That’s disappointing. You turned on the logging on the bottom bar, and dragged it open and said update automatically? The other logging is…terrible (the persistent logging with the same date/time is just annoying, is that fixed yet?)
Maybe paste a link to the log here (gist/pastebin)? I don’t think there’s anything secret in them, but have a look first 
From the log
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | 2021-01-13 20:26:21.583 [TCE:INFO] INFOS reconnect backoff 10s (retry 1) |
|---|---|---|---|---|
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | 2021-01-13 20:26:21.582 [AIO:DEBU] [5] WS connection shutdown… |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | 2021-01-13 20:26:21.567 [AIO:XDEB] [5] ws_connecting state=1 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | 2021-01-13 20:26:21.540 [TCE:INFO] Connecting to INFOS: wss://lns.eu.thethings.network:443 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | 2021-01-13 20:26:21.539 [AIO:XDEB] [5] ws_connecting state=1 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | key usage : Digital Signature, Key Cert Sign, |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | basic constraints : CA=true, max_pathlen=0 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | RSA key size : 2048 bits |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | signed using : RSA with SHA-256 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | expires on : 2021-03-17 16:40:46 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | issued on : 2016-03-17 16:40:46 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | subject name : C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3 |
| RG1xx297A94 | lora | user.notice | Jan 13 20:26:21 | issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3 |
That all looks fine, the right server from what we’re told, and you have a valid cert.
It’s probable the next messages will be the error/timeout. Also check if LoRa/Advanced has Logging Level set to Debug?
It keeps repeating this part over and over again (see bottom):
I cant find an option to set the Logging Level to Debug in the Gatway’s Web UI.
(I dont have remote logging, cant find a manual for that either so im using the logging from the web UI)
| RG1xx297A94 | lora | user.notice | Jan 14 08:22:24 | 2021-01-14 08:22:23.617 [TCE:INFO] INFOS reconnect backoff 60s (retry 8) |
|---|---|---|---|---|
| RG1xx297A94 | lora | user.notice | Jan 14 08:22:24 | 2021-01-14 08:22:23.616 [AIO:DEBU] [3] WS connection shutdown… |
| RG1xx297A94 | lora | user.notice | Jan 14 08:22:24 | 2021-01-14 08:22:23.608 [AIO:XDEB] [3] ws_connecting state=1 |
| RG1xx297A94 | lora | user.notice | Jan 14 08:22:24 | 2021-01-14 08:22:23.582 [TCE:INFO] Connecting to INFOS: wss://lns.eu.thethings.network:443 |
| RG1xx297A94 | lora | user.notice | Jan 14 08:22:24 | 2021-01-14 08:22:23.581 [AIO:XDEB] [3] ws_connecting state=1 |
What cert are you using?
Currently, their FW update URL is
https://connectivity-firmware.s3.amazonaws.com/rg1xx-lora-gateway/firmware/newest/fw.txt