Network-related settings

Join-retry period

SET

This command is used to set the period (T) of LoRaWAN join request sending from the device, in case it was unable to join the network from the first attempt.

Byte index	Hex value – Meaning
0	10 – The command code.
1	$T, [s] = XX * 5.$ Value 0x00 isn’t applicable. Default value: 0x78 * 5 = 600 sec = 10 minutes.

Example command: 0x10F0 – the server sets join request send period to 20 minutes.

GET

This command is used to get the period (T) of LoRaWAN join request sending from the device, in case it was unable to join the network from the first attempt. Server sends the command code and the response is sent together with the next keep-alive command.

Byte index	Sent request	Received response
0	19 – Command code.	19 – The command code.
1		XX – Network join retry period value. $T, [s] = XX*5$

Example command sent from server: 0x19;

Example command response: 0x19C6 => T = 0xC6*5 = 198*5 = 990s = 16.5 minutes.

This join retry period (T) must comply to LoRaWAN messages duty cycle. Otherwise the join request will be sent on the next attempt. In most of cases, min. acceptable value for T is 240s. Recommended are higher values, for less battery discharge, e.g. 480s.

This join retry period (T) is for the first 15 sent messages. After, the used LoRaWAN stack automatically changes the possibility to send join request to ~20 minutes for 20 network join attempts. If the device is still not joined to the network after these 20 attempts, next join request can be sent after ~3 hours and 15 minutes.

LoRaWAN Region

This command reports the LoRaWAN Region your device is setup to work in. Make sure it matches you network as LoRaWAN regions/bands are country dependent. This region is hardcoded in the FW and the user can not change it, only report on it. The keep-alive in the command response is omitted for clarity.

GET

Byte index	Sent request	Received response
0	A4 – Command code	A4 – Command code
1		Radio region: 00 => EU868 01 => AS923 02 => AU915 03 => US915

Example command, [Hex]: A400 – extracting the 1st byte value we get 00[HEX], thus the device operates in the EU868 LoRaWAN band.

Set Send event button later when it is allowed

The device may not always be able to send the command right now. The reason for this is the duty-cycle of LoRaWAN devices, which limits the amount of time a device transmits on the radio spectrum in order to be compliant with the EU regulations.

The duty-cycle depends on the Spreading factor. E.g. on SF12, the device can send one command every approx. 2m30s and on SF7, it can send a command approx. every 15 seconds.

This command is used to define the device behavior when it is not allowed to send the signal right now due to duty-cycle restrictions. You can choose to not send the signal at all or to send it at earliest convenience. The command is described in Table 9.

Byte index	Hex value – Meaning
0	1E – The command code.
1	00 - Do not send the button event later when allowed. Default value: 00 01 - Send the button event later when allowed.

Table 9

Example command, [HEX]: 1E01 – the server sets device send the button event later when the LoRaWAN duty-cycle allows it.

Get Send event button later when it is allowed

This command is used to retrieve the device behavior on sending an uplink when the duty-cycle restrictions do not allow it to do it in real-time. The sent command request and the received command response are described in Table 10.

Byte index	Sent request	Sent request
0	1F – Command code.	1F – The command code.
1		00 - Do not send the button event later when allowed. 01 - Send the button event later when allowed.

Table 10

Example command sent from server, [HEX]: 1F;

Example command response, [HEX]: 1F01 - the device send the button event later when the LoRaWAN duty cycle allows it.