The best thing of TTN is that while creating an application and registering an end device node in the application, the AppEUI and AppKey both are automatically generated for us. It takes away the work from the end device programmer.
But now I am using the gateway from an external vendor who also gives me access to his cloud server running the network server. Here while creating an application and registering an end device node, the AppEUI and AppKey are not generated automatically. I have to manually enter them. So, I just select some random AppEUI and random AppKey and enter them and successfully register the device in the network server and start working with it. My questions are:
Are there any rules for generating an IEEE EUI-64 AppEUI. Should I follow any guidelines to create it. For testing and hobby projects it is OK. If I want to deploy a commercial project then can I still generate an AppEUI randomly or should I buy it from certain standard regulatory body just like device manufacturers do it in the case of DevEUI.
For a particular application (having an unique application Id in the network server), once the AppEUI is generated, should all the devices which will get registered in that application in the future have the same AppEUI? Can the AppEUI for 2 different end node devices under the same application be different. I mean while provisioning the end node devices with AppEUI and AppKey, can I provision 2 different end node devices, registered under the same application, with 2 different AppEUI’s ? In case of TTN I do not need to do that as TTN gives me the same AppEUI for any number of devices registered under a particular application. But the network server provided by my gateway manufacturer allows me to provision the 2 different end node devices, registered under the same application, with 2 different AppEUI’s. Is this correct behavior?
Please provide valuable suggestions.
Thanks and Regards,