Export devices as V3 JSON about ttn HOT 9 CLOSED

Work started in https://github.com/TheThingsNetwork/ttn/compare/feature/v3-export

@rvolosatovs please see what other fields we may need to transfer when migrating existing devices from v2 to v3.

from ttn.

OK. @neoaggelos please coordinate with @rvolosatovs and file an issue in lorawan-stack for documenting migrating devices from V2 to V3 via CLI.

from ttn.

The v2 API only allows talking to the Handler, so you can't talk to the NetworkServer.

The difference between OTAA and ABP devices in v2 is that OTAA devices have an AppKey and ABP devices don't.

from ttn.

When this is done and working, we may want to add the same to the console.

from ttn.

@neoaggelos is taking this over

@htdvisser can you let @neoaggelos know if the branch that you mentioned is still relevant and like we want this to be?

from ttn.

This was practically done. Only thing left was for @rvolosatovs to confirm what MAC settings need to be set in the network server.

from ttn.

OK. @neoaggelos please coordinate with @rvolosatovs and file an issue in lorawan-stack for documenting migrating devices from V2 to V3 via CLI.

There is TheThingsNetwork/lorawan-stack#1685

from ttn.

I'm having trouble telling apart OTAA from ABP devices from v2 with ttnctl. What I've seen is that all devices (both OTAA and ABP) have ActivationConstraints equal to Local. The console seems to be telling them apart by looking up the usages for devaddr prefixes in https://console.thethingsnetwork.org/api/handlers.

ttnctl discover broker --metadata is the closest I can get, but it does not include the usages of the prefixes.

Can we retrieve this info from the handler itself?

from ttn.

I don't think you can get this from the Handler, but you should be able to get this from the V2 NS. Indeed it's buried in a map value, @htdvisser probably knows best.

from ttn.