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 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/sensorsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package4819e744…8ddc1df9
4819e744e109…f91a8ddc1df94 files · 3.6 KBScanLowno findings
Sourcegithub.com/AeonDave/malskill/tree/main/hardware/sensors@21cd568
On this page
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
Define the event or quantity.
- presence, passage, open/closed, impact, orientation, distance, climate, occupancy, leak, smoke
Define the environment.
- indoor/outdoor
- noisy people nearby
- vibration, dust, sunlight, reflective surfaces
- battery vs mains
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
Specify the signal model.
- digital or analog
- active-low or active-high
- debounce, hysteresis, cooldown, baseline drift, edge detection
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.mdwhen choosing among sensor families. - Load
references/signal-quality.mdwhen debugging false triggers, debounce, or noisy data. - Load
references/home-automation.mdwhen 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.
Files in this version
references/35.8 KB
- home-automation.md1.5 KB
- sensor-selection.md2.5 KB
- signal-quality.md1.8 KB
- SKILL.md2.9 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 4819e744 | Signed | – |
More from AeonDave
All from this publisherMore in Mobile, firmware and hardware
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login