Do you guys have the “Automatically update gateway” checkbox enabled? (TTN/Gateways/Console/Settings). I believe that this might cause the trouble with TTIG.
Edit: I unchecked the box and re-plugged/ rebooted the device. So far it still receives …
Edit2: … and offline again 
1 Like
did not help in my case
it seemed to keep it on a bit longer today ong that but now when its on downlinks are not processing corectly .
its about to go back in its box and be returened as not fit for function.
Thanks to the slack channel, a possible explanation:
Unplug, wait more than 600 seconds, replug.
Looks like that short power cycles may cause trouble …
3 Likes
The keepalive was recently extended from 60 to 600 secs which helps make up GW’s more resilient from WS disconnects, but now means a longer wait before restart if they go down?! Also this is lousey problem to deal with if gateway is ‘remote’ as no way to shutdown and restart to recover, simply forcing a reboot would seem not giving enough time so may need to engineer some kind of long period power supply turn off/turn on solution (a node driving a relay? but how to command if the TTIG is the only GW in range?! 
)
1 Like
Yes, and apparently introducing problems to people for whom the 60 seconds setting was shorter than an automatic daily reset of their internet connection, but the 600 seconds is troublesome.
I also have the same problem with 4 TTiG that won’t connect to the TTN:
EUI_ 58A0CBFFFE801DDD
EUI_58A0CBFFFE801E98
EUI_58A0CBFFFE801EFF
EUI_58A0CBFFFE801DCB
they all 4 got a MAC APP address starting with 2C:…
3 other ones work fine they got MAC APP addresses starting with CC:…
All off them are registered on TTN via console gateway.
How can help me? Greetings Frans
Channelling @arjanvanb, here’s a recent thread on the matter:
If they are already registered on TTN or not correctly provisioned, you’ll need to mention a TTI staff member, as you will see was done in that thread.
@descartes: In this particular issue, these gateways are correctly provisioned by the manufacturer. Seems like something else. @WSVV1 is discussing with me on a private thread. Thanks for the redirect. 
1 Like
How can i test with you this issue. Teams video conference or here? I don’t know what is the problem and if i have to sent them back to RS were bougth them.
HELP! My TTIG (TBMH100) never goes to solid-green. I did the setup and it connects to my WiFi base station and receives an IP address (confirmed from the base station that it sees the TTIG, and I can ping the TTIG), but it just fast-blinks green (and occasionally momentarily blinks green/red)- it NEVER goes to solid-green. I tried re-doing the setup twice, in which I deleted my WiFi network and re-added it, but I get the same result each time- it goes to fast-blink green. I yanked it out of the wall and plugged it back in, but I get the same fast-blink-green. No firewalls or weird network, just a typical Linksys WiFi router doing NAT to the Internet, that works fine for lots of other devices on my network.
I added it into the TTN Console, but since the gateway never goes to solid-green, I don’t expect it to work. (It shows “Last seen: ”.)
MY 915MHz unit, bought at Adafruit:
MFG date: 2020-01-04 07:23:01
FW Build: 2018-12-06 09:30:37
FW Version: 2.0.0
Core Version: 2.0.0(minihub/debug)
Copyright (c) 2018 Semtech Corporation. All rights reserved.
Hey Eric. What’s the EUI?
Gateway EUI: 58-A0-CB-FF-FE-80-2C-7C
Thanks in advance.
Ok, this is weird. I didn’t change anything, but my TTIG is now (finally) showing a solid-green LED, and it apparently connected, according to the console:
Last Seen: 11/18/2020 02:22:29
I hope it stays this way!
My TTN gateway was up for more than a week but suddenly I stopped working since yesterday 2:02PM.
Light is still solid green but it says it’s not connected. More people who have this problem?
eui-58a0cbfffe802ee8
Thanks in advance
Stopped working as in does not forward any packets or just does not show connected in the console?
It’s not connected in the console. Didn’t do anything with it yesterday so it just lost connection.
Tried restarting it multiple times and connecting it again to the WiFi but it’s still not working.
Do you have an active node close (but not too close) to the gateway? Active LoRaWAN traffic should result in the gateway being listed active in the console.
There are two nodes close to the gateway, a light sensor en an CO2 sensor with PIR. The CO2 sensor is new. But the light sensor is 2 weeks old and was working fine with the gateway.
Same for me, status not connected, rebooted but not connected.
Not connected from yesterday, reachable via ping same wifi network
