Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/sensorsMobile, firmware e hardware

sensors

⁨Select, compare, and integrate sensors for Arduino, ESP32, robotics, model-making, and home automation with focus on signal quality, false positives, debounce, and practical wiring. Use when asked which sensor to choose, how to detect an event reliably, how to map signals into code, or how to design⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/sensors

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
f5qm7sZ2ok…ySo0gxBQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto4819e744…8ddc1df9
4819e744e109…f91a8ddc1df94 file · ⁦3.6 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/hardware/sensors@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

This skill is for picking the right sensor and making it behave in the real world, not just on paper.

Use it when the hard part is reliability: noisy rooms, bounce, bad mounting, false triggers, threshold tuning, or choosing between several sensor types.

Workflow

  1. Define the event or quantity.

    • presence, passage, open/closed, impact, orientation, distance, climate, occupancy, leak, smoke
  2. Define the environment.

    • indoor/outdoor
    • noisy people nearby
    • vibration, dust, sunlight, reflective surfaces
    • battery vs mains
  3. Prefer the sensor that directly measures the thing that matters.

    • impact -> piezo / vibration / accelerometer, not microphone
    • path crossing -> break-beam or switch, not generic ranging by default
    • open/closed -> reed / Hall / microswitch
  4. Specify the signal model.

    • digital or analog
    • active-low or active-high
    • debounce, hysteresis, cooldown, baseline drift, edge detection
  5. Describe failure modes and fallback options.

    • false positives from noise
    • missed triggers due to blocking code
    • calibration drift
    • ambiguous multi-sensor events

Decision rules

  • If the environment is noisy, avoid microphones unless audio itself is the signal.
  • If the event is a physical crossing, start with break-beam.
  • If the structure feels the event, mount the sensor on the structure.
  • If two sensors are viable, prefer the one with easier calibration and clearer failure modes.

Output rules

When recommending a sensor or architecture, include:

  • why this sensor fits the environment
  • why common alternatives are worse here
  • wiring/interface type
  • tuning notes: debounce, threshold, cooldown, sampling
  • whether the project needs edge-based logic, not just level polling

When to load references

  • Load references/sensor-selection.md when choosing among sensor families.
  • Load references/signal-quality.md when debugging false triggers, debounce, or noisy data.
  • Load references/home-automation.md when the task is about domotica, occupancy, binary sensors, or practical monitoring.

Resources

references/

  • references/sensor-selection.md — selection workflow and concrete recommendations by use case.
  • references/signal-quality.md — debounce, hysteresis, cooldown, mounting, and ambiguous-event handling.
  • references/home-automation.md — binary-sensor style thinking and practical smart-home sensor patterns.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd5684819e744Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login