Nick, @johncassidy John, The Hub Pro can be thought of as a superset of the TTIG - as I dropped a few clues lets get explicit - it uses a different/more capable processor and allows for additional capabilities and given it can run either Basic Station - via CUPS - which is what we are waiting for official release on TTN V3 or it can run the Semtech (UDP based) Packet Forwarder, that gives possibilities. Can it run of a V3 stack - yes, TTIG/Mini Pro on BS on TTI, testing on TTN, now…if you dont want to wait for CUPS release…there is the legacy option… Mini Pro on V3 using UDP - yes?!
There are a number of retailers of the Mini Pro offering it as option for a number of LoRaWAN networks…
Personally I would stick it on V2 (using BS) for now then when TTI ready to open it to the TTNV3 CUPS - Robert is you mothers brother…
Can someone sum up what the current state eo May 2021 is? Is it possible to update a TTIG to V3 now or will it be automatically done in the future as I heard as rumor?
thethingsnetwork.org sends out newsletters with adds for V3 and straight time table to switch off V2 but is there a update possibility for former mass sold TTIGs?
What’s next?
May 28 - The Things Conference - The Things Stack Edition
July 1 - The Things Network V2 becomes read-only
December 31 - End of Life The Things Network V2
For my taste it is critical to shout out loud “the end is near” without a solution for month before soled own / TTN hardware!
It does work on v3 but it is being tested and there are no special privileges on this testing so please don’t ask - I’m not testing my TTIGs but I totally believe the people I know who say it is working.
So please do not fret, it is in hand but now is not the time.
Questions about if TTIG is already supported for V3 are understandable.
However, getting the same question over and over again, spread over multiple topics becomes tiresome.
TTIG is currently not supported for V3.
It will be but a date for when TTIG gets V3 support has not yet been announced.
Please stop asking. We don’t know a date yet.
As soon as a date is known this will be clearly announced on the forum.
Until then we all have to be patient.
(The title of this topic has been updated to make clear TTIG is not yet supported for V3.)
Hi, I just noticed we’re just 8 days away from being unable to add end devices (“Registrations of new gateways and end devices in The Things Network V2 clusters will be disabled on Wednesday, 30th June 2021”).
So I guess the question is, will there be a way to get this sorted and migrate TTIG-based installations to v3 before Wednesday next week?
TTIG device claiming was added as part of the capabilities for the TTS(CE) update/upgrade yesterday - now we are just awating on instructions on how to use it Will be trying myself in coming days…
I have small indoor Things Network Gateway, about 5 months back i was told that it could not be registered with V3 Console, i wanted to know if V3 now supports registering (small indoor) The Things Network Gateway. (Please find the link to item I’m referring here)
TTIG claiming was enabled by the last TTS(CE) update on monday - we are just awaiting formal release of instructions on how to best use the capability… a few more days patience needed whilst core & beta testers confirm all good
Hello!
Im aware we have to wait for a solution to connect TTNIG to version 3 of TTN. My problem is that I have 10 Indoor Gateways installed and none of them are forwarding traffic from my nodes in Version 3. I can see incoming traffic in the gateway (in V2) but I CANT see any incoming messages from my applications in V3.
Im using United States frequency plan since Im in Mexico (I have tried ttn-router-eu and ttn-router-us-west as the router address of the gateway with no luck) . It was very urgent for me to have my nodes working so I bought some LPS-8 Gateways and they are running OK in version 3 but I would like to keep using my TTNIG as soon as possible since I need some more and don`t want to spend that “extra” money if i can use my old TTNIG gateways.
There appear to be a number of things going on here, assuming TTNIG is actually The Things Indoor Gateway:
v2 traffic is forwarded to v3 and has done since we started using it - so there is likely a configuration issue on your devices. Where these devices migrated? What join method do they use - ABP or OTAA?
When you say you tried the different router addresses, the TTIG doesn’t give you that option as far as I recall, so can you clarify what you are doing when you tried the different addresses.
But the good news is we are literally days away from migrating TTIG’s to v3 - it is actually available now if you know the magic incantations on the command line tool - and the functionality for doing it on the console is very very close.
Whilst I’m sure this issue is burning a hole in your soul, you could just hang on a few more days whilst bigger brains than ours figure out the details, cross the i’s and dot the t’s and generally make it safe for public consumption.
Of course, none of this may help you as you didn’t answer either of my questions and we may well just be circling back to the v3 console not seeing traffic or where you were putting the router address!
TTIG is currently not supported for V3.
Us with a The Things Indoor Gateway are waiting with excitement. Thank you for your efforts. 
Will be trying myself in coming days… 
