Configuration (config)
Device settings are read and written with the config command over the developer shell. See Firmware Setup for setting up the firmware and opening the console.
The config command and most parameters on this page apply to STICKER firmware v1.4.0. Key updates in v1.4.0 include:
- Radio-Silent Factory Default: The radio is disabled by default (
radio-mode off) to save power until activated via NFC using HARDWARIO Manager or shell. - Encrypted NFC Access: AES-CCM encrypted local command channel (
hio.stck:cmd/hio.stck:rsp) with anti-replay nonce protection. - Write-Once Claim Token: Immutable provisioning token (
config claim-token) for secure cloud onboarding. - Link Supervision: LoRaWAN link checks (
lrw-link-check-interval,lrw-link-check-fail-rejoin). - Sensor History: Buffer and replay capabilities (see Sensor History).
While this page documents interactive shell commands (config) accessed via an RTT debug connection, standard field configuration and commissioning are performed wirelessly over NFC using HARDWARIO Manager.
Command Syntax
config <subcommand> [value]
- Called without a value, the subcommand reads and prints the current setting.
- Called with a value, it writes the new setting.
Print every current value at once:
config show
A config write updates the setting in RAM and takes effect immediately, but it is not persisted until you run settings save, which writes the configuration to flash and reboots the device (see Maintenance). A change that is not saved is lost on the next power cycle. Alarm rules set with the alarm command (see Alarm Rules) persist immediately and do not reboot.
Sampling and Reporting Intervals
| Command | Argument | Description |
|---|---|---|
config interval-sample | 0, or 5-3600 (seconds) | How often sensors are sampled. 0 means sample once, immediately before each report. |
config interval-report | 60-86400 (seconds) | How often an uplink report is sent. Default 900 (15 minutes). |
Example - report every 10 minutes:
config interval-report 600
settings save
LoRaWAN & Radio Settings
| Command | Argument | Description |
|---|---|---|
config radio-mode | on / off | Enable or disable the LoRaWAN radio. Default in v1.4.0+ is off (Radio-Silent mode). |
config lrw-region | eu868 / us915 / au915 | Frequency region. |
config lrw-sub-band | 0-8 | US915/AU915 sub-band. 0 = all channels. Default 2. |
config lrw-network | public / private | Network type. |
config lrw-activation | otaa / abp | Activation method. |
config lrw-adr | true / false | Adaptive Data Rate (ADR). |
config lrw-deveui | 16 hex digits | Device EUI. |
config lrw-joineui | 16 hex digits | Join EUI (AppEUI). |
config lrw-nwkkey | 32 hex digits | Network Key (OTAA). |
config lrw-appkey | 32 hex digits | Application Key (OTAA). |
config lrw-devaddr | 8 hex digits | Device Address (ABP). |
config lrw-nwkskey | 32 hex digits | Network Session Key (ABP). |
config lrw-appskey | 32 hex digits | Application Session Key (ABP). |
config lrw-link-check-interval | 0-255 | Request a LinkCheckReq every Nth uplink. 0 = disabled. Default 5. |
config lrw-link-check-fail-rejoin | 1-255 | Link-check failures before an OTAA rejoin is attempted. Default 5. |
Example - EU868 with OTAA and enabling radio transmission:
config lrw-region eu868
config lrw-activation otaa
config lrw-deveui 0102030405060708
config lrw-joineui 0807060504030201
config lrw-appkey 0102030405060708090A0B0C0D0E0F10
config radio-mode on
settings save
Sensors and Capabilities
Capability flags tell the firmware which hardware is present on a given variant. They are normally set during factory provisioning and should not be changed in the field.
| Command | Argument | Description |
|---|---|---|
config cap-barometer | true / false | Barometric pressure sensor present. |
config cap-pir-detector | true / false | PIR motion detector present. |
config cap-light-sensor | true / false | Ambient light sensor present. |
config cap-accelerometer | true / false | Accelerometer present (orientation, motion, free-fall). |
config cap-w1-sensors | true / false | 1-Wire bus enabled; attached sensors are auto-detected on scan. |
config cap-hall-left | true / false | Hall left sensor present. |
config cap-hall-right | true / false | Hall right sensor present. |
config cap-input-a | true / false | External input A present. |
config cap-input-b | true / false | External input B present. |
Sensor Settings:
| Command | Argument | Description |
|---|---|---|
config accel-motion-sensitivity | off / low / medium / high | Accelerometer motion-detection sensitivity. Default off, which powers the accelerometer down. |
config sensor1-rom ... config sensor4-rom | 16 hex digits | Bind a 1-Wire sensor to slot 1-4 by its ROM serial. All-zero = empty slot. |
Pulse Counters
| Command | Argument | Description |
|---|---|---|
config hall-left-counter | true / false | Count pulses on the left hall switch. |
config hall-right-counter | true / false | Count pulses on the right hall switch. |
config input-a-counter | true / false | Count pulses on external input A. |
config input-b-counter | true / false | Count pulses on external input B. |
For wiring details (DIP switches, 1-Wire, dry contact, analog), see STICKER Input Wiring.
Device Identity & NFC Security Architecture
These parameters manage device identity, NFC access control, and claim provisioning. They are set during factory provisioning and should not be altered in standard operation.
| Command | Argument | Description |
|---|---|---|
config serial-number | 10 decimal digits | Device serial number. |
config secret-key | 32 hex digits | Device secret key used to secure the local NFC channel via AES-CCM. Readable/writable over shell only. |
config nonce-counter | Integer | Anti-replay nonce counter enforced on the encrypted NFC and LoRaWAN command channels. |
config claim-token | 32 hex digits | 128-bit write-once device claim token. Once set during commissioning, it becomes immutable to lock unit ownership to a backend. |
config calibration | true / false | Enable calibration mode (factory use). |
Encrypted NFC Local Access Channel
From firmware v1.4.0 onwards, NFC local read/write transactions are secured against eavesdropping and unauthorized reconfiguration:
- AES-CCM Security: Smartphone communication via HARDWARIO Manager uses an encrypted AES-CCM channel operating over NDEF records (
hio.stck:cmdfor requests andhio.stck:rspfor responses). - Anti-Replay Mechanism: Each transaction evaluates and increments the
nonce-counterto prevent replay attacks from captured NFC sessions. - Claim Token Provisioning: The 128-bit
claim-tokenallows a physical unit to be bound to a customer's cloud instance before or during deployment, without requiring an immediate LoRaWAN Join session.