no idea what the reason is… I only noticed that for the last days they happen less so that’s an improvement.
and the gw always reconnects so I only can see it looking at the gw status page Uptime
I try to build a wireless solution for the UART debug info so I can see that in a browser to.
Hang fire - folks are working on this. Do you have a Pickit or serial interface that you could connect to the box to analyze what is happening?
thanks for your reply.
Sorry, no pickit or serial device available.
Still not able to pass step three in activating the gateway.
Connected via Ethernet now.
Sometimes three led burning
Third led starts blinkking (gently).
Third led switches off
Two leds are still on and then all leds switch off.
Looks like some sort retry proces in activating.
My two gateways were working fine on 1.0.3 beta firmware for the last 5 days or so, even with the occasional power cycle. But as of yesterday they both keep restarting. They seem to eventually get a broker connection, but it doesn’t stay up and then they restart. I wonder if there is a backend issue?
Same here. Keep in touch.
Sounds like the dreaded reboot loop.
As you said you cannot peek into the serial log: maybe boldly upgrade using a microSD card? See gateway/firmware at master · TheThingsProducts/gateway · GitHub (and http://things-gateway.local/info on the same network as your gateway to see the current version you’ve got).
For me, the factory June 2017 firmware got me the reboot loop, the March 13th 1.0.1 worked fine (with other problems), the March 15th 1.0.2 got me the reboot loop again, and the March 22nd 1.0.3 seems fine again. (Today, the beta gives one 1.0.3.)
If you happen to have a Raspberry Pi lying around (or one doing other things) then you can connect that as well. See, e.g., my GitHub - avbentem/raspi-uart-monitor: Monitors a Raspberry Pi UART, logging to rotating files and posting important events and basic reports to Slack and/or Telegram. (which can also alert you through Telegram and/or Slack).
Hi Arjan,
Thanks a lot! An updated firmware via SD-card did the trick.
Firmware March 15th still gave issue’s. When updated to beta formware March 22th, Iwas able to connect the gateway succesful.
Léon
After pressing “Configure Gateway” Button, still getting error message:
Request has been terminated.
Possible causes the
Network is offline, Origin is not allowed by Access-Control-Allow-Origin
15 March Build (see below)
MON: SYS Stack size: 3959
MON: heap usage: 150KB (158KB), free: 189KB
BTN: change to state: 1
BTN: change to sta
*** Application reboot
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
G A T E W A Y *
Firmware name: AmazingAckermann, type: 0, version: 1.0.2, commit: 475aef56, timestamp: 1521108973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 15 2018 10:16:33
Reboot reason: 0x40
BOOT: (persisted info) 6F 72 72 65 01 03 76 45 9E 2F 09 28 94 1D 65 DA
WIFI: Entering state 0
WIFI: Entering SCAN state 0
MAIN: Initialisation complete
LORA: Changing state from 0 to 0
MAIN: Leaving state 0
MAIN: Entering state 1
FLASH: Magic bytes not found: no stored wifi config present
FLASH: Magic bytes not found: no stored activation data present
FLASH: Magic bytes not found: no stored FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
MAIN: Leaving state 1
MAIN: Entering state 2
INET: State change to 0
INET: No Ethernet and no WiFi config
INET: State change to 1
LORA: Initialisation complete
LORA: Changing state from 0 to 1
WIFI: Entering state 1
ETH: IP Address: 0.0.0.0
WIFI: Entering state 4
WIFI: Entering SCAN state 1
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
WIFI: Entering state 3
SNTP: State change from 0 to 1
WIFI: Entering state 4
WIFI: Entering SCAN state 1
INET: State change to 0
INET: Gateway has Ethernet
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
SNTP: State change from 1 to 2
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 3
Head magic match void: trying to free an already freed block, ignore
SNTP: State change from 2 to 1
WIFI: Entering SCAN state 4
ETH: IP Address: 192.168.1.75
SNTP: State change from 1 to 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 5
WIFI: Enabling modules for server
WIFI: Entering state 6
WIFI: IP Address: 192.168.84.1
CB: INET: State change to 3
INET: Ping probe
INET: Error sending probe on WiFi
INET: Ping response from PIC32INT, set as default
INET: State change to 4
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
SNTP: State change from 2 to 3
MON: SYS Stack size: 3959
MON: heap usage: 147KB (157KB), free: 192KB
SNTP: State change from 3 to 4
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5
MAIN: Leaving state 2
MAIN: Entering state 3
CNFG: Load online user config state change to 0
MON: SYS Stack size: 3959
MON: heap usage: 148KB (157KB), free: 192KB
MON: SYS Stack size: 3959
Still unable to configure after updating to beta via SD card with same error via WiFi and Ethernet
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1521721252
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 22 2018 12:21:52
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 76 C5 9F 6F 29 00 9C 1D 75 DA
Is that the “Mode” button inside the gateway? If yes, that is resetting the gateway. Why are you pressing that? Just click the green “button” in the browser instead.
Arjan: Thank you for your reply
After Connecting to WiFi 
I pressed the Configure Gateway button: 
and immediately get an error message from the browser: 
Where to get “firmware.hex” for this v1.0.3-2c56ce09?
Correct
I recently downgraded my gateway to version “v1.0.2” and installed version “v1.0.3” using the SD-card. For this first time I thought that I had broken my gateway. This combination did not work and I had a Christmas tree of blue blinking lights.
After removing the SD-card and power cycling, the gateway came back to life.
Until now I have no good experiences with version “v1.0.3”
In my experience its more stable, however it reboots min.once a day but always reconnects to the backend.
I just downloaded firmware.hex from brach stable from the link you provided.
The boot log shows the version is 1.0.2, commit: 475aef56.
Am I missing something?
I saw this too at first, but unfortunately now I am seeing the opposite.
One of my gateways doesn’t reboot at all (it stays up for days, at least till I power cycle), connects to the broker, but the broker connection doesn’t stay up overnight. The other one reboots regularly, occasionally connecting to the broker - but only for a few minutes. Neither is really usable.
Strangely in the console the first one shows as “not connected” and “last seen yesterday”, where the second one shows “connected” but “last seen 19 hours ago”. Not sure what the timeout on “connected” is, but 19 hours seems a bit long?
You want to download the hex file for the beta branch for 1.0.3.
Well maybe not if you see the same issues as me… 