Skip to main content

Configuration Reference

GLIDER stores configuration in non-volatile memory (NVS), so settings survive power cycles and reboots. You can change configuration through either console:

  • AT console: AT$CONFIG="<module>","<key>",<value>
  • RTT console (Zephyr shell): <module> config <key> <value>

After making changes, always save them to flash:

AT&W

This persists the new values and reboots the device. To wipe everything back to factory defaults:

AT&F

Listing configuration

GoalAT commandShell command
List every moduleAT$CONFIG?config show
List one moduleAT$CONFIG="<module>"<module> config show
Read one keyAT$CONFIG="<module>","<key>"<module> config show <key>
Show full schemaAT$CONFIG=?-

The schema (AT$CONFIG=?) reports each key's type, range, default and a one-line description - useful for discovery.

Global app settings

These keys apply to the whole device.

KeyTypeRangeDefaultDescription
interval-sampleint (s)5 - 360060How often the firmware reads sensors and evaluates alarms.
interval-sendint (s)30 - 86400300How often the firmware encodes a CBOR payload and uplinks it.
downlink-wdg-intervalint (s)0 - 1209600129600 (36 h)Downlink watchdog. If the cloud sends no downlink within this period, the device reboots. 0 disables the watchdog.

Example

app config interval-sample 30
app config interval-send 120
AT&W

Digital inputs

GLIDER has two galvanically isolated digital input channels (CH1 and CH2). Each channel can run in one of three modes:

ModeBehavior
disabledThe channel is powered off - no counting, no events.
counterSelected edges (rising / falling / both) increment counters. Counters are sent in every CBOR payload.
eventEach edge produces a timestamped event. Events are streamed in the next CBOR payload (up to 64 per channel, per send cycle).

Per-channel keys

The same keys exist for both channels, prefixed with 1- (CH1) or 2- (CH2):

KeyTypeRangeDefaultDescription
<n>-modeenumdisabled / counter / eventdisabledChannel mode.
<n>-active-durationint (ms)0 - 60000100Minimum time the input must stay active (rising edge debounce).
<n>-inactive-durationint (ms)0 - 60000100Minimum time the input must stay inactive (falling edge debounce).
<n>-cooldown-timeint (ms)0 - 6000010Minimum time between two registered transitions.
<n>-counter-edgeenumrising / falling / bothbothWhich edges increment the counter (only used in counter mode).
<n>-event-typeenumactivation / deactivation / bothbothWhich transitions create events (only used in event mode).

Example - count pulses on CH1

inputs config 1-mode counter
inputs config 1-counter-edge rising
inputs config 1-active-duration 5
inputs config 1-inactive-duration 5
AT&W

This counts every rising edge on CH1 as long as the input stays high for at least 5 ms (and low for at least 5 ms between pulses).

Thermometer slots (therm)

Eight independent slots, one ROM code per slot. Empty slots are skipped in the cloud payload.

KeyTypeSizeDefaultDescription
18hex8 bytes0x00…DS18B20 ROM serial bound to that slot. 0x00… = empty.
tip

In practice you should not edit these by hand - use therm scan --save to discover and bind sensors automatically. See External Temperature Sensors.

Alarms

Up to 32 independent alarm rules can be configured. Each rule watches one thermometer slot and toggles between active and inactive based on a threshold with hysteresis:

  • The rule activates when temperature ≥ threshold.
  • The rule deactivates when temperature ≤ threshold − hysteresis.

Each transition is recorded in the alarm events buffer and uploaded with the next CBOR payload.

The same four keys exist for every rule, prefixed with <n>- (1-32):

KeyTypeRangeDefaultDescription
<n>-enabledbool-falseMaster switch for the rule. When false, the other keys for this rule are hidden.
<n>-thermint1 - 81Which thermometer slot the rule watches.
<n>-thresholdfloat (°C)−55 - 12550Activation threshold.
<n>-hysteresisfloat (°C)0 - 505Deactivation offset below the threshold.

Example - alarm on slot 1 if it exceeds 30 °C

alarm config 1-enabled true
alarm config 1-therm 1
alarm config 1-threshold 30
alarm config 1-hysteresis 5
AT&W

When slot 1 reads ≥ 30 °C the firmware fires the alarm; it clears again when the reading drops to ≤ 25 °C.

Saving and resetting

ActionCommand
Save and rebootAT&W
Factory reset (wipe everything)AT&F
Reboot without savingAT$REBOOT
caution

AT&F is destructive - every configured slot, alarm rule and interval is reset to factory defaults. There is no undo.