I’ve got a question regarding the (now gone) LNS key:
After claiming the device a LNS key was generated and showed up automatically in the general settings of the gateway.
Looking at the settings of my TTIG now shows an empty LNS key (see picture below, I’ve marked the empty field in red). Nevertheless my TTIG in still connected and is still successfully forwarding packets.
So is the LNS key still stored and just not displayed for security reasons (and neither a placeholder) or should I be worried that soon the gateway will disconnect due to a missing LNS key?
Here’s a screenshot of (that part of) my basic settings:
This has worked for me - my gateway now shows connected on both the v2 and v3 pages. Traffic showing on v3 gateway (not v2). Data being forwarded to v2 app fine. Should I remove the gateway from v2?
Hi @Jeff-UK ,
we have a few customers using the gateways on their own server. That’s why we needed to claim them. We have unclaimed the TTIGs that were sold to TTN customers now.
I added my new TTIG gateway (Amazon/iot-shop.de) via the “Add Gateway” route rather than the “Claim Gateway”.
It is currently showing as offline in v3 but is forwarding traffic via the traffic forwarder. What steps do I need to claim the gateway and have it show as online in v3?
My last one arrived from RS in a bubble wrap bag ie, no box. So someone could have taken down the details.
If you’d sold a few hundred TTIGs, would you have got each one out, recorded the details and then at a later date claim the device for yourself (rather traceable to an account) but not have physical access to it (as its location is unknown). Why would they do that? In the UK that’s illegal, I’m sure it would be too in the EU.
As you’ve no doubt been told before, search the forum where you will find instructions for the TTIG and advise not to delete the gateway from v2, just in case.
Its not regarding migrating from V2 to V3, in January 2021 I deleted my TTIG from V2 and i was told that it cant be restored and i can get back later when TTIG devices can be connected to V3 (or supported by V3)
So my TTIG was already removed from V2 now when i created new Gateway on V3 it shows status disconnected, when i try to claim it, i get error message “No claim authentication code” I’m sure I’m using correct Claim authorization code which i got from TTIG access password
To be brutally honest, this is where you are at, you deleted your gateway prematurely and then you put “I added it to V3 Console it shows disconnected” and then you tell me I’ve got the wrong idea about your message???
Why could you have not used the correct language ‘claim’ with the error you were getting from your first post above.
Your last thread ran for 32 entries, if you can’t respect the other forum members time, please do not expect much in the way of help.
If you read this thread, you’ll see that the error message if it’s not typed in correctly is “Claim authentication code mismatch” whereas you are reporting “No claim authentication code” which suggests you didn’t actually type in the WiFi password (I’m not sure wha the TTIG access password is, accuracy in terminology is everything).
I’m sorry for my poor English/understanding, I highly appreciate everyone on this forum helping us.
As its said in the help that Claim Authentication code is WIFI code on the back of (TTIG) device
I’m attaching image to show how I’m trying to claim and what error message i get. (Please let me know if i should i hide any information in the picture)
- my gateway now shows connected on both the v2 and v3 pages. Traffic showing on v3 gateway (not v2). Data being forwarded to v2 app fine. Should I remove the gateway from v2?