{"schema_version":"1.0","service":"Publicasta","type":"article","id":1230,"slug":"esp32_c5_receive_only_rf_interference_detector","title":"What an ESP32-C5 Receive-Only RF Detector Can Tell You About 2.4 and 5 GHz Interference","excerpt":"A new open-source ESP32-C5 project turns a dual-band Wi-Fi MCU into a standalone RF watchdog. Here is what its sweep, baseline, alarms, and waterfall logs can reveal—and why they cannot identify intent or replace calibrated test equipment.","language":"en","default_language":"en","canonical_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=en","image":{"url":"https://publicasta.com/storage/projects/40/pages/1230/2026/11/4caffd80-662d-4837-9603-1b41b5bcc332.webp","alt":"A compact receive-only RF detector displays spectrum and waterfall activity on an electronics workbench."},"publisher":{"id":40,"slug":"ham_radio_diy_electronics","name":"Ham Radio & DIY Electronics","url":"https://publicasta.com/ham_radio_diy_electronics"},"author":{"name":"Anton Es"},"published_at":"2026-11-13T14:58:02+00:00","updated_at":"2026-11-13T14:58:02+00:00","content_markdown":"## Why this small project is timely for radio builders\n\n ![A compact receive-only RF detector displays spectrum and waterfall activity on an electronics workbench.](https://publicasta.com/storage/projects/40/pages/1230/2026/11/4caffd80-662d-4837-9603-1b41b5bcc332.webp)\n\n The ESP-WiFi-Jam-Detector project turns an ESP32-C5 touchscreen board into a portable way to watch the radio environment around it. A November 10, 2026 RTL-SDR.com report describes it as a standalone detector for activity in the 2.4 and 5 GHz bands. That framing matters: the device is presented as a receive-only monitor, not as a transmitter and not as a tool that can establish who created a signal or why it appeared.\n\n For radio builders, that distinction makes the project useful. Many interference problems begin as observations that are difficult to reproduce: a Wi-Fi link becomes unreliable at one desk, a Bluetooth connection drops in one room, or a receiver becomes noisy at a particular time of day. A monitor that can be carried to different locations can help turn those impressions into repeatable comparisons. It can show that the local RF environment changes, whether the change is concentrated in the 2.4 GHz range, whether activity is also visible in 5 GHz, and whether the pattern persists long enough to record.\n\n The underlying ESP-WiFi-Jam-Detector repository is an open-source hardware and software project built around the ESP32-C5’s wireless receiver. Espressif documents the ESP32-C5 as a dual-band Wi-Fi 6 microcontroller with 2.4 and 5 GHz radio support. This design uses that built-in capability as the sensing front end. The board is not trying to behave like a laboratory spectrum analyzer with a calibrated measurement chain. It uses a wireless MCU to scan defined portions of the spectrum, display changes on a touchscreen, and preserve observations for later inspection.\n\n That is a useful category of instrument for troubleshooting because the first question is often comparative rather than absolute. An operator may not need an exact field-strength measurement to discover that a signal appears only when a nearby device is running, or that one corner of a room has a markedly different noise pattern. The project’s value is in making changing RF conditions visible and portable. Its readings can support an investigation, while the interpretation still depends on the operator, the test setup, and the limitations of the receiver.\n\n The two bands covered by the project are especially relevant to everyday electronics. The 2.4 GHz range is used by Wi-Fi and Bluetooth and can also be affected by equipment such as microwave ovens. The 5 GHz range is used by Wi-Fi and can have a different local occupancy pattern. Seeing both ranges in one handheld instrument gives a builder a way to compare behavior instead of assuming that every wireless problem has the same source or follows the same path through a building.\n\n That comparison should not be confused with proof of deliberate jamming. The project can report that energy or activity differs from a learned reference condition. It cannot, from that observation alone, identify intent, attribute a signal to a person, or distinguish every benign source from every malicious one. A busy access point, Bluetooth activity, a microwave oven in operation, or another local electronic device may produce a change that looks important to the detector. The device also should not replace calibrated test equipment when the task requires defensible field-strength measurements, compliance work, or detailed signal characterization.\n\n The most productive way to approach the project is as a practical RF watchdog and a learning platform. Its screen and logs can help answer where and when the environment changes; its open implementation lets builders examine how the scan, baseline, alarms, and waterfall records are assembled. That makes it a timely experiment for diagnosing wireless reliability or exploring embedded radio measurement, provided the result is treated as evidence for the next troubleshooting step rather than as a final verdict.\n\n In this context, “detector” describes a change-detection workflow. The board observes the bands it is designed to scan, establishes a local reference, and draws attention to activity that departs from that reference. The following sections examine how that workflow is implemented, what its visual and recorded outputs can reveal, and how to use them without stretching a relative observation into a claim the hardware was not designed to support.\n\n ## How the ESP32-C5 detector works\n\n The ESP-WiFi-Jam-Detector uses the ESP32-C5 as a receive-only monitor for two unlicensed radio regions: 2400–2483.5 MHz and 5150–5895 MHz. It does not transmit a test signal or attempt to decode the traffic it observes. Instead, the device sweeps across the selected range and presents changes in received energy as a practical indication that the local RF environment is no longer quiet. That distinction matters: the instrument can show that activity has appeared, strengthened, persisted, or moved across a band, but the sweep alone does not establish who created it or why.\n\n The project’s operating description cites an 80 MS/s detail for the sweep process. In practical terms, the detector is built to make repeated, broad observations across the supported 2.4 and 5 GHz ranges rather than to serve as a narrow, laboratory-grade receiver for one precisely characterized signal. Its value is therefore comparative. A user can look at the same location before and after a device is switched on, compare the two supported bands, and watch how the pattern changes over time. The result is a visual and logged record of RF conditions that can guide further troubleshooting.\n\n Before it starts treating changes as noteworthy, the detector learns a local reference. The project describes a 60-second baseline period, during which the device observes the surrounding environment and establishes what normal conditions look like at that location. This is a useful design choice for a portable instrument because the background level in one room, workshop, or outdoor position may differ substantially from another. A baseline made beside an active access point should not automatically be treated as the same reference as one made in a quieter part of a building.\n\n The alarms are organized around different kinds of change rather than a single generic “interference” warning. The reported categories include raised wideband noise, persistent narrowband carriers, swept signals, and suspect pulsed energy. A broad rise can indicate that energy has increased across a larger portion of the monitored range. A narrowband alert points to a more concentrated feature that remains present. A swept pattern describes activity that moves through frequency, while a pulsed-energy category is intended for intermittent bursts that may be difficult to recognize from a single spectrum snapshot.\n\n These labels are best understood as pattern descriptions. They help the operator decide what to inspect next, but they do not turn the ESP32-C5 into a signal-identification system. A persistent carrier is still only a persistent carrier from the detector’s point of view; the project does not claim that the alarm can identify a transmitter, infer intent, or prove deliberate jamming. Likewise, “suspect” pulsed energy is a prompt to examine the evidence and repeat the measurement, not a final diagnosis of the source.\n\n The user interface combines a touchscreen spectrum display with a waterfall view. The spectrum presents a current slice of activity across the selected range, while the waterfall adds the time dimension so that persistent, intermittent, and moving patterns can be distinguished more readily. That distinction is central to the project’s usefulness. Two signals may look similar in a single frame but behave very differently when observed over successive sweeps: one may remain fixed, another may recur in bursts, and a third may trace a moving path across the display.\n\n The detector also supports event logging to an SD card and the saving of waterfall images. Those functions make the project more than a live “look at the screen” experiment. An operator can retain a record of an alarm, compare observations made at different times, and review whether a pattern was actually repeatable. The saved material can also provide a more disciplined basis for troubleshooting than memory or a one-time visual impression. Even so, the logs document what this particular receiver observed under its particular setup; they are not calibrated measurements of field strength.\n\n Taken together, the sweep ranges, learned baseline, alarm categories, touchscreen displays, and SD-card records form a compact workflow for observing changing RF conditions. The ESP32-C5 supplies the receive platform, while the project’s software turns repeated scans into relative comparisons and time-based visual evidence. That is enough to make the device a useful standalone watchdog for a builder who wants to know when the local 2.4 or 5 GHz environment has changed. It remains a monitoring experiment, however, and the meaning of each alert depends on the baseline, location, antenna arrangement, and surrounding sources that shaped the measurement.\n\n ## What an operator can actually use it for\n\n The most useful way to treat this detector is as a repeatable comparison tool. It can show that the RF environment has changed, indicate which of the two monitored bands is more affected, and preserve a visual record of when the change occurred. That is already enough to make troubleshooting less dependent on memory or guesswork. It is not enough to identify a person, prove intent, or establish the exact power or field strength of a signal.\n\n A sensible first measurement is a baseline taken in the place where the problem is actually observed. Let the detector complete its 60-second learning period with the equipment in its normal state, then record the conditions: location, antenna position, nearby powered devices, network activity, and the time of day. The point is not to create a universal definition of “quiet.” The point is to create a local reference against which later sweeps can be compared. A different room, antenna orientation, or collection of active devices can produce a different normal environment.\n\n Once that reference exists, repeat the measurement from fixed positions. If a Wi-Fi connection becomes unreliable at one desk, for example, the detector can be moved through the area in a consistent pattern while the operator watches the spectrum and waterfall display. A change that follows the detector toward a particular device or cable is more useful than a single alarm observed at an arbitrary location. Conversely, a disturbance that appears across the room or at several positions suggests a broader environmental change, although the detector alone cannot determine its source.\n\n The next step is controlled isolation. Switch off likely local sources one at a time, wait for the measurement to settle, and repeat the same observation. Candidate sources can include Wi-Fi access points, Bluetooth devices, microwave ovens, and other local electronics. The result to look for is not merely whether an alarm disappears, but whether the corresponding pattern in the waterfall changes at the same time. A persistent narrowband feature, a broader rise in noise, a swept pattern, and pulsed energy do not carry the same diagnostic implication, even when they occur in the same band.\n\n Comparing 2.4 and 5 GHz behavior adds another useful layer. A problem visible mainly in the 2.4 GHz sweep points the investigation toward devices and activity occupying that portion of the spectrum; a change concentrated in the 5 GHz sweep points elsewhere. If both bands change together, the event may be related to a local device or operating condition that affects the wider RF environment, but that remains a hypothesis to test. The project’s value is in narrowing the next measurement, not in turning a spectrum pattern into a definitive attribution.\n\n The saved waterfall images and SD-card event logs make this workflow easier to review. Instead of relying on a verbal report that “the interference was there,” an operator can retain a time-linked record of what the display showed and compare it with network failures, radio-receiver symptoms, or a device being switched on and off. This is particularly practical for intermittent problems, where the signal may be absent by the time a conventional inspection begins. Repeated records can also reveal whether an event is tied to a regular household or workshop activity or appears without an obvious local trigger.\n\n For amateur-radio builders, the same method is useful as an initial receive diagnostic: establish what the site normally looks like, identify a change near the affected equipment, and separate a persistent feature from a short-lived event. That role should remain distinct from calibrated compliance testing or formal spectrum measurements. Relative changes on this detector can guide an investigation, but they do not replace instruments intended to quantify RF conditions. The disciplined workflow is therefore simple: baseline first, measure from repeatable locations, change one variable at a time, compare both bands, and preserve the evidence before drawing conclusions.\n\n ## Limits, safety, and a sensible build decision\n\n The most important limitation is that this project is a relative monitor, not a calibrated measurement instrument. Its readings can show that the radio environment has changed and can help compare one observation with another, but a displayed dB value should not be treated as a certified field-strength measurement. Antenna characteristics, the board’s position, nearby objects, receiver behavior, and the local noise floor all affect what the detector sees. A higher trace therefore means “more energy reached this receiver under these conditions,” not a precisely measured power level that can be transferred to another site or instrument.\n\n That distinction also limits what an alarm can establish. The project’s categories—raised wideband noise, persistent narrowband carriers, swept signals, and suspect pulsed energy—describe patterns in the received spectrum. They do not identify the device that produced a pattern, establish why it was present, or prove that someone intended to disrupt communications. A sudden alarm may reflect a nearby source, a normal burst of Wi-Fi or Bluetooth activity, or a changing installation rather than deliberate interference. Even a persistent-looking trace is evidence for a follow-up investigation, not a conclusion about intent.\n\n False positives are consequently part of the operating reality. The same bands used by the detector contain ordinary consumer and industrial activity. A microwave oven can produce energy in the 2.4 GHz range, while busy Wi-Fi and Bluetooth devices can create changing peaks or bursts. Local electronics can also alter the noise environment enough to trigger attention. The useful response is not to treat every alarm as a confirmed jammer, but to repeat the observation and ask whether the pattern follows a particular device, time, location, or operating state.\n\n A disciplined build is best used as a comparative troubleshooting tool. Keep the detector in a fixed position, record the normal background, and repeat the sweep under similar conditions. If the alarm appears, switch likely local devices off one at a time and observe whether the trace changes. Compare the 2.4 and 5 GHz views rather than assuming that activity in one band explains activity in the other. The touchscreen view, waterfall history, SD-card event records, and saved waterfall images are valuable here because they preserve the shape and timing of an event instead of relying only on a brief visual impression. Those records can help a builder return to the same question later: what changed, and can the change be reproduced?\n\n The project is especially sensible for receive-side diagnostics around Wi-Fi and other equipment operating in or near the monitored bands. It can help indicate that a quiet location is no longer quiet, distinguish a broad rise from a concentrated carrier, and show whether an intermittent event deserves more investigation. For amateur-radio builders, however, that role should remain separate from calibrated compliance work or formal spectrum analysis. When the question requires absolute levels, measurement uncertainty, traceable calibration, or a defensible technical record, a purpose-built spectrum analyzer or other appropriate test equipment remains necessary. The ESP32-C5 instrument can point toward a problem; it cannot supply every measurement needed to characterize one.\n\n Safety and scope matter as much as measurement quality. The open-source GPL-3.0 design is presented as a receive-only experiment. Building or modifying it should not be treated as permission to transmit, interfere with other users, or attempt to validate a suspected source by creating additional RF activity. A receive-only workflow reduces the risk of adding another signal to an already crowded environment and keeps the device’s purpose clear: observing and documenting what is already present.\n\n The sensible build decision is therefore modest but useful. Choose this project when a standalone, dual-band watchdog and repeatable visual evidence would help explore a local RF problem, and when relative changes are enough to guide the next test. Do not choose it as a replacement for calibrated measurements, as proof of malicious intent, or as a device with automatic legal evidentiary status. Used within those boundaries, the ESP32-C5 detector is a practical open-source experiment: it can make an invisible change visible, narrow the list of likely causes, and tell the operator when a more capable instrument or a different investigation is warranted.","available_translations":[{"language":"ar","title":"ما الذي يكشفه كاشف تداخلات الترددات الراديوية ESP32-C5 للاستقبال فقط عن التداخل في نطاقي 2.4 و5 غيغاهرتز؟","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=ar","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=ar","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=ar","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=ar"},{"language":"de","title":"Was ein reiner ESP32-C5-RF-Detektor über Störungen im 2,4- und 5-GHz-Band verraten kann","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=de","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=de","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=de","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=de"},{"language":"en","title":"What an ESP32-C5 Receive-Only RF Detector Can Tell You About 2.4 and 5 GHz Interference","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=en","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=en","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=en","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=en"},{"language":"es","title":"Qué puede decirte un detector de RF de solo recepción basado en ESP32-C5 sobre las interferencias de 2,4 y 5 GHz","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=es","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=es","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=es","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=es"},{"language":"fr","title":"Ce qu’un détecteur RF en réception seule basé sur l’ESP32-C5 peut vous apprendre sur les interférences à 2,4 et 5 GHz","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=fr","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=fr","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=fr","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=fr"},{"language":"pl","title":"Co może powiedzieć o zakłóceniach w pasmach 2,4 i 5 GHz detektor RF ESP32-C5 działający wyłącznie odbiorczo","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=pl","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=pl","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=pl","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=pl"},{"language":"ru","title":"Что может рассказать детектор радиопомех на ESP32-C5 только с приёмом о помехах в диапазонах 2,4 и 5 ГГц","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=ru","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=ru","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=ru","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=ru"},{"language":"zh","title":"一款仅接收 ESP32-C5 射频检测器能告诉你哪些 2.4 GHz 和 5 GHz 干扰信息","html_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=zh","markdown_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=zh","json_url":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=zh","api_url":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=zh"}],"_links":{"self":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=en","api":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles/esp32_c5_receive_only_rf_interference_detector?lang=en","html":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=en","canonical":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector?lang=en","markdown":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.md?lang=en","json":"https://publicasta.com/ham_radio_diy_electronics/esp32_c5_receive_only_rf_interference_detector.json?lang=en","channel":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics","channel_articles":"https://publicasta.com/api/public/v1/channels/ham_radio_diy_electronics/articles","search":"https://publicasta.com/api/public/v1/search","documentation":"https://publicasta.com/api-docs#reading-publicasta","openapi":"https://publicasta.com/api-docs/openapi.json","llms":"https://publicasta.com/llms.txt"}}