Change the address in global or local json.conf and erm, carry on.
What do you need that may need a GUI - the Pi should just crack on and you can use the command line to view the forwarder log. Adding a full (or just bits of X) GUI will put a load on that’s unwarrented for its use as a gateway.
The easiest way would probably be to use Balena with the BasicStation setup. There are tutorials on-line.
The legacy TTN packet forwarder (written in Go) is not supported in V3. So a replacement packet forwarder will be required. BasicStation is the TTN prefered option. Other options are the Semtech UDP packet forwarder or MP Forwarder.
Hi Jac @kersing will shortly be moving the 1st ~5-10 Pi (various flavours to test) GW’s from estate over to V3 - all currently running your MP… simple change of target address will do the trick or do I need to go deeper? Tried simple switch to of one to Nick’s @descartes V3 instance a few weeks back to test but didnt go well (discovered RAK Conc card on the system had ‘gone deaf’!) so parked project until more time and focussed on other GW’s instead.
Are you running Balena? In that case you will need updated scripts which are not there yet (afaik) because the current script pulls the gateway config from V2.
For plain Linux gateways updating the server address for ‘semtech’ transport is sufficient. For ‘ttn’ transport you need to update ‘serv_gw_id’ and ‘serv_gw_key’ as well.
No dont use Balena - so many disparate GW types a harmonised solution somewhat lost on me - though perhaps I should try for some of the more common types.
Will make sure I look at the id’s/keys as well… expect panicked calls next week
I have same problem build a pi gateways as per the tutorial, now not working, can someone guide me though the update to getting it to work on v3 please