If you switch off gateway for a long time and start it. it gets connected to ttn console once.
But after that it fails (ie the last seen time increases) My lorawan card is warm but not hot, it’s inside it’s normal working temp I think.
Some questions what does reboot reason 0x13 mean?
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 917719b9, timestamp: 1498499973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jun 26 2017 19:59:53
Reboot reason: 0x13
Maybe this is a valid reason, but some time after that it reboots in the middle of the test CNFG: Load onlin (notice it’s truncated) it does this every time at same spot.
CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CNFG: Load onlinSNTP: State change from 0 to 0
Looking at that last line, could it also be NTP related? Maybe it corrects the time wrongly (too big step or backwards) after the first reboot causing a software error or watchdog issue.
Will try to block the request and see. Maybe SNTP doesn’t stand for Simple Network Time Protocol in this case? We need the sourcecode in a github repo!
Thank you for the great project! I was happy to get my packages in the mail this week (through Skynet), and couldn’t wait to unbox the gateway, uno’s and node.
Unfortunately, I haven’t be able to connect to the TTN network yet. As a few others mentioned above, I am able to connect it to my local WIFI network (and after that, i’m even able to connect to read out the /info page on the by our DHCP provider ip adress of the gateway), but it enters a reboot loop after the third LED started blinking for a few seconds, stops, and then all LEDS start to blink and the gateway starts to reboot.
I’m waiting for my UART cable to get some more information from the serial port.
For now: i’m not in a hurry, I wish you a good conference, but if you need me for some testing, just know that i’m there to supply extra debug information or to test any new firmware builds (if that would be a solution).
Welcome to the club of backers who made this all possible in the first place but must wait for support.
Perhaps we need to find a good banner maker, and organize a protest outside the conference!
I want to fill this hole in the TTN coverage in my neighborhood for some years now…
Enabling “Beta Updates” in TTN Console does not show anything different than my earlier log. In other words: I don’t see it trying to download the firmware, maybe as it never successfully completed Step 4 of its initial activation.
Also, erasing the serial flash (holding down the “mode” button while powering up) and then using ethernet rather than WiFi in Step 3 of https://activate.thethingsnetwork.org, makes no difference: I still see it fetching some frequency configuration from the internet, soon followed by LORA: Configuration failed, retry (sometimes two times) and then rebooting.
Unlike I thought earlier, the reboot reason is not only Reboot reason: 0x13 but often shows Reboot reason: 0x53. I don’t know which one is shown why.
In the earlier and today’s log I noticed HTTP: Got 1232 bytes (I assume decimal?) for both WiFi and ethernet in:
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
Of course, maybe those lines in the log are very much unrelated. Or maybe the gateway gets it in some gzip’d transfer encoding, while my Chrome does not.
…apparently being the following, which I don’t know how to use:
------- Supported command groups ------
*** tcpip: stack commands ***
*** wifi: Wi-Fi commands ***
---------- Built in commands ----------
*** reset: Reset host ***
*** q: quit command processor ***
*** help: help ***
Did you find something more?
And some asides:
For WiFi I use an XS4ALL FRITZ!Box modem. This supports IPv6 but the gateway does not seem to use that, or prefers IPv4. The gateway’s information page can be reached at both http://things-gateway/info and http://things-gateway.local/info
For ethernet, I use some Ziggo/UPC Technicolor modem, IPv4 only. Its DNS needs the .local suffix; the gateway can only be reached at http://things-gateway.local/info
When using ethernet, it seems the activation JavaScript relies on things-gateway.local to resolve.
The http://things-gateway.local/info page will keep refreshing its details depending on its internal state. Like: “Config correct” might first show “false” but “true” later, “Region” might be empty first but become “EU_863_870”, and “Gateway Card” might change from “ND” (not detected?) to “868Mhz”.
When trying to use the Ziggo ethernet while the XS4ALL WiFi was still configured, the ethernet’s DHCP would just be too slow for the gateway to get a lease, so it would choose WiFi instead.
I am using PlatformIO on a Mac to append the serial output to a file, while prepending a timestamp to each line (and adding a date to the name of the log file). Like: LOG="ttn-gateway-`date +'%Y%m%d-%H%M%S'`.log"; pio serialports monitor --raw -b 115200 | while read l; do echo "[`date +'%F %T'`] $l" | tee -a $LOG; done
I am using a Raspberry Pi to save the serial output to a file, while prepending a timestamp to each line.
Ah, I figured I needed to prefix commands with tcpip or wifi, but no. As help tcpip shows the following, one can just enter those commands without the prefix:
*** netinfo: Get network information ***
*** defnet: Set default network interface ***
*** dhcp: DHCP client commands ***
*** dhcps: Turn DHCP server on/off ***
*** zcll: Turn ZCLL on/off ***
*** setip: Set IP address and mask ***
*** setgw: Set Gateway address ***
*** setdns: Set DNS address ***
*** setbios: Set host's NetBIOS name ***
*** setmac: Set MAC address ***
*** if: Bring an interface up/down ***
*** stack: Stack turn on/off ***
*** heapinfo: Check heap status ***
*** dhcpsinfo: Display DHCP Server Lease Details ***
*** ping: Ping an IP address ***
*** arp: ARP commands ***
*** dnsc: DNS client commands ***
*** macinfo: Check MAC statistics ***
Like: ping google.com:
Ping: resolving host: google.com
Ping: request sent to: google.com [172.217.20.78
Ping: reply from 172.217.20.78: time = 8ms
Ping: reply from 172.217.20.78: time = 7ms
Ping: reply from 172.217.20.78: time = 6ms
Ping: reply from 172.217.20.78: time = 6ms
Ping: done. Sent 4 requests, received 4 replies.
It’s a bit hard to type the command while it’s rebooting all the time, and to read the output between the regular log lines. But: might be useful indeed!
Hi There,
Received my GW, was hoping as read here to have setup in less than 5 min (not my 1st GW setting, but first one with the TTN one) :
First boot, 1st led fix, 2nd fast blink, great expected, so I went to TTN install portal but stuck to connect to GW
Ok let’s see, OMG no Wifi AP seen on my Computer Windows 10, ok let’s see with my mac, same thing, my iphone, same thing, Wifi AP does not seem to start (or at least seen), power off then GW Power on with reset switch, to force AP, same thing no WiFi!
Ok plug Ethernet cable into GW, TTN portal see gateway and continue configuration, I setup to use Wifi, My Office Wifi is seen by setup, I select it and put password.
GW configuration is continuing GW seen on console, everything works. got it !
Remove Ethernet cable, reboot the GW to be sure and it’s down, 1st led fix, 2nd slow blink heuuuuu
Ok, needed to wait some minutes, but that’s it all is working
Anyway, just amazing I never saw the GW as an AP as setup mention, if anyone is experiencing this, just plug network cable, will remove you some headache
Yesterday the gateway arrived - but unfortunately, same story here. Initial setup through wifi - ending up in boot loop. Second try using ethernet, same story - also after full reset. The device does register on the local network, below the screenshot of the /info page - and also of the console, showing the device never managed to connect. Hoping for a solution as much as everyone else here!
I can’t get my gateway ready to work. After resetting, everything look to go smooth including configuring the gateway. But after a short while, it keeps rebooting. Also no packets are being sent.
Tried to reseat the lora board, but no success. See my configuration page of the gateway that looks correct during some time between reboots.
In TTN they ought to be able to see how many people are registering a Gateway, and how many Gateways are successfully connecting… so as to get a view on the scale of the problem. Most people posting here are posting messages of frustration, but it’s hard to tell if DOA (also known as ‘doorstop’) is the norm or the exception…
Yes, please. Many have asked, and that list alone might be so helpful, if only to decide to just wait rather than spending time trying to decipher the serial output (like what does HTTP: Got 1232 bytes refer to?), or rather than trying all kinds of different ways to activate the gateway.
Why does it take TWTG more than 40 days to publish that list?
When ready earlier, please, please just publish it and not wait for the conference? There are many smart people around here who might find the flaw that makes some/many gateways reboot—I’d say that such would make an even better announcement at the conference!
Some people here might even find a fix, if the following is documented too:
Not sure if useful to others, but I activated my gateway entirely by Wifi using the latest version of win10 as follows:
N.B. If something has gone wrong, then I understand you can reset it to factory before trying this again?
Preparation.
Use a win10 computer that is wifi enabled (Don’t connect via ethernet)
Using your Win 10 computer, “Forget” the Wifi connection and reconnect making sure your wifi connection for broadband is ticked to connect automatically and looks for anything on the network
Attach the antenna and switch the gateway on where it can get a good wifi signal with your broadband router. N.B. When it powers up, the gateway is first in AP mode (you will see it listed in your computer’s Wifi connections).
Right so now what?
The first thing you do, is go to the TTN activate page (via your broadband - gateway not involved yet)
Follow the initial instructions on the TTN web page and at some point, it will display a password It is at this point that you go to your computer’s WIfi connections and sign into the gateway wifi AP using the password you have just been given,
The TNN Web page will advance to the next step and you will be prompted to give the broadband SSID and password that your computer is using.
Once you have pressed continue, the info will be passed to the gateway and then it will then reboot (it will dissappear from your Wifi list). 2 things will happen - your computer will now reconnect back to your broadband and the gateway will no longer be an AP (because it will try to sign into your broadband SSID)
If your gatway connects to your broadband OK - then hopefully, the rest of the process should be OK
In the TTN console, switch off “automatic updates” for your gateway
Once all set up. switch off your gateway and install where you want to put it. When you power it up next, the gateway should now aiutomatically connect to give you 4 LEDS
Hi, guys (@htdvisser, @rish) , also checking in to report a similar reboot loop issue as reported elsewhere in this thread.
Although I managed to register / activate my (finally!) received TTN gateway relatively easy, it will maintain a stable connection only for some 5-10 minutes and then will spontaneously reboot. After a few iterations it may become stable again for a short while and then enter the reboot loop again.
Any assistance / progress reports regarding this issue would be appreciated.
However you can then run 
