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!
He does not mean literally 11. It’s a US thing. The best description I could find for the saying “News at 11” from reddit:
It’s a trope referencing a time when there was only a morning news, an evening news, and late night news, and nothing else. Special stories that broke during the day and too hot to wait for morning would air at 11.
One of the leading experts got in a tangle migrating one of his remote TTIGs but got it working. TTI team are tweaking some bits as the error message would have us mortals running for the hills …
And the Leading Expert’s Sidekick’s bag carrier & boot cleaner (me) will likley be helped with a couple of crutches to limp through the process breaking things and looking for gotcha’s over next day or two to see how resiliant & idiot proof (me again) the process is… more news by the weekend?!
And if you read the forum, you’ll see that you can, if we infer that you mean you bought a product just as the easiest place to deploy it was publicly going read-only …
For anyone with new TTIGs reading this topic. When it comes to TTIG the word ‘migrate’ is used a lot where we probably should use ‘claim’, to connect new TTIGs to V3 you can use the same procedure used to migrate TTIGs from V2 to V3, no need to register them in V2.
The problem is the manufacturer, which sells a gateway that only connects to the TTN and takes off a system (V2) that is working without having the new (V3) working perfectly.
Sorry if I was aggressive, but I’m in the middle of a POC and I can’t test the up and down as a whole.
I read practically the entire site, every post. I’m letting off steam because I don’t see a light at the end of the tunnel.
You purchased something with all the info available about how it could be deployed publicly available so much of the responsibility for this situation is self-generated.
The instructions for setting up on v3 are in two threads on this forum.
If it’s on v2, then, as I’m sure you will know from research, it will forward packets to v3, so it’s all good and you can carry on with your PoC testing.
But if you look around the forum, you’ll find the instructions for getting a TTIG on to v3.
Understood
