right now LoRa 1.0.3 and 1.1 are published as well as LoRa backend interfaces v1.0:
LoRa 1.0.3 and 1.1 are specifying quite different formats of DevAddr. Version 1.0.3 (see 6.1.1 End-device address) defines:
NwkID[31…25] | NwkAddr [24…0]
without a proper explenation what NwkID or NwkAddr should look like.
LoRa 1.1 uses a different definition (184.108.40.206 End-device address):
AddrPrefix [31…32-N] | NwkAddr [31-N…0]
LoRa backend interfaces 1.0 uses (see 13 DevAddr Assignment):
TypePrefix | NwkID | NwkAddr
All three fields can have varying lengths, but this format still matches the LoRa1.1 DevAddr definition. The TypePrefix + NwkID are components of the AddrPrefix as it is defined within LoRa 1.1 spec.
NwkAddr between LoRa 1.1 spec. and backend spec. are the same.
The specification for the backend defines a DevAddr which is compatible to LoRa 1.1 but not with LoRa 1.0.3 . It is also clear, that the definition of NwkID differs between LoRa 1.0.3 and LoRa1.1 / Backend1.0.
Are the different LoRa versions are really using incompatible or formats of DevAddr or am I missing some detail?
Also, the backend specification mentions, that some roaming modes are possible with LoRa 1.0 but also only the LoRa 1.1 DevAddr is mentioned within the backend specification. How can one use roaming with LoRa 1.0 if the defined DevAddr seems incompatible?
Well folks, that’s it. I would have liked a more structured question, but quite now my brain is fried from reading LoRa specifications…