Yes! Works for me fine as well…so far 
Been claiming the TTIG, everything went through pretty well. I’m happy! 
Now I will have to wait till tomorrow, to see whether it got the new settings as the device is more than 500km away from me.
Does this claiming-thngy only work for the TTIG or do I have to migrate all gateways like this, e.g. 3rd party gateways which are using the semtech udp packet forwarder?
Thanks very much everybody for your patience 
That’s a good suggestion. Let’s remove the links until we figure this out.
Let’s hope we can find a solution before then.
If you don’t want to wait, I would recommend you to follow the steps under New Gateways at https://www.thethingsindustries.com/docs/gateways/models/thethingsindoorgateway/ to connect it to WiFi. If the LED eventually turns green, it’s at least connected to some network (probably V2).
Since V2 is read-only you won’t be able to register your gateway there, but it should still be able to forward LoRaWAN traffic.
This claiming thingy only works for TTIG, because those can be remotely reconfigured using that TrackNet/Semtech server. Many other gateways need to be reconfigured by accessing the gateway (over SSH or web interface) from your local network.
I bought exactly the same item end of January 2021, from “seeed studio-Store” which apparently is “iot-store.de”.
Just followed the steps given by @htdvisser and was able to successfully claim my TTIG in the V3 Console.
Power cycled it and it is now connected and receiving messages in the V3 Console.
Thanks!
I am also getting ‘Claim authentication code mismatch’. Triple checked the password.
I bought mine at Connected Things
Hi. Please check if the characters are correct; The Things Indoor Gateway | The Things Stack for LoRaWAN
We’ve had quite a few instances where users mistyped characters.
If you’re sure your claim is correct, paste your EUI here and I’ll check. If you don’t want to share that publicly, please send me a private message.
Could you please drop me a PM so that I can respond to it with the EUI?
thx
martin
Just click on his user name and it will open window for you to send a message!
thx … I was blind to not see the Message button
I have my TTIG registered in V2 and have performed above steps.
It seems everything went through without an error and the TTIG now appears in V3.
But even after several power cycles, the status in V3 is “Disconnected” and in V2 it is “unknown” and both console do not show any live data.
my V3 ttnmapper application however still seems to be receiving message coming from my tracker via the v2 packer broker.
I have to add, that I have bought the device on Amazon … but as mentioned, did not receive any error when claiming it for V3.
Update: Yes, after claiming the TTIG successfully yesterday it came online today without powercycling it. 
Thanks again everyone!
Did the v2->v3 migration of my TTIG today, without any issues. The TTIG (gift from the TTN conference 2019) shows firmware 2.0.4, is this current? I enabled automatic updates.
@xAPPO and/or @mas_vie: We are testing a fix to make iot-shop.de gateways also work with claiming and would like a couple of volunteers. Could either of you send me a direct message?
@KrishnaIyerEaswaran2 @htdvisser How was it that A-O were able to pre claim these TTIG’s as their IoT shop clearly calls them out as Things Indoor GW’s
vs being Tabs GW’s, Browan Indoor GW’s, or “whatever alternate brand” Indoor GW, with clear implication they are for use with TTN/TTS. This doesnt sound good from a supply chain security POV! Begs the question what other devices they sell might have been prior captured to A-O vs being free open market devices? (You only have to look back at some of the prior TTConf presentations where security of supply chain and esp. distribution operations questioned/challenged to see why a concern - recall Johan and others using this to call out & justify use of seperate Join/ID Servers, Secure Elements, etc.)
Thought A-O was an energy metering/industrial private network operation & IoT solutions provider supporting a swathe of IoT connection technologies…though using private TTS instance for their LNS solution?
TTIGs come out of the factory unclaimed, and pre-provisioned for The Things Network.
Networks can then claim the gateways on the TrackNet server using the information that’s printed on the sticker (the EUI and WiFi password) in order to reconfigure them.
I don’t know what reasons the Alpha-Omega guys had to claim the gateways on their account. Maybe they just thought they still had to provision the gateways for The Things Network.
In any case, @KrishnaIyerEaswaran2 is working closely with them to sort this all out, and as he wrote above, we’re close to a solution. So if there are any volunteers with TTIGs from IoT-Shop.de that they couldn’t claim before, please reach out to @KrishnaIyerEaswaran2.
i can confirm that your solution seems to work together with @KrishnaIyerEaswaran2 ---- some minutes ago we tested it- mine was claimed back and its now running in v3 ! well done and thanks for your support !!!
Indeed as confirmed by Jens above, we deployed a fix to the server that makes iot-shop.de gateways also claimable.
However, we have enabled that on a gateway-by-gateway basis for testing. Later in the day today, we will enable this for all gateways purchased from iot-shop.de.
I will respond in this thread once that’s ready.
Thanks to everyone who volunteered to test.
Will there be any other residual aspects (configuration parameters) that might have been set for these iot-shop gateways that might not be reset appropriately for Things usage or will they be identical to all other users now ?
They’ll be the same as all TTIGs.