Skip to main content

Configuration Template Generator

Build a STICKER configuration template below: open a section, tick the settings you want, set their values, and the tool encodes them into the AppConfigMessage payload the device ingests over NFC. The result is shown as a hex string and a QR code, and you can paste an existing template's hex back in to decode it into the form.

Only ticked settings are encoded, so a template carries just what you choose and can be reused across many devices. The form covers the template-friendly settings only; per-device identity and secrets (serial number, LoRaWAN keys and EUIs, session keys, 1-Wire ROMs, and similar) are intentionally left out because they cannot be shared across devices.

Open a section and tick the settings to include. Hover or focus a setting to see what it does and its allowed values.
LoRaWAN basics
Radio region for the LoRaWAN band: EU868, US915 or AU915.
US915/AU915 sub-band. 0 to 8 (default 2); 0 enables all channels.
LoRaWAN sync word: PUBLIC or PRIVATE network.
Join method: OTAA (over-the-air activation) or ABP (activation by personalization).
Interval
s
How often the device measures. 5 to 3600 s, or 0 to sample once right before each report.
s
How often the device sends an uplink. 60 to 86400 s (default 900).
Sensors
Enable the hall-left sensor.
Enable the hall-right sensor.
Enable input A.
Enable input B.
Enable the light sensor.
Enable the barometer.
Enable the PIR detector.
Enable the 1-Wire bus and auto-detect probes.
Enable the accelerometer.
Accelerometer motion detection: OFF, LOW, MEDIUM or HIGH.
Enable the hall-left pulse totalizer.
Enable the hall-right pulse totalizer.
Enable the input-A pulse totalizer.
Enable the input-B pulse totalizer.
Alarms
s
Minimum seconds between alarm uplinks. 0 to 3600 s; 0 disables the limit.
s
How long the red LED stays on when an alarm fires. 1 to 60 s (default 10).
No alarm rule yet. Add one to include it in the template.
AppConfigMessage hex · 0 byte(s)
(no settings selected)
Template (JSON)
(no settings selected)
Select at least one setting to generate a QR code.
Replaces the current selection. Settings outside this form are ignored.

This is the plaintext config template (an AppConfigMessage protobuf). On a production device the NFC Configurator encrypts it per device before writing it over NFC.

How to use it​

  1. Open a section (LoRaWAN basics, Interval, Sensors or Alarms; they are collapsed by default) and tick the settings you want. Hover or focus a setting to see a short clue with its meaning and allowed values.
  2. Numbers are range-checked (for example sample interval 5 to 3600 s, report interval 60 to 86400 s); an out-of-range value is flagged and left out of the payload until you correct it.
  3. For Alarms, click + Add alarm rule to add a slot (up to 16), then choose its source and quantity and set the thresholds. Use Remove to drop a rule, or set Action to Clear slot to wipe that slot on the device. With no rules added, the template carries no alarms.
  4. Copy the hex string, or use the QR code (it carries the same hex), to store or share the template.
  5. To inspect an existing template, paste its hex into Read a template from hex and click Load template. The form, including any alarm rules, is repopulated with what the template contains, and the sections it sets are expanded automatically so you can see what changed (settings outside this form are ignored).
This is the plaintext template

The bytes shown here are the unencrypted AppConfigMessage. On a normal device the tag payload must be encrypted with the device's secret key (AES-CCM), so you cannot write this hex straight to a production STICKER. The NFC Configurator performs that per-device encryption for you when it writes the configuration. The raw payload is accepted directly only by a plaintext validation build.

Field notes
  • Switches are explicit: a capability set to off writes that capability = false, it does not leave it untouched. Tick a row only for settings you want the template to carry.
  • Numbers show their allowed range in the help clue and are validated. Sample interval also accepts 0 (sample right before each report) and alarm limit accepts 0 (disabled).
  • Alarm rules are encoded into the same 17-byte packed slots used by the Downlink Commands Generator and the alarm shell command; here you build them with the rule editor instead of pasting hex.

For the full list of configurable parameters and their meaning, see Configuration. To write a finished template to a device, see the NFC Configurator and its Setup guide.