

For this change to take effect, the end device does not need to perform a re-join. The Network Server will then start using the Rx1Delay of 6 seconds for scheduling downlinks. The end device will answer with an RxTimingSetupAns MAC command in the next uplink.

The Network Server will schedule an RxTimingSetupReq MAC command to communicate a new Rx1Delay of 6 seconds to the device. To see Rx1 delay change in the current session, modify the 1-delay parameter: ttn-lw-cli end-devices update -application-id -device-id 1-delay RX_DELAY_6 For demonstration purposes, in this example we use 6 seconds. The Things Stack configures the Rx1Delay to 5 seconds by default to accomodate for high latency backhauls and/or peering with Packet Broker, so this is the recommended configuration. If no settings are provided on device creation or unset, defaults are first taken from the device Frequency Plan if available, and finally from Network Server Configuration. See how this applies to the Rx1 delay parameter in the example below.
#Qr factory mac how to#
Learn how to install the CLI MAC Settings and MAC State
