thanks for the fast reply. I do hope we can find a way to resolve this
…Due to the long validity of (old) gateway access tokens, we can’t
release gateway IDs to be registered by different users. … if your old
account is deleted, that will not work.
Reading the forum, we are not the only company, group or person to run into
this issue as we get familiar with the hardware and software. The way we
initially configured the package resulted in the gateway device never (so
far as we can tell) coming active.
To try and fix this, we deleted the original account, assuming, wrongly as
we found out, that this would also unregister the EUI. What we are now left
with is a ghost / orphan EUI and no obvious way to recover it other than
To be clear, we ARE NOT a different user, it’s the one and same Sandbox kit
with the same EUI.
…register your gateway under a different EUI
I really don’t see how this can be a technologically valid option. My
understanding is that each gateway device has a unique EUI. Surely the last
thing TTN wants is people registering random EUI IDs that don’t align with
the hardware, or worse, duplicate other gateway nodes. Or have I missed
If not, what do you suggest for the EUI? Change the last EUI hex digit?
Just make one up?
I’d need to be absolutely certain that the TTN server apps can handle a
different EUI and don’t query the hardware for the actual EUI and then
behave in an undefined manner.
Releasing our gateway ID so we can reregister it correctly would appear to
be the ideal and simplest solution for everyone.
So over to you. What can you do to solve this? What would you need from us
to do it?