TTN V3 Migration

[tobiascrackz]

Hello all :)
Is there already a guide on how to migrate this Gateway (Raspi + IC880) to TTN V3? Since there are always issues and migration differs from gateway to gateway this would be really awesome.

[Gepro-TeusVerbeek]

I just tried it. It seems very simple.

I have a local configuration so I just updated local_conf.json in /opt/ttn-gateway/bin. I changed the server address from router.eu.thethings.network to eu1.cloud.thethings.network.

If you have remote configuration configured you can change it in your remote file.

I think the script needs an update where the correct server address is selected whether you want to connect with stack V2 or V3. Or maybe the server address is automatically updated at some point so that the V3 stack gets the router.eu.thethings.network address.

[gonzalocasas]

Yes, the gateway migration is very simple but please do not do it generally just now. If you check the forum, or ttnmapper and many other resources, you'll find that applications need to be migrated first, otherwise, devices not compatible with v3 will stop being able to send data. So, we're actually postponing the gateway migration for a later time in the year.

[dbrgn]

There's a note now in the docs:

Since version 3.13 (released in May, 2021), The Things Network V2 routes traffic back and forth to The Things Stack Community Edition. When migrating your gateways to The Things Stack Community Edition, the coverage of the public community network won’t be impacted.

This means that we can start migrating our gateways now, right?

[gonzalocasas]

Oh cool! Yep, that might indicate so! Thanks for pointing it out!

[hatyri]

Is there an address specification somewhere else than Install.sh on line 182. If not, is it enough?

change

echo -e "{\n\t\"gateway_conf\": {\n\t\t\"gateway_ID\": \"$GATEWAY_EUI\",\n\t\t\"servers\": [ { \"server_address\": \"router.eu.thethings.network\", \"serv_port_up\": 1700, \"serv_port_down\": 1700, \"serv_enabled\": true } ],\n\t\t\"ref_latitude\": $GATEWAY_LAT,\n\t\t\"ref_longitude\": $GATEWAY_LON,\n\t\t\"ref_altitude\": $GATEWAY_ALT,\n\t\t\"contact_email\": \"$GATEWAY_EMAIL\",\n\t\t\"description\": \"$GATEWAY_NAME\" \n\t}\n}" >$LOCAL_CONFIG_FILE

to

echo -e "{\n\t\"gateway_conf\": {\n\t\t\"gateway_ID\": \"$GATEWAY_EUI\",\n\t\t\"servers\": [ { \"server_address\": \"eu1.cloud.thethings.network\", \"serv_port_up\": 1700, \"serv_port_down\": 1700, \"serv_enabled\": true } ],\n\t\t\"ref_latitude\": $GATEWAY_LAT,\n\t\t\"ref_longitude\": $GATEWAY_LON,\n\t\t\"ref_altitude\": $GATEWAY_ALT,\n\t\t\"contact_email\": \"$GATEWAY_EMAIL\",\n\t\t\"description\": \"$GATEWAY_NAME\" \n\t}\n}" >$LOCAL_CONFIG_FILE

[colonelmoutarde68]

I tried to upgrade my gateway to TTN v3 by updating the server address to eu1.cloud.thethings.network, and then by recreating it (with a new name) and event reinstalling the whole thing, but no success, it always says "• Disconnected" !

[umbertowski]

I tried to upgrade my gateway to TTN v3 by updating the server address to eu1.cloud.thethings.network, and then by recreating it (with a new name) and event reinstalling the whole thing, but no success, it always says "• Disconnected" !

i have the same problem

[gonzalocasas]

the script is now updated to point to v3 by default. please try and let me know. Later this year, we'll do a bigger update and switch to basicstation.

[Gerard880]

Hello Gonzalocasas,
Where can i find the updated script?
regards,
Gerard.

[TTNIdrija]

$ cd ~/ic880a-gateway
$ sudo ./install.sh

[dbrgn]

Full migration guide if you use local configuration:

• Create gateway in the new backend (https://console.cloud.thethings.network/)
• On the Raspberry Pi, use "git pull" to fetch the latest version of the setup script
• Run sudo ./install.sh spi (or without "spi" if you have the non-SPI version)
• Ensure that the gateway shows up as connected in the new backend
• Remove gateway from old backend

If you use remote configuration, then I think you'll simply have to update your config in https://github.com/ttn-zh/gateway-remote-config instead, and point it to eu1.cloud.thethings.network, followed by sudo ./install.sh spi.

[colonelmoutarde68]

Tried to reinstall the whole thing with the new script but still no luck (ic880a spi version)

[dechantw]

I don t know what s wrong. Using the latest setup script, its not possible to get the gateway connected.

[MystikReasons]

I have the exact same problem. The 880a is working just fine with the integrated test scripts on the RPI 4 but I can't get it connected to the TTN network.

And I noticed that the start.sh script isn't working, since the packet-forwarder does not exist like that anymore.

[dechantw]

Has somewone an idea where i can found the log files on the gateway. I m not so familar with Linux.