HARDWARIO Manager
STICKER has no buttons, no display, and no configuration cable. It is set up over NFC with HARDWARIO Manager, the HARDWARIO mobile app — you hold the phone against the device and the app reads or writes its settings.
This page explains how the app fits into working with STICKER. The app itself is documented in full under APPS → HARDWARIO Manager.
What you need
- A phone with NFC, running the app. Getting it onto the phone and switching NFC on is covered in Install the app.
- The device's secret key. STICKER talks over an encrypted NFC channel, so the app cannot read or write anything without it. You add each device once — see Saved STICKERs — and from then on the app fills the key in automatically.
Configuring without batteries
STICKER is NFC-ready and can be configured with no batteries inserted. The field from the phone powers the device long enough to store the settings, which it applies on its next boot. This is how a batch of devices is prepared before installation — see Configure a powered-off device.
It is also why an unprovisioned device stays radio-silent until it is given real LoRaWAN keys: see Features.
What you can do with a STICKER
| Task | Where it is documented |
|---|---|
| Read the serial number, firmware, and the LoRaWAN keys needed to register the device | Device info and LoRaWAN keys |
| Read and edit the full configuration — intervals, sensors, history, LoRaWAN | Configuration |
| Set threshold, state, and rate alarms | Alarm rules |
| Give many devices the same settings | Templates |
| Capture a whole fleet's configuration in one session | Scan multiple devices |
| Assign external 1-Wire probes to their slots | 1-Wire sensors |
| Test a device end to end | Sample sensor data |
| Read measurements stored on the device | Sensor history |
| Reboot, reset, or re-key a device | Reset a device |
Registering the device on a network server afterwards is covered under ChirpStack and The Things Stack.
Configuring over the shell instead
The app is the standard way to set up a STICKER, and the only one that needs no hardware beyond a phone. A device delivered in Debug Mode can also be configured from a console over a debug connection, which is intended for firmware development rather than deployment — see Developer Access and the full configuration parameter reference.