Connecting TTIG to The Things Stack (TTN V3)

TTN V2 to V3 Upgrade V3 Gateways
197

i’m back

I bought the device as new (rsonline-privat.com), I unpacked it, registered with ttn (my first account with ttn) and it worked straight away since 11-2019 to this day and is still working
in the v2 i can see it and it has no other owners, no collaboraters

I tried the instructions from htdvisser
in cli answer is

…nothing

i have in another account (school in Dresden, since 2020) a mikrotik, is working fine in v3,
with the same commands, i’ve correct answers
the comands are working in my account…

is there anything else i can try?

thx for help!

198

We run the risk of splitting hairs here, but Hylke said claimed …

199

We run the risk of splitting hairs here, but Hylke said claimed …

That’s probably a mistake. I don’t think that passwords can be repeated since they are generated based on a gateway specific hardware secret.

I think someone else “registered” this EUI. @htdvisser’s recommended steps to resolve this issue are still valid.

200

Sorry for the confusion. I meant “claimed the EUI” – either by registering a gateway with that EUI (ignoring all the warnings), or by claiming a gateway and then returning it to RS like @Jeff-UK described above.

Since the CLI says that this gateway has no collaborators, it’s possible that someone did register it, and then (instead of deleting it) revoked their own rights on the gateway. @dvbahder could you please share the full EUI of your gateway, then we try to find out what’s going on here.

201

thx
Gateway ID
eui-58a0cbfffe800fb0

202

sorry
Gateway with EUI 58A0CBFFFE800FB0 already exists and is not authorized for claiming
on cli my rigths only for own v3 gateways, could`nt find any gateways#

I should just wait until v2 ends and then register my ttig new in v3 with a new ID

Status in v2 (is working)
GATEWAY OVERVIEW
Gateway ID eui-58a0cbfffe800fb0
Description TTN Gateway Indoor DvB
Owner dvbahder
Status connected (v2)
Frequency Plan Europe868MHz
Router ttn-router-eu

there is another idea? thx

203

ID yes, but it’s the EUI that’s already registered so it will be blocked until someone finds out who has used that EUI already.

204

but doesn’t it say in v2 that i am the owner?

205

You never actually own an EUI, you merely look after it for the network.

In short, no, an entry in v2 doesn’t verify the ownership of a gateway as anyone can enter any EUI they like. And it has been clearly stated by TTI that they aren’t going there - search the forum for such discussions from around mid-June when migrations started.

You need to petition TTI to help you with this - only TTI staff have access to TTI systems so only they can help you further - maybe @KrishnaIyerEaswaran2 can help.

206

thx
i’ve ask him

207

The gateway that was registered with EUI 58A0CBFFFE800FB0 hasn’t connected since it was registered, so the EUI was probably entered incorrectly. We’ll unset the EUI from that gateway, so you should now be able to claim your gateway.

1 Like
208
  • claiming 10sek
  • new start 1min
  • ready

:slight_smile: :sunny:

many thx
i’m so pleased

3 Likes
209

Hi everyone, and Merry Christmas!

I’m experiencing exactly the same problem as @dvbahder here. Same error while claiming:
image

When I use the CLI to see if anyone else registered this gateway (just in case), it seems nobody did:
image

I tried the EUI in upper case and lower case, just in case, but got an empty array in both cases.
As @dvbahder, I’m simply trying to migrate from V2 to V3 (all devices migrated already). To the best of my knowledge, I never created this gateway myself in V3. No one else has ever had access to this gateway, it’s plugged next to me in my lab since I bought it.

I guess I’m out of options. Anyway, not urgent really, specially on Christmas Eve, but I would really appreciate some help to see what could be going on.

Thank you all, Merry Christmas, and my very best for next year!

210

I believe un-migrated TTIGs as of date of V2 shut down (or shortly thereafter) may well have been ‘auto–migrated’ to V3 using the eui as GW ID… you should be able to see this as a listing in your GW console overview (if you were the orginal owner)…is there anything there? If so you can delete and reclaim under a name of your choise at that point.

See here

Note your original V2 details are shown here:
https://account.thethingsnetwork.org/api/v2/gateways/eui-58a0cbfffe801992

1 Like
211

… as long as you have exactly the same user ID.

@ddemarco, you write several paragraphs without saying EXACTLY which gateway, so just to sanity check, what is is?

212

Hi Jeff, that’s very much appreciated. While I believe the TTIG meets all conditions in the linked article, it does not show in my console:
image
I certainly have the same user ID as I had in V2 (ddemarco), because I always logged into V3 using the V2 credentials.

The information you provide in the link seems totally correct, i.e. that’s the data the gateway had on V2. Based on the article, it really looks like the gateway was migrated to V3 automatically, but doesn’t show in my console. It does work, though, as I receive the traffic from all devices. Would that confirm that the gateway was migrated? If so, under which account?

Thank you!
Diego

213

Hi @descartes,

I do have the same user id, as I only logged into V3 using the V2 credentials. I apologize for not including the gateway EUI as text (it was part of the screenshots only), so here it goes: 58a0cbfffe801992

Based on the conditions mentioned by Jeff, I tend to think the gateway was effectively migrated, but for some reason it doesn’t show in my console (checked all three regions just in case).

Here is a bit of data that I’m getting through a webhook, which seems to effectively show the gateway is working fine, as this is extracted from data received from one of the end devices:

"packet_broker":
{
    "message_id":"01FQQ028FDEMXRKTSD769WTDKX",
    "forwarder_net_id":"000013",
    "forwarder_tenant_id":"ttnv2",
    "forwarder_cluster_id":"ttn-v2-eu-1",
    "forwarder_gateway_eui":"58A0CBFFFE801992",
    "forwarder_gateway_id":"eui-58a0cbfffe801992",
    "home_network_net_id":"000013",
    "home_network_tenant_id":"ttn",
    "home_network_cluster_id":"eu1.cloud.thethings.network"
}

I can’t think of anything else to check on my side. It’s working (and probably migrated, right?) but not showing in my V3 console. Anything else you can think of?

All the best,
Diego

214

It looks like someone else registered a gateway with the EUI of your gateway. Looking at the ID of this registered gateway, it looks like this was done by mistake, so I just released the EUI. You should be able to claim your TTIG now.

215

Hi, that’s brilliant, thank you! The claiming succeeded all right and I’m receiving data from the devices without any issues. Thank you again for your support, and all the best for 2022!

Cheers,
Diego

216

Hi everyone,

I’m experiencing the same problem and always getting the following error when I login to my account.

Error ID: error:pkg/auth/rights:no_gateway_rights
Correlation ID: 2638a37fc5ad4e12ac6b996e728eafea

{
“code”: 7,
“message”: “error:pkg/auth/rights:no_gateway_rights (no rights for gateway eui-2cf7f21116090001@ttn)”,
“details”: [
{
“@type”: “type.googleapis.com/ttn.lorawan.v3.ErrorDetails”,
“namespace”: “pkg/auth/rights”,
“name”: “no_gateway_rights”,
“message_format”: “no rights for gateway {uid}”,
“attributes”: {
“uid”: “eui-2cf7f21116090001@ttn”
},
“correlation_id”: “2638a37fc5ad4e12ac6b996e728eafea”,
“code”: 7
}
]
}

Here is also a screenshot of the gateway page.

image
image1323×585 40.9 KB

I would really appreciate some help to see what could be going on.

Thank you all!