What problem(s) are you seeing? How far are you getting through the process? Have you registered all details in your console → gateway → add gateway (note not claim gateway, and you do not need a gw eui to register), what do status leds show? What firmware version is your gw? Was it previously on TTN v2?..… some details and we can start to help and make suggestions otherwise it’s guess work for the forum volunteers….
I see you have populated it with 27…63, where did you get that from? Why put it in? Try to delete and update - delete gw & register again if needed (you will need to change GW ID if deleting as these cant be reused, sorry)…did you generate the API key and enter that (simple copy/paste)? Can you see the GW on your local router/AP? Has it taken an IP address under DHCP ok?
Updated to add:
I see
And though official docs say need 1.0.8, IIRC one of the TTI core team posted previously that should be ok with 1.0.7. I think you may get problems with 1.0.5. Give it a try per above and the docs and leave for 48 hrs to see…if recognised on the system and if in the general settings you have ticked the boxes to allow visibility in the network and auto updates etc. under General Settings tab, then hopefully it should auto update to 1.0.8 if not even 1.0.9 in more recent times - to cover cert changes if I recall. If that fails follow the doc link to do firmware update using SD card…only issue thereafter is you need to leave sd card in place for future good running IIRC which may not be ideal but I gather works ok.
That’s because you don’t need one…… per the documentation and info on this very forum!
Why go off piste…. Vs follow the documentation?
Nope, that is where you enter one if needed…… per the documentation it isn’t and can be left blank (note once registered the gw console page will list gw eui with status n/a).
That is good and to be preferred to using WiFi for stability and some users have reported issues in the past
Use the documentation and advice given here and elsewhere on the forum….basically start again and do it the documented way.
If you do need to update then…… the link is in the documentation……definite pattern emerging here good luck!
Thanks, Kersing the website issue has been resolved for registering the gateway and also, I managed to update the firmware on the gateway. However, I am still unable to activate the gateway the new things I managed to do is that the I got two solid Leds and the third is flashing since last night.
I am not sure if the server address is right I have it as ‘‘eu1.cloud.thethings.network’’ I copied this and past it at the gateway
Can anyone advice about the right server address please?
I have got TTN-GW-915
I am using: nam1.cloud.thethings.network as my gateway server address and US_902_928_FSB_2 as the frequency plan.
I see following status LED sequence:
1st LED ON
2nd LED ON
after couple seconds all LEDs go OFF
then 1st LED ON
2nd LED ON
after couple seconds all LEDs go OFF
…
In one of your screenshots I see “Gateway Card: ND”, (Not Detected I think).
I remember seeing an issue like that on the two TheThingsGateways that I helped migrate to TTNv3.
I found the instructions on the official page not very clear, even a bit confusing.
Unfortunately I do not have access to those gateways anymore (was helping someone else).
It was a bit weird, perhaps even a bug in the firmware. I got the “Gateway card: ND” symptom when trying to configure WiFi at the same time as entering the gateway id and gateway key. For me, the solution was to NOT setup WiFi, just first setup basic gateway settings, let it connect, etc, then later set up the WiFi parameters.
I recall similar advice/suggestion from somewhile back - may have been firmware dependant… I always set up on wired e’net 1st before deployment and have only occasionally used wifi on a TT(K)GW so haven’t seen the issue 1st hand.