How can I delete a EUI registered twice by mistake? about gateway-remote-config HOT 3 CLOSED

I think you're mixing up two different things: TTN registration (which is complaining now as you said), and this repository that contains some remote config files.

For the issues with the local file versus the one in this repo, you can simply delete everything the installation, you can delete the following two folders to get rid of it: 1) ~/ic880a-gateway and 2) /opt/ttn-gateway. After that, restart the install and it should be clean as new.

For the issues regarding the TTN console, you need to ask in the forum or slack channels. But it looks like you registered that EUI in another user account, and the only way to register it in a new one, is to deregister it on the former one first. If you lost your credentials, you will need to create a new MAC address, you can do that by 1) using a different raspberry pi, or 2) adding a usb wifi dongle to it.

I will close this issue because there's no action required in this repo, but feel free to keep commenting to get to a solution.

from gateway-remote-config.

Hello Gonzalo,

Regarding the configuration files, I have already solved it by deleting the directories you mentioned and restarting the installation. But the log shows the following:

ttn@ttn-gateway:~ $ ls
Descargas Desktop Documentos ic880a-gateway Imágenes Música Plantillas Público Vídeos
ttn@ttn-gateway:~ $ sudo tail -f /var/log/syslog
[sudo] password for ttn:
Apr 16 22:39:47 ttn-gateway systemd[755]: Reached target Timers.
Apr 16 22:39:47 ttn-gateway systemd[755]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 16 22:39:47 ttn-gateway systemd[755]: Listening on GnuPG network certificate management daemon.
Apr 16 22:39:47 ttn-gateway systemd[755]: Listening on D-Bus User Message Bus Socket.
Apr 16 22:39:47 ttn-gateway systemd[755]: Reached target Sockets.
Apr 16 22:39:47 ttn-gateway systemd[755]: Reached target Basic System.
Apr 16 22:39:47 ttn-gateway systemd[755]: Reached target Default.
Apr 16 22:39:47 ttn-gateway systemd[755]: Startup finished in 201ms.
Apr 16 22:39:47 ttn-gateway systemd[1]: Started User Manager for UID 1001.
Apr 16 22:39:47 ttn-gateway systemd[1]: Started Session c2 of user ttn.
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # RF packets forwarded: 0 (0 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PUSH_DATA datagrams sent: 1 (226 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PUSH_DATA acknowledged: 100.00%
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ### [DOWNSTREAM] ###
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PULL_DATA sent: 3 (100.00% acknowledged)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # RF packets sent to concentrator: 0 (0 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # TX errors: 0
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ### [GPS] ###
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # Invalid gps time reference (age: 1587069516 sec)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # Manual GPS coordinates: latitude 36.72024, longitude -4.29749, altitude 180 m
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ##### END #####
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 50 ms
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 48 ms
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 48 ms
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 53 ms
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ##### 2020-04-16 20:39:06 GMT #####
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ### [UPSTREAM] ###
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # RF packets received by concentrator: 0
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # RF packets forwarded: 0 (0 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PUSH_DATA datagrams sent: 1 (226 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PUSH_DATA acknowledged: 100.00%
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ### [DOWNSTREAM] ###
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PULL_DATA sent: 3 (100.00% acknowledged)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # RF packets sent to concentrator: 0 (0 bytes)
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # TX errors: 0
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: ### [GPS] ###
Apr 16 22:40:36 ttn-gateway ttn-gateway[311]: # Invalid gps time reference (age: 1587069546 sec)

On the other hand, I think the issues regarding the ttn console are rare. Indeed, you are right, I had another account but I deleted the gateway from it and then I deleted the account. Also, a couple of days ago I registered the gateway on my current account and I had no problems. Then I made the configuration error (which I know has nothing to do with it but I'll tell you the order in which I did things). And then, I deleted the gateway again from ttn, updated the configuration and I couldn't register the gateway in the ttn server again because it detects that the EUI already exists. As I told you a couple of days ago I didn't have this problem.

So, in this moment, doing the whole process (not for the first time these days), nothing works. What I can say is correct:

• The JSON record in your repository.
• The connection of Raspberry to IC880a
• ISP enabled
• Power supply
• USB WiFi serving the gateway

I also have a LoRa node, which cannot be activated by the OTAA mode with this gateway. Therefore, I cannot continue working. I'm locked out.

I expect for new instructions. Thank you!

from gateway-remote-config.

SPI*

from gateway-remote-config.