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
- claiming 10sek
- new start 1min
- ready
many thx
i’m so pleased
3 Likes
Hi everyone, and Merry Christmas!
I’m experiencing exactly the same problem as @dvbahder here. Same error while claiming:
When I use the CLI to see if anyone else registered this gateway (just in case), it seems nobody did:
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!
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
… 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?
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:
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
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
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.
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