hmm, that is the account server…
I could not find that in the docs…
I am not a specialist 
just supported The Things Network with the kick starter.
forgive me for not understanding all details and naming of all different components in the architecture.
I still believe in your mission!
But this migration was a bit hard on me
1 Like
Same here. I had a gateway up and running to test an AmbaSat in the lab and in the field.
It suddenly stopped working in mid-June. I’ve spent hours on this trying to get moved over to version 3. “May as well do it now” is what I thought.
I have a Gateway ID, a Gateway Key, An Application EUI, a Device EUI, a Device Address, a network session key, an application session key, a “new” application ID, and a “new” API Key. I am no longer sure of what is what (I thought I knew, but it just doesn’t work) and where these values go. I have tried every combination that looks reasonable. I’ve gotten “new” ones when it seemed like it was instructed.
But…
There are conflicting explanations from different webpages and projects. I’m just trying to get this to work. I believed in the TTN thing and campaigned pretty hard to raise awareness about it. But, it’s not the central piece of the project I’m working on. If I can’t figure it out then how in the world are users going to figure it out?
I already lost one lab volunteer because their data has been missing for nearly a month.
-Abx
That shouldn’t be caused by V2 to V3 migrations so it might have been better to find the cause of the issues. As that is a last station let’s move on…
It is not that hard if you take a moment or two to think about it. And use the proper documentation which can be found on the TTN website.
What brand gateway are you using and what protocol does it use to talk to the backend?
There is plenty of migration documentation on the TTN website and you could have asked for help on this forum earlier on.
Your current message does tell us anything about what currently works and what doesn’t. Perhaps you can start by telling if the gateway is online in V3 and if not provide the information I asked for above?
Next we can look at the issues you might be having with the node(s).
Users? It’s not a mobile phone service, we are the users. Any one can deploy a device being heard by a community gateway, but it’s not really at appliance level (yet).
Why didn’t your lab volunteer make enquiries the day data stopped?
We get the use of a set of servers for free, the rest is up to us!
1 Like
Question specific to Kickstarter GW. Documentation states cannot change ID., yet searching forums seems you need to if moving from V2 to V3.
Like some others, being a numpty I jumped the gun months ago after receiving several emails with dire warnings from TTN to move to V3. Just hope I have not bricked my GW as now probs with connecting to V3
Reset and Followed the Kick st Docs exactly to connect multiple times but LED3 fast flash which I see may be a key problem or GW already activated.
Question should I try again but use the same ID that I had on V2 ?
Answer: attempted this but “ID already taken”
So what next? Have read and re read every doc and forum . I know that at 75 my brain is getting foggy but I thought I had followed instructions to the letter. Shame as have now got a great aerial site high atop the South Downs if I can get this to work.
@niccoleman, I followed these instructions and the gateway was recognized in the V3 console, I could see connect & disconnect events, but nothing else.
I followed the advice here, to not use @ttn in the gateway ID and it worked! Immediately I started seeing “Receive gateway status” messages in the console.
This with a Kickstarter gateway running Firmware: v1.0.8-846da98b, fresh reset and reconfigure:
- Gateway ID: my-gateway-name (without @ttn)
- Account Server: https://nam1.cloud.thethings.network
- Gateway Key: apiKey created in the V3 console with “Link as Gateway to Gateway Server…” permission
Cheers,
- Frank
Hello,
I am not able to connect my TTN Gateway to V3. Firmware is v1.0.8.
HTTP: Starting connection<\r><\n>
HTTPS: Connection Opened: Starting TLS Negotiation<\r><\n>
HTTP: Wait for TLS Connect<\r><\n>
HTTP: TLS Connection Opened: Starting Clear Text Communication<\r><\n>
HTTP: Got 1074 bytes<\r><\n>
MON: SYS Stack size: 2833<\r><\n>
MON: TCPIP Stack size: 3759<\r><\n>
MON: APP Stack size: 4155<\r><\n>
MON: LoRa Stack size: 3909<\r><\n>
MON: heap usage: 265KB (275KB), free: 73KB<\r><\n>
HTTP: Connection Closed<\r><\n>
HTTP: Close active socket 1<\r><\n>
CONF: Parsing response token: HTTP/1.1 400 Bad Request<\r><\n>
ACTI: Failed to parse JSON: -3<\r><\n>
<\r><\n>
CNFG: Downloading gateway configuration failed<\r><\n>
<\r><\n>
CNFG: Load online user config state change to 8<\r><\n>
<\r><\n>
CNFG: Communication ERROR<\r><\n>
That’s what I get with my serial monitor. The third LED is slowly flashing, means that the activation is not working.
I tried the Gateway ID with and without @ttn, different Account-Servers and different Gateway Keys. With V2 I am able to connect.
Please have a look to my screenshot. I am using the gateway ID from the top, and the gateway server address from the bottom. Is that correct?
What could I try? What is the correct way?
Thanks!
If you want to connect to TheThingsNetwork community edition you should use a gateway server address like:
eu1.cloud.thethings.network
(first part may be different depending on your region)
What worked for me:
- DON’T set up WiFi on the gateway
- enter the gateway id WITHOUT @ttn
- make sure that you copied the ENTIRE API key from the console (you can see it only once in its entirety)
Thanks, but still the same issue.
How could I check if I am using the community edition?
I am using ethernet connection.
The documentation is sometimes contradicting between documents.
But I got it to work using the device id without @ttn and using account server https://eu1.cloud.thethings.network
It took several tries but it’s possible that I had an enter at the end of the generated api key when copy-pasting.
So, make sure you copy the exact api key (with no enter/cariage return at the end).
@thingsaregreat , I can see that you are using The Things Stack Cloud from the screenshot. The account server URL is going to be the same as the URL you access the console at, <tenant>.<region>.cloud.thethings.industries
Here is the URL for our TTI tenant, your tenant name will be different and your region should be the same.
All server addresses are listed here → Server Addresses | The Things Stack for LoRaWAN
Or more simply put:
It’s on the overview layout that you blanked out in your screen shot.
Everyone who’s had issues with getting going has eventually posted “so I removed the @ttn” at the end and it worked!
Hi all, I struggled also a little bit to migrate my Kickstarter-GW from v2 to v3, think one of the issue was that the API-Key displayed was not the same as copied when generated
e.g. copied NNSXS.JEP7xxxxxx , displayed in the console JEP7xxxxxx
summarized my steps:
1.) Add Gateway, mandatory is Gateway ID (no Gateway EUI needed)
2.) Add API-Key: copied API-key when generated (and saved somewhere)
3.) Reset-Gateway with pink button inside
4.) WiFi connection to GW SSID e.g. “Things-Gateway-xy”
5.) Password “thethings” / (IP-address of GW is normally 192.168.84.1)
6.) check Firmware of GW http://192.168.84.1/info (my was v.1.0.8)
7.) GW-console http://192.168.84.1
8.) set GW-ID from add GW (without @ttn e.g 8916jonenv3)
9.) set WiFi-connection
10.) for EU: https://eu1.cloud.thethings.network
11.) set API-Key from adding the GW e.g. NNSXS.JEP7xxxxxx
12.) Save - GW will reboot
Thank you for sharing you procedure.
It is important to note that the API KEY is different from the API ID.
API Key: NNSXS.JEP7xxxxxx
API ID: JEP7xxxxxx
I got “LGMD:Rejected packet (0x11)” messages before configuration the correct API Key.
Thanks to everyone on this thread.
I purchased a Kickstarter TTN Gateway from Farnell in the UK (selling for £34 including shipping).
Couldn’t get it to work until I found your advice.
2 Likes
Your timing must have been exceptional - it seems they had a web pricing issue (for about a week); I suspect triggered when they updated system to show not being manufactured anymore and stock would not be replaced once sold!
Anyone looking to replicate your deal will be dissapointed as now back to £266+Vat (20% in UK), though at that level free shipping 
They did apparantly ‘sell out’ at one point last week but I guess once people heard price was being corrected back before shipment they cancelled and stock levels look to rebound this week to 12 then 14 and today looks like 23 left. Note also: all Things Uno’s and Things Nodes are now long gone…
Wow! Just looked at the Farnell website and you are right. Never been that lucky before. I should have bought two!.
Should have bought all of them and sold them as Helium Miners on eBay …
Would be data only not mining…and a struggle to get onto H?..still mugs are born every day so you could sell to those in a hurry who dont check (caveat emptor) and shut up shop before repercussions arise!
Was thinking 5-10 but too slow! 
Those units run the TTN specific gateway protocol so there is no way to use them with Helium. Not even for data only gateways.