Okay, so it does (should) support registering it to, e.g., TTN? Then I should not have deleted my earlier answer after I ran into that warning text.
I disagree. Yes, in V2 using the same AppEUI among multiple applications seems to work. (Or does it?) But will it still work if the community network migrates to V3? Or if you want to move to another network? I don’t know.
I’d say that the following:
1.3. AppEUI / JoinEUI
The LoRaWAN AppEUI, now known as the JoinEUI (they are sometimes used interchangeably), is consistent among Radio Bridge products and thus is not listed on the product labels. Earlier products use a generic, non-unique, JoinEUI, and newer products use a unique JoinEUI as described in the following table.
Table 1 AppEUI/JoinEUI for Radio Bridge Products
||Used in the following product families: RBS301, RBS304, RBS305, and RBS306
||Used in product families not listed above
…is really bad if the devices are registered outside of the Radio Bridge platform. I really feel that each off-the-shelf device should have its own unique AppEUI (or allow for changing it).
0101010101010101 is not even owned by them. They do own the block of 16,777,215 addresses of that second EUI-64 but only seem to be using one value for all devices of some type? Also, I don’t understand their “newer products use a unique JoinEUI as described in the following table” while that table refers to a single non-unique value? Maybe it’s just a documentation error?
Surely we noticed, but JoinEUI is a LoRaWAN 1.1 term. And it’s actually a different thing, although a 1.0.x network that is oblivious about the existence of 1.1 can just perform a 1.0.x OTAA if a user has registered the JoinEUI of a 1.1.x device as the AppEUI on a 1.0.x network. When that happens, a 1.1.x device can tell from the Join Accept that it should fall back to 1.0.x while deciphering the Join Accept to derive the secrets, and in all its subsequent communications.
So, in LoRaWAN 1.0.2 (which is what the TTN Community Network uses, and what this specific device uses), it’s still AppEUI. For the 1.1.x JoinEUI:
The JoinEUI is a global application ID in IEEE EUI64 address space that uniquely identifies the Join Server that is able to assist in the processing of the Join procedure and the session keys derivation.
I’d say that the JoinEUI should again be unique for each off-the-shelf device, as a manufacturer cannot make assumptions about the device’s usage.
Long story short, if one does not want to use the Radio Bridge services, then to make sure things work in the future I’d return the devices and request the following:
Note that the AppEUI/JoinEUI can be modified at the time of manufacturing to match the end customer’s requirements. Please contact Radio Bridge for more details on customization and pre-configuration.