Processing the Downlink Packet

Process the Application Data

When coding your application, you will identify several scenarios that require a downlink, such as changing settings, frequency of broadcast, or triggering a real-world action such as opening or closing a valve. You can assign each of these a different FPort value, between 1 and 223, and select an encoding method. The end device must use these rules to interpret the FPort value and decrypted FRMPayload value and take the relevant actions. Learn more about designing configuration by downlink in our paper Downlink Configuration Versus Firmware Version.

If either the port or payload cannot be recognized, the message must be ignored.