4. Conguration
Name
Type
Used
Description
OTAA
bool
both
true: use over-the-air activation (OTAA)
f alse: use activation by personalization (ABP)
DevEUI
bytes[8]
OTAA the 8 byte long DevEUI is used with OTAA to identify the
device on join. The default is predened in the hardware
and guarantees an ID that is unique world wide. Should
not be changed unless required by the network provider.
Hex format without 0x prex.
AppEUI
bytes[8]
OTAA ID dening the application used in the LoRaWAN net-
work. Hex format without 0x prex.
AppKey
bytes[16] OTAA Application Key as dened by the LoRaWAN network
operator. This is used to encrypt communication, so
keep it secret. Hex format without 0x prex.
OTAADelay int
OTAA Seconds to wait for a new attempt after an unsuccessful
OTAA join. The actual waiting time will be randomly in-
creased by up to a third of that amount, in order to avoid
devices repeatedly interfering with each other through
bad timing. The default value is 300, which means the
timeout between attempts is 300-400 seconds.
AppSKey
bytes[16] ABP
App Session Key as dened by the LoRaWAN network
operator. Hex format without 0x prex.
NetSKey
bytes[16] ABP
Network Session Key ad dened by the LoRaWAN net-
work operator. Hex format without 0x prex.
DevAdr
bytes[4]
ABP
Device Address as dened by the LoRaWAN network op-
erator. Hex format without 0x prex.
SF
int
both
Initial LoRa spreading factor used for transmissions.
Valid range is 7-12. The actual spreading factor used
might change during operation of the device if Adaptive
Data Rate (ADR) is used.
TxPower
int
both
Initial transmission output power in dBm. The LoR-
aWAN protocol allows only specic values: 2, 5, 8, 11,
14. The actual power used might change during opera-
tion if Adaptive Data Rate (ADR) is used.
ADR
bool
both
true: use adaptive data rate (ADR)
f alse: don't use adaptive data rate (ADR)
Table 3: LoRaWAN network parameters
wMBUS over LoRaWAN Bridge
12