Most makers who want to build interactive devices face the same wall: a list of 50 different Arduino modules with no guidance on where to start. HC-SR04, HC-SR501, DHT22, FSR, sound sensor, IR break beam, LDR, TTP223 — they all appear in tutorials, but none of the tutorials tell you: what interaction does this module actually make possible, and which one should you reach for first?
This article maps five common modules by the interaction intention they serve. If you know what you want the experience to feel like, you will know which module to pick.
The Real Problem: Modules Are Categorized by Technical Specs, Not Human Intentions
Arduino modules are typically organized by type: sensors, actuators, controllers, displays. That classification makes sense for engineers. It does not help a maker who wants to build an interactive installation that feels alive.
When I was starting out, I bought a kit with 37 sensors. I spent three weeks blinking LEDs before I realized I had no idea what to do with a PIR sensor, a force resistor, or an ultrasonic module — beyond the obvious.
The breakthrough came when I stopped asking "what can this module do?" and started asking "what experience do I want to create, and which module makes that experience possible?"
Here is the map I wish I had.
Scenario 1: You Want the Space to Know When Someone Is There
Module: HC-SR501 PIR Motion Sensor
Passive Infrared sensors are the most underused module in beginner kits. Most people use them for LED control — but they are the foundation of any installation that responds to human presence.
A PIR sensor detects changes in infrared radiation. When a warm body moves into its field of view, the sensor triggers. You can mount one at chest height in any doorway or corridor, connect it to your Arduino, and use the signal to trigger lights, sound, projections, or motors.
The key design insight: a PIR sensor does not detect distance. It detects change. It needs a moving heat source crossing its field. A person standing completely still in front of a PIR sensor will disappear after about 30 seconds. Plan your installation accordingly.
Amazon affiliate link: HC-SR501 PIR Sensor modules
Affiliate disclosure: As an Amazon Associate, I earn from qualifying purchases.
Scenario 2: You Want the Installation to Respond to How Close Someone Gets
Module: HC-SR04 Ultrasonic Distance Sensor
If you want an interaction that changes based on proximity — not just presence — the HC-SR04 ultrasonic sensor is the answer. It measures distance by emitting a 40kHz ultrasonic pulse and measuring the time until the echo returns.
Mount it at floor level or in a panel, aim it at where a visitor will approach, and map different distance thresholds to different behaviors. At 100cm, start a slow color fade on your LED strip. At 50cm, speed up the pulse. At 20cm, trigger the full animation. This is how you make an installation feel like it is reading the visitor, not just reacting to them.
The HC-SR04 works best for single-user interactions. If multiple people are in the beam at once, the echo becomes noisy. For group interactions, consider using multiple sensors or switching to a PIR-based presence detection system.
Amazon affiliate link: HC-SR04 Ultrasonic Sensor modules
Scenario 3: You Want the Floor, Seat, or Surface Itself to Respond to Touch and Pressure
Module: FSR (Force Sensing Resistor) 400 Pressure Sensor
Pressure sensors turn passive surfaces into interactive triggers. Embed a thin FSR mat under a rug, beneath a floor tile, or inside a cushion, and the surface itself becomes your interface.
The design pattern that works best: use the FSR as a threshold trigger, not a continuous input. When pressure exceeds a certain value — someone's full weight on the mat — trigger an event. This avoids the noisy continuous analog readings that FSRs produce when you try to use them for gradual pressure sensing.
The most common mistake with FSRs is wiring them without a pulldown resistor. The analog signal will float without a 10k resistor between the signal pin and ground. Without it, your readings will be garbage.
Amazon affiliate link: FSR 400 Pressure Sensor modules
Scenario 4: You Want the Installation to React to Environmental Changes Over Time
Module: DHT22 Temperature and Humidity Sensor
For installations that change with the environment rather than with human action, the DHT22 is the most accessible entry point. It reads both temperature and relative humidity with enough accuracy for artistic purposes, and the library support means you can get stable readings within an hour of opening the package.
The interaction design principle here is ambient awareness. The DHT22 does not respond to a human action at a specific moment — it makes the installation continuously sensitive to its environment. A paper windmill that spins faster as the room warms up. An LED strip that shifts from warm to cool tones as temperature changes through the day. A fan that turns on when humidity rises above a threshold.
This is the module that makes an installation feel alive in a different sense — not reactive to visitors, but continuously responding to the conditions around it.
Amazon affiliate link: DHT22 Temperature Humidity Sensor modules
Scenario 5: You Want Sound to Trigger a Response
Module: Sound Sensor with LM393 Comparator
A basic sound sensor module — the kind with an LM393 comparator chip and a potentiometer for sensitivity adjustment — can detect sound events without needing to process audio waveforms. Set the threshold with the potentiometer, read the digital output pin, and use sound events as triggers.
The key to making this work is setting the threshold carefully. Too sensitive, and background noise triggers your installation constantly. Too insensitive, and you need to shout. The potentiometer is not just an calibration tool — it is part of your interaction design. The right threshold turns "the room is noisy" into "someone just made a deliberate sound."
Clap-activated lights are the canonical example, but sound triggering becomes far more interesting when the response is not immediate. A short delay between sound event and reaction — 300 to 500 milliseconds — makes the installation feel like it is thinking before responding.
Amazon affiliate link: Sound Sensor Module with LM393
How to Combine Modules: The Interaction Stack
Real installations rarely use just one module. The most compelling experiences layer multiple sensors to create richer readings of visitor behavior.
A basic interaction stack might look like this:
- HC-SR501 PIR — detects when a visitor enters the space
- HC-SR04 Ultrasonic — tracks how close the visitor gets to the installation
- WS2812B LED Strip — the output, controlled by the Arduino based on sensor inputs
The logic layer — the Arduino code that translates sensor inputs into output behaviors — is where the design happens. This is the part that tutorials rarely cover well, because it is not about individual modules. It is about the relationship between modules.
If you want a blueprint for building this kind of multi-sensor interactive system, I put together a detailed Interactive Project Blueprint on Fiverr that covers the module selection logic, wiring approach, and code structure for a proximity-reactive installation.
Get the Interactive Project Blueprint on Fiverr
The Module Selection Framework
When you are planning your next interactive project, work through this sequence:
- What is the primary interaction? Presence, proximity, contact, environmental change, or sound?
- What is the output? LED effect, motor movement, sound playback, projection mapping?
- What are the physical constraints? Range needed, mounting position, weather exposure?
- What is the single module that best serves the primary interaction?
Most beginners buy a sensor kit and then try to find an application for each module. More effective: define the interaction you want, then find the single module that makes that interaction possible. Start there. Add complexity only when you have a reason.
The five modules above cover the most common interaction patterns in interactive installations. They are not the only options — but they are the ones I reach for most often when I am building something new.
Start With One Module, One Interaction
If you have been stuck in tutorial paralysis — reading about modules without building anything — pick one scenario from this article and build it this weekend. Not a complex system. One module. One output. One clear interaction.
A PIR sensor triggering an LED when someone walks by. An ultrasonic sensor making a servo rotate as someone approaches. A sound sensor turning on a light when you clap.
Once you have that single interaction working reliably, you will understand the module well enough to know where it fits in something more ambitious.
The gap between "I have a list of sensors" and "I know how to use these to create experiences" is not knowledge. It is practice.
Top comments (0)