Hello! Thanks for your help! I have finally moved some of my indoor gateways to V3. Can I delete them from V2 once I have them connected in V3?
Thanks!
As a wise man recently said on another thread
NO, as nothing is pointing at v2 it’s a bit academic right up to the time you suddenly need it working on v2 to try something.
Though in your case you may still have some V2 apps/devices, the principle remains the same.
Well actually if you are happy with V3 behaviour then yes you could but above advice to hold may be safe option. No need to keep on v2 as local V2 users in range of your gw(s) will still be serviced by V3 GW & Packet Broker interop. V2 op will end when V2 killed of at end of year anyhow…
1 Like
Hi @koljaS ,
we’ve updated the configuration of our Minihubs, it should work now connecting them to TTN v3.
Felix
Hello, Except that it’s been 9 hours on my side since I registered a TTIG and the status is still disconnected. I give training to let you know but I find it more complicated to switch to V3 than V2 
Did you power off/on the TTIG? That way it got connected within minutes.
I turned it on, off, moved it, changed the wifi configuration, turned it off, then on again … I have the LED which lights up green and stays on continuously. However I still have Disconnected.
I am using: EU_863_870_TTN and the server:
eu1.cloud.thethings.network
I had read somewhere that you have to wait for it to be active but the concern is that I had TTIGs bought for participants and there they will just find that it does not work 
Do you have the four magic parts (LNS Key plus the three attributes) as seen in this screen shot?
Your values will/may be different.
If not, delete it and try again. This is a current (as of mid-July) fix, not great, but there are two senior TTI team members looking in to this, but in the meanwhile, delete & retry has worked for many others.
Once the settings appear, a simple power cycle will speed up the TTIG reading the new settings. Changing WiFi isn’t a thing.
Once it takes you should see status reports in the gateway web console (you may need to turn on verbose mode).
The acid Jeff test is device traffic if you have one you can trigger on demand.
Hello, I have nothing of the kind, here is what I have like configuration, these fields like on your image must be filled (exactely like your pic) ?
Please check if the following are done
- Claiming was successful and the gateway was created in V3.
- You waited for 24 hours (for non-reachable gateways) or power cycled (reachable gateways).
- Gateways were able to connect to the internet properly and the LED shows solid GREEN (not blinking).
- The Gateway is still shown as disconnected in the V3 console.
If this is your case, please send me your EUI via a direct message and I’ll look what’s going on.
Hello Krishna,
Thank you for the message. For me all the stages went well. And I remain on the status disconnected. My EUI is as follows: 58A0CBFFFE802072
The console LiveData : {
“time”: “2021-07-13T06:51:32.796Z”,
“name”: “synthetic.status.reconnected”,
“isError”: false,
“isSynthetic”: true,
“unique_id”: “synthetic.1626159092796”
}
Ok thanks. I’ll check and get back to you
@James32 It looks like you just registered your gateway and did not follow the claiming process:
https://www.thethingsindustries.com/docs/gateways/thethingsindoorgateway/
Your gateway is just registered and not claimed and hence is not connecting. Please check the docs above and follow those steps.
Ok so I don’t understand because my gateway had never been registered before. Therefore it seemed to me that it was necessary to follow the following procedure in the document:
New gateways
If your gateway has never been configured on an LNS, follow the steps below.
Hold the RESET button (small button on the back of the gateway next to the USB-C port) for 5 seconds until the LED flashes rapidly from GREEN to RED and vice versa several times.
Hold the SETUP button (at the top of the gateway, next to the LED) for 10 seconds until the LED quickly flashes RED.
The gateway now exposes a WiFi access point whose SSID is MINIHUB-xxxxxx, where xxxxxx are the last 6 digits of the EUI gateway. The password for this network is the same WiFi password from the Prerequisites.
After connecting to this network, go to 192.168.4.1 using a web browser to access the WiFi configuration page.
And I don’t know where to find the claim steps … knowing that I’m in V3?
Sorry but I can’t see anything about it at all!
Can you help me please because here I am desperate
Ok the Claim button has just magically appeared !!! I will be able to do the configuration!
I will come back to you if I have a problem, thank you very much
error
Gateway with EUI 58A0CBFFFE802072 already exists and is not authorized for claiming
So before making the Claim Gateway I had registered the gateway in the classic way (add button). There I put the parameters back through the button claim but I have the following message:
error
Gateway with EUI 58A0CBFFFE802072 already exists and is not authorized for claiming
What should I do at this level. I understand that I am trying to register the same gateway twice. In this case, should I delete the previous config I had before clicking on claim?
If yes, how ?
How to unregister a gateway and start its registration again?
Because I read that if we unregister a gateway, it will never be possible to save it for life (its EUI)