Device Dialog — Settings

The Settings tab contains the device’s protection and data quality mechanisms. These settings control how the system validates sensor readings, handles errors, detects anomalies, and filters noise.

Changes are not saved automatically — click 💾 Save Settings at the bottom after making changes.

Section 1: Noise Filtering (Sampling)

Controls how many hardware readings are averaged into a single value.

FieldRangeDefaultDescription
Sample Count1–10From templateHow many individual readings to take per measurement cycle. Higher = smoother but slower.
Sample Delay0–500 msFrom templatePause between individual readings. Helps stabilize the sensor between samples.
ButtonDescription
Disable FilteringSets count = 1, delay = 0 (pass through raw data)
Restore RecommendedResets to the template’s recommended values

Section 2: Range Validation

Defines the acceptable value range for this sensor. Any reading outside this range is considered invalid.

FieldDescription
Min ValueMinimum acceptable reading. Hardware limit shown as reference.
Max ValueMaximum acceptable reading. Hardware limit shown as reference.

You cannot set min/max beyond the hardware limits defined by the device template.

Section 3: Frozen Sensor Detection (Anomaly)

Detects when a sensor is returning the same value repeatedly — a common symptom of hardware failure or stuck ADC.

FieldRangeDefaultDescription
EnableToggleOffMaster switch for anomaly detection
Max Consecutive1–100040How many identical readings in a row trigger the anomaly
Cooldown1–3600 sec10After triggering, wait this many seconds before checking again
Variance Delta0+0.05How much variation is allowed while still considering readings “identical”
ActionSelectIgnoreWhat to do when detected

Anomaly Actions

ActionDescription
IgnoreLog the anomaly but continue using the readings normally
Alert OnlySend a notification alert but continue using the readings
Mark ErrorFlag the sensor as “frozen” error state — readings are rejected

If the device is currently in frozen state, a red ↻ Reset Frozen button appears to clear the flag after fixing the physical issue.

Section 4: Retry Strategy

Controls what happens when a sensor read command fails (timeout, communication error).

FieldRangeDefaultDescription
Retry Count0–103How many times to retry after a failed read
Retry Delay0–5000 ms100Pause between retries

Setting retry count to 0 means no retries — any failure immediately triggers the fallback.

Section 5: Fallback Action

Determines what the system does when a reading is invalid or all retries have failed.

OptionDescription
ErrorReport the reading as an error. The flow or program receives an error event and can react (stop, pause, etc.)
Use Last ValidSubstitute the most recent known-good value. Requires configuring a stale limit.
Use DefaultSubstitute a fixed default value that you define.

⚠ Substituting values can mask real hardware problems. Use with caution.

How All 5 Sections Work Together

Hardware Read Command
       ↓
[Noise Filtering] — Average N samples
       ↓
[Range Validation] — Is value within min/max?
   ├── YES → Value accepted ✓
   └── NO → Value rejected
              ↓
       [Retry Strategy] — Try again (up to N times)
          ├── Retry succeeds → Value accepted ✓
          └── All retries fail
                    ↓
             [Fallback Action]
              ├── Error → Report error event
              ├── Use Last Valid → Check data age
              └── Use Default → Substitute fixed value ✓

[Anomaly Detection] — Running in parallel, counting repeated values