Auto generate DevEUI and AppEUI in TheThingsStack v3

[ecosoph (Markovicz)]

Hi Guys,

I’ve noticed that there’s no option for auto generate AppEUI and DevEUI in thethingsstack v3 anymore (as compared to TTN):

To be honest, I don’t have so much glue so I needed to google a bit to find related threads:

Registration of node with pre-configured LoRaWAN keys

Hi, When buying a commercial node, how can you register it on a network ? I understand the keys (DEVEUI, Apsskey and Appeui) must match the server side. Does a device manufacturer needs to label his device with these 3 keys ? Or is just the DEVEUI sufficient ? How do the remaining keys match ? Thanks!

Register new devices on join

Custom RF95 hope solution: HopeRF RFM95 and arduino a low cost LoRaWan solution - disk91.com - the IoT blogdisk91.com – the IoT blog

What is the recommended procedure for adding a custom-built LoRa device using OTAA to v3?

Thank you a lot!

EDIT: I’ve digged a bit further:
https://lora-developers.semtech.com/library/tech-papers-and-guides/the-book/deveui/

One solution could be buying cheap ICs from e.g. farnell with a EUI-64 identifier from what I understood:
https://de.farnell.com/microchip/24aa025e64t-i-ot/eeprom-2k-256x8-1-8v-seriell-6sot/dp/2345565?st=eui

[kersing (Jac Kersing)]

@ecosoph

One solution could be buying cheap ICs from e.g. farnell with a EUI-64 identifier from what I understood:

That is certainly the best solution if you only need small amounts of EUIs.

However if you searched this forum a bit you should have found this question popped up a few weeks ago and the pragmatic solution for now is to use V2 to generate EUIs and use them on V3.

[ecosoph (Markovicz)]

@kersing the v2 generated EUI came up to my mind as well somewhen yesterday after posting this question. I did some forum search but couldn’t find it. Sorry for the spam.

[bluejedi]

@ecosoph

I did some forum search but couldn’t find it.

Really?

A simple search for DevEUI would have shown the following in top of the results:

Unable to generate new DevEUI in V3 Console [known issue]

When adding a new device in the V3 Console it is currently not possible to generate a new DevEUI. This is a known issue. Generating new DevEUI will be added in a new release. (The DevEUI is actually not generated but will be issued from a valid range of DevEUI.) The DevEUI is required for adding a new device to a V3 application. Existing V2 devices will already have a DevEUI but many new (DIY) devices will not. As workaround a temporary device can be created in the V2 console and then copy …

[ecosoph (Markovicz)]

@bluejedi alrighty, sorry! Shall we lock or delete my thread?