General Forum users or Moderators do not have access to TTI/TTN Backend systems or databases and TTI Core staff only drive by the Forum occasionally. Best option is to put request into TTN Slack #support channel which is more likely to be picked up by TTI Core team.
Would be interested to hear more backgound and reason as to why not - have you already attempted to delete in the TTN Web interface or are you changing instances etc. as that may inform alternate actions/options.
Sign up for a support contract and then you can get the TTN admin (the TTI staff) to do it.
Or very carefully delete the gateway - you will NOT be able to reuse the same Gateway Id but you can use the Gateway EUI.
But if we knew what the gateway actually was, we could advise further.
its a kerlink i station. And i must purge it. i work at fugro and used my account to show how lora works and they like it very mutch. we have sensors all over the world and they now want to begin small and i think they wil get big very fast. they ordered a lot of sensors for a test in the netherlands and i want to use my gateway for the workshop and fugro is one big security thing so i want to connect it to my fugro account. so please @KrishnaIyerEaswaran2 or another @admin do it for me please :
ttn-lw-cli gateways purge klk-7076ff0056071283
WARN [dns]dns: TXT record v=spf1 -all missing grpc_config= attribute
WARN Finished unary call {âdurationâ: 0.158, âerrorâ: âerror:pkg/identityserver:admins_purge_gateways (gateways may only be purged by admins)â, âerror_correlation_idâ: âe017da14fa084385864e7fe09ff69a07â, âerror_nameâ: âadmins_purge_gatewaysâ, âerror_namespaceâ: âpkg/identityserverâ, âgrpc.methodâ: âPurgeâ, âgrpc.serviceâ: âttn.lorawan.v3.GatewayRegistryâ, âgrpc_codeâ: âPermissionDeniedâ, ânamespaceâ: âgrpcâ, ârequest_idâ: â2a194249-bad3-464c-86c1-4a975563f639â}
error:pkg/identityserver:admins_purge_gateways (gateways may only be purged by admins)
correlation_id=e017da14fa084385864e7fe09ff69a07
Lots of sensors for a commercial company means the company should be using a paid for TTI instance, not freeload on someone elseâs infrastructure. And with a paid for instance you have support that can help with purging the gateway from TTN.
If the commercial company is using TTN while starting up with LoRaWAN the method to add the other account as described by JeffUK works to move the gateway to that account.
And if the gateway is to be registered with a different LoRaWAN network (not the sandbox but any other even commercial TTI instances) you should not need to purge the gateway.
Who said they are not going to pay for it. What is your problem. But Ok i will order a new one and throw this one in the trash. Thank you very much for the helpâŚ
WHY???
You can delete it and re-register it, but with a different id.
But as @kersing says, thereâs a lot of holes in this request and plaintively tagging a staff member for a free service is, as those pesky Brits call it, not cricket.
PS, we donât need the ânot an error message but an advisoryâ again, but if you do want assistance in the future, please format logs with </> tool.
PSS, I doubt this is creating a good impression of the company.
PSSS, If the deal is so big, why not buy a new one. Oh, wait, you thought of that, but throwing away a perfectly good gateway that can EASILY be reused - is this the way "to create a safe and liveable world?
Excellent selective reading.
I handed you a solution that will work if you happen to have a paid for instance already.
As well as refer to the solution if you are still using the sandbox.
However, feel free to buy new hardware now. Keep in mind you will be able to reuse the old hardware later when you can log a support ticket. Having two gateways cover a site (specifically for workshops) is advisable. If you want to know why, the forum contains the answers.
Keep in mind people without access to purge your gateway are trying to help solve your problem.
Having a few kerlink gateways myself I might be able to think of a work around, however your responses donât encourage me to spend some of my vacation time on the subject.
i am sorry for my reactions i tried to workaround myself if it use the kll_ttn script and try --naming it does not work it does not change te id. but i still donât get why a admin canât fix the problem in 10 seconds to purge it for me. 
.
The first very good reason is that you havenât âgotâ what TTN is about and the level of support that is available on this forum in so many ways as good as TTI, itâs just weâve not got access to the back end databases, what with us being volunteers. There have only been a half-dozen times over the last few years when thereâs been an issue that canât be resolved without database access.
But mostly because TTN is free to us but it costs TTI tens of thousands a year to run.
If they start providing one on one support, theyâd end up having to pay for someone at a mid-tier level to do all the things for people that they can already do for themselves.
And that would cannibalise even more than it already does the use of paid for instances which is where the tens of thousands comes from to pay for the free service.
Iâm still very much unclear why you canât use a different gateway id if you delete the current entry and re-register?
The Kerlink script forces a naming convention while registering gateways. The only way around this (at least last year) was to modify the shell script itself.
Crumbs! So many questions!
Canât you manually register it on the console with the EUI?
Is the script on the gateway itself?
How does the script authenticate against your account?
i tried but i had no luck will try it again this weekend. dig deeper in the script.
Hi Krishna,
Can you purge my deleted gateway?
24E124FFFEF8E1DC
24E124FFFEF8E16A
Best regards
Mohammed Ali
Hello,
I deleted my gateway in the Console with the aim to re-register it and now I am unable to re-register it. When I try, I receive the error: âSubmit failed â Already exists.â
Could you please help me fully remove or release the gateway so I can reuse the EUI?
Gateway EUI: DB3ADDFFFE690B42
Cluster/Region: eu1
Gateway ID (previous): agrosense-gateway
am actually in Ghana and am really a beginner with the TTN
Best Regards
Abdul-Aziz N-Yo
Gateway ID (previous):
agrosense-gateway
Did you try registering it with a different Gateway ID? The same will never work.
No, I did not try registering with a different ID, I have been trying with the same ID and EUI
Hint, try. If it does not work, copy-and-paste the exact (json) error message in you reply to help us determine what might be wrong. (Use the controls at the top of the text box for formatting for readability)
{
"code": 6,
"message": "error:pkg/util/store:id_taken (ID already taken, choose a different one and try again)",
"details": [
{
"@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",
"namespace": "pkg/util/store",
"name": "id_taken",
"message_format": "ID already taken, choose a different one and try again",
"correlation_id": "34b302b8460840fa866308ab0f5ad71a",
"cause": {
"namespace": "pkg/util/store",
"name": "already_exists",
"message_format": "already exists",
"correlation_id": "d9a548ff9bec4da9bf21b58ea31c7704",
"code": 6
},
"code": 6
}
]
}
As you can see if you read the error message, it says that the Id is already taken, so you have to use a different one. It even says that.
As littered all over this forum (search is your friend) and the docs about the gateway id having to be unique forever (RTFM!), the Id is not the EUI.
So just come up with a new Id like @kersing said 14 hours ago, use the EUI in the EUI box and profit.
Forum search will reveal the advice that there is never a good reason to delete a gateway - you can change ALL of its settings. Ironically, the only good time to delete a gateway is if you want to change the Id âŚ.
A post was split to a new topic: Gateway radio settings required