TTN Indoor Gateway 1/4 green LED flash. Setup Peformed Coorectly as guided

I am having issues with TTN indoor Gateway 868-eu. I have followed the 5min setup quick start guide. And followed it exactly, however, the device is not connecting to the LNS. The green led flashes 1/4 per second and occasionally red/green. This happened on the first GW i bought and is repeating the same on the second.
Is there a problem that I’m missing?


Did you ever get the first gateway working? If yes: how?

Maybe validate that it has been provisioned by the factory/manufacturer/supplier:

(Or post your gateway ID here if you need help with curl.)

I’m having the same issue as @CDonohoe.

Set it up, I can see it connect to my router, get an IP and then constant green flashing 1/4 per second then after a while green/red flashes then back to green 1/4 second.

I tried the curl POST request trick to see if there is something up with my gateway’s backend config. All I get is the following, and that is after a good couple of minutes waiting.

curl -k -i -X POST --data '{ "router": "58-A0-CB-FF-FE-80-31-B1" }'

HTTP/1.1 401 Unauthorized
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Date: Tue, 20 Oct 2020 06:49:49 GMT
Server: Python/3.6 aiohttp/3.5.4
Connection: close

HSM timeout

I’ve performed a few power cycles with no luck. I am now trying the setup again but using my phone’s hotspot instead of my house internet, just in case.

My devices details are:

Gateway EUI58-A0-CB-FF-FE-80-31-B1
WiFi AP MAC 58:A0:CB:80:31:B1
WiFi STA MAC DC:4F:22:64:89:EB
Serial Number  TBMH100915003745
MFG date  2020-04-24 07:58:35
FW Build  2018-12-06 09:30:37
FW Version2.0.0
Core Version2.0.0(minihub/debug)

I’m just about ready to give up on it. I am terribly disappointed by it (and the lack of a simple diagnostics log/webpage)

1 Like

Maybe not getting a 404 Not Found (along with its “Not Provisioned”) actually indicates it is known, hence has been provisioned just fine? (And would need some authentication in that curl command, but that’s not important for this first check?)

(Using a random value in "router" gets me that 404 all right.)

I partly agree to arjan.
It seems that they protected the HTTP endpoint by some kind of authentication. I’m not aware how to cicurmvent this. But I can tell, that I receive the same HSM timeout when I try to check your EUID. When i do the same with my already provisioned gateway, I receive this:

HTTP/1.1 401 Unauthorized
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Date: Tue, 20 Oct 2020 11:58:07 GMT
Server: Python/3.6 aiohttp/3.5.4
Connection: close

Wrong Token

So I guess there is something wrong with the registration of your device, but I cant tell for sure.

1 Like

@ttnkufstein and @CDonohoe
Why are you making requests to That server requires an auth that’s directly embedded into the gateway.

The gateway 58-A0-CB-FF-FE-80-31-B1 is configured to wss://
This gateway has not been seen by the CUPS server. This means that there is most likely a connectivity issue.

Just to clarify, is your WiFi setting correct?

I believe my WiFi settings are correct. I go through the setup process and I can ping the device on my network.

@matqua: Can you connect your gateway now? I’ll check what’s happening in the backend

Update: I just looked over at it and the LED is solid green and it was last seen 6 minutes ago on the console.

Same settings all day and now its on.

Well, I asked @matqua to do that, given that’s about all we know, from previous troubleshooting. :frowning:


@KrishnaIyerEaswaran2 it appears to be online now. I’ll fire up a node and see if some data flows…

Hi @KrishnaIyerEaswaran2,
requesting the mentioned endpoint helped me to find out, that my gateway was not provisioned (happened half a year ago, see TTIG "not connected")

That’s very strange. Just to be clear. I haven’t touched the settings.

These gateways are configured in a batch along with about 1000 other gateways via a script so there are no specific settings here.

Also, it seems a good way to figure out something is wrong, as right now @matqua is also getting a different response:

curl -k -i -X POST --data '{ "router": "58-A0-CB-FF-FE-80-31-B1" }'
HTTP/1.1 401 Unauthorized
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Date: Tue, 20 Oct 2020 12:38:52 GMT
Server: Python/3.6 aiohttp/3.5.4
Connection: close

Wrong Token

Yeah sure sure that’s fine. It’s just that this API needs a key that you will not be able to get.

@arjanvanb thanks for inviting me to this discussion. Please do that in case of such issues. Though I don’t exactly know what the issue is here.

1 Like

The only thing I have done different now verses earlier today was I left a ping running in the background on my computer to the TTIG for the last 30 minutes or so.

A websocket ping?

No, just old fashioned ping -t

@matqua, are you seeing the AU915 thing now, or is the following pending?

I believe it is pending still. I haven’t had a reply yet on that thread (only posted today).

My guess is once they manually enable it on the backend it should just work. From what I read I should NOT delete the gateway from the console as the EUI will not be usable anymore?