Make sure your TTIG is not yet registered on V3. The claiming process will register it for you.
If you did already register your gateway on V3, you can delete it, but then you’ll have to choose a different Gateway ID for the claiming process.
Find the EUI of your TTIG. This should be printed on the sticker on your gateway. The EUI starts with 58A0CB, then on some stickers there’s FFFE (if it’s not, just imagine it’s there), and the EUI ends with 80****.
Find the WiFi password of your TTIG. This should also be printed on the sticker.
For Claim authentication code, enter the WiFi password of your TTIG.
Choose a Gateway ID. You can’t use a gateway ID that is (or was) already registered on V3.
Select the frequency plan you want to use on your gateway.
Click Claim gateway.
Keep your fingers crossed and hope that everything works.
If claiming was successful, now either wait (up to 24 hours) for your gateway to reload or unplug your gateway, wait a couple of seconds and then plug it back in.
When you see your gateway online on V3, you can (but don’t have to) delete it from V2.
NOTE: If your The Things Indoor Gateway was sold by IoT-Shop.de (either directly or via Amazon.com) The Things Network was not always able to claim your gateway on the upstream server. This issue should now be resolved.
I attempted this and it it gave me an error on the claim screen “No Claim Authentication Code”. I had a code entered (the wifi password on the back of the device). I confirmed it was correct by logging into the device using it.
I then claimed the device using the CLI which worked and my device is claimed and has a solid green light but still says disconnected in the console. I unplugged the device from the wall for a count of 30 and plugged it back in. Still showing disconnected.
I then tried to download the global_config.json file from the console for the device and got a failed to download with and error of “Failed to download global_conf.json An unknown error occurred and the global.conf.json could not be downloaded”
Hello, I claimed TTIG in V3 according to above documentation. I un- and replugged it but it stays disconnected in the console and the green LED blinks (freq 1/4 sec).
Before, the TTIG was disconnected for months because I changed WIFI password and forgetting to change it in TTIG as well - I have corrected this. How can I trouble shoot?
Can you check if the extra BasicStation info has appeared in the gateway settings (menu on the left will get you there, scroll down a bit, it appears after the description box, gateway server address & required authentication):
You should expect the LNS key and the three attributes. The numbers/entries/details will not necessarily be the same.
If you can’t see any of this stuff, then delete the gateway and re-claim it.
You will not be able to reuse your gateway ID so think of another one.
PS, the public bit is optional, I turned it on because I’m a nice TTNer
I did everything you wrote above, I can see that the gateway is connected to my WiFi AP, I can ping the IP and I can see that it exchanges traffic:
But the status in the console remains “Disconnected”, the cups attributes are missing and the gateway blinks red and green. I let it run for 2-3hours but nothing changed… Any idea?
Not sure why you remark on your gateway having the CUPS attributes missing, which implies you read my post but read my post above where it says
but when you read it this time, do not past Go, do not collect $200, just do it!
One of my TTIGs took three goes. It’s not a great state of affairs but there is a lot going on in the background to do a claim and it’s only been running a few days now so plenty more ironing out to do.
I did it at least 6 times before I wrote the post yesterday and nothing changed. So, yes, I read your post and also your copy/pasted post in the other thread. Does it help to be a moderator and assume that nobody reads your posts, basically expecting the worst from other people? In my experience if you try something so many times and it doesn’t work your in a situation where you need real help and that’s why I wrote the post, rather hoping for help than sarcasm.
Anyhow: I left the gateway unplugged over night and put it back in this morning and now it is connected. So my message to other users in the same situation: you might have to be patient, don’t expect the system to give you any helpful indication and keep re-trying, even if you have to do that many times.
Something you choose not to share with us, so we had no context to your situation.
It doesn’t help to be a moderator as it takes up a fair amount of time, but you are confusing my role as moderator with someone who posts answers which is what I was doing above, you don’t have to volunteer to be a moderator to post pointed comments. As to expecting people not to read my posts, that would be a normal expectation, yes. Some threads go on for 40 to 60 posts before we get a result. If I ask three factual questions to help debug, I usually get at least one full answer, one partial and then we have to go back & forth to get the third answered.
If you’re game, you could add me as a collaborator that can manage gateways only and DM me your EUI and WiFi password and I can have a go.
[ModeratorMode] FYI, we don’t do ad hominem attacks here. [/ModeratorMode]
