Room sound-level logger

What you will work towards

Compare how noisy a workspace is at different times.

CAIBI’s proposed addition: Record relative sound trends without retaining conversations; calibration is a separate step.

Guide version 1.0. AI can help explain, adapt and debug; you still measure, assemble and test the physical result.

Start with the original

Tutorial foundation

• How To Electronics · view source material ↗
• CircuitDigest sound logger · view source material ↗

Tutorial located; parts, current dependencies and physical results have not been tested by CAIBI. Additional source inspected 10 October 2026: Use as a relative sound-trend project until properly calibrated; do not inherit the source safe/unsafe hearing labels. Cloud alerts and credentials are additional dependencies.

See the original source for its photos and demonstrations. We have not copied imagery without confirmed reuse rights. A source prototype is not a photo of this proposed CAIBI build.

From source to something you can finish

What the source provides: Two microphone logging examples with different possible implementations.

What still needs doing: Exact microphone matching, calibration and privacy need deliberate choices. Source hearing-risk labels are not validated.

Your first milestone: Read relative level locally and confirm raw audio is not saved.

Parts to confirm before buying

• One complete microphone/ESP32 combination from one source; do not mix analog and digital microphone wiring or code
• A matching display if wanted, and suitable USB power
• Local storage or serial output for timestamped summaries; a known time source if wall-clock time is required

Use the source wiring and bill of materials as the starting point. Confirm exact variants, availability, tools and complete cost before ordering.

The completion route

1. Choose one source implementation and record its exact microphone, board, dependencies and electrical interface.
2. Read the microphone locally and confirm readings respond to quiet and louder conditions. Detect clipping and missing input before adding a dashboard.
3. Reduce samples to relative summaries and discard raw audio. Use elapsed time until a time source is configured.
4. Compare repeated conditions at the same distance and orientation. Use neutral labels such as lower/higher relative level, not safe/unsafe.
5. Make a desk case that leaves the microphone opening unobstructed. Repeat the comparison after enclosing because placement can change readings.

Prompts to move it forward

Copy a prompt into your AI tool with the source material and your actual parts. Work through one small step at a time and check the output before using it. Choose an AI tool or practise the skills first.

Review the source material I supply for Room sound-level logger. Make a table of what is provided, missing, contradictory or dependent on a paid service. Identify exact hardware revisions, firmware files, library versions, CAD files and licences. Separate creator claims from your proposed additions. Do not fill gaps with guessed specifications. Finish with one small test that can resolve the biggest uncertainty before I buy parts.

Sources:
How To Electronics: https://how2electronics.com/diy-accurate-esp32-decibel-meter-spl-with-data-logger/
CircuitDigest sound logger: https://circuitdigest.com/microcontroller-projects/esp32-noise-pollution-monitoring

Help me turn the supplied microphone example into a local relative sound-trend logger. First identify my actual microphone interface, board revision and working code. Propose an aggregation method, clipping indication and elapsed-time log with explicit units. Do not label uncalibrated values dB SPL, dBA or safe/unsafe. Do not store speech or raw audio. If I request calibrated measurements, explain the reference instrument and calibration evidence still required. Add restart and missing-input tests before optional networking.

Sources:
How To Electronics: https://how2electronics.com/diy-accurate-esp32-decibel-meter-spl-with-data-logger/
CircuitDigest sound logger: https://circuitdigest.com/microcontroller-projects/esp32-noise-pollution-monitoring

Design a stable desk enclosure using my measured microphone and controller dimensions. Preserve the acoustic opening and mark the intended orientation. Keep power accessible and avoid treating the enclosure as acoustically transparent without a before/after test. Start with a mounting sample.

Sources:
How To Electronics: https://how2electronics.com/diy-accurate-esp32-decibel-meter-spl-with-data-logger/
CircuitDigest sound logger: https://circuitdigest.com/microcontroller-projects/esp32-noise-pollution-monitoring

Create a test log for Room sound-level logger. Intended outcome: Compare how noisy a workspace is at different times. Separate expected behaviour from observed results. Include power restart, disconnected inputs, communication failure and the actual physical use. Ask me to provide results, firmware versions, changes, photos and unresolved problems. Never mark a test passed without my evidence.

Sources:
How To Electronics: https://how2electronics.com/diy-accurate-esp32-decibel-meter-spl-with-data-logger/
CircuitDigest sound logger: https://circuitdigest.com/microcontroller-projects/esp32-noise-pollution-monitoring

What to test and record

• Repeated comparable conditions produce inspectable relative trends; record distance and orientation.
• Missing microphone and clipped input are distinguishable from quiet conditions.
• No raw audio files or speech recordings are retained.
• Restart and storage-full behaviour are recorded.
• Compare readings before and after enclosure assembly; do not infer calibrated accuracy.

Keep photos, exact parts and software versions with the test log. Failed or incomplete attempts are useful evidence too.

A possible next version

Add a local history display or export of aggregated readings. Occupational or hearing-risk decisions require appropriate calibrated equipment and expertise.