Wireless problems we solve
RF Interference and Non-Wi-Fi Interference Investigation
Wi-Fi tools see Wi-Fi. Distinguishing contention from non-Wi-Fi energy requires a spectrum analyzer measuring raw RF, not frames.
Engineer’s questionHow do I know whether interference is Wi-Fi or non-Wi-Fi, and how do I find it?
1 — Direct answer
The short answer
There are two different problems with the same name. Wi-Fi interference is contention: other 802.11 radios sharing your channel, which your infrastructure can see and report. Non-Wi-Fi interference is raw RF energy from something that does not speak 802.11 — it raises the noise floor, corrupts frames and is largely invisible to a Wi-Fi adapter.
The practical test is the relationship between reported utilization and the noise floor. If channel utilization is high but attributable to identifiable BSSs, you have contention and a channel-plan or density problem. If the noise floor is elevated, retries are high, and the controller cannot account for the airtime, you likely have non-Wi-Fi energy and need a spectrum analyzer to characterise it.
Be careful with certainty. Spectrum analysis reliably shows duty cycle, occupancy, bandwidth and signature, and many sources classify confidently. Pinpointing a specific physical device usually requires directional hunting on site, and some sources are only ever classified by signature rather than identified by name.
Likely causes, roughly in order of frequency
- Co-channel and adjacent-channel Wi-Fi
- Your own over-dense deployment, or a neighbouring tenant, sharing the same channels. Common, and it is contention rather than interference in the RF sense.
- Bluetooth and BLE
- Frequency-hopping energy across 2.4 GHz from headsets, beacons, asset tags, medical devices and peripherals.
- Microwave ovens and industrial heating
- Broad, high duty-cycle 2.4 GHz energy correlated with kitchen or process activity.
- Video senders, wireless cameras and proprietary telemetry
- Fixed-frequency, often continuous occupancy that can render channels unusable.
- DFS radar events
- Radar detection forces channel changes in 5 GHz DFS channels, producing sudden disruption near airports, ports, weather radar and some medical installations.
- Motors, lighting, chargers and faulty equipment
- Industrial electrical noise raises the noise floor across wide ranges without producing anything a Wi-Fi tool can decode.
2 — Symptoms
Symptoms and what they usually mean
| Symptom | What it usually indicates |
|---|---|
| High retries with good RSSI and low client count | Strong indicator of non-Wi-Fi energy or hidden-node behaviour rather than capacity. |
| Noise floor worse than about −85 dBm indoors | Something is raising the floor; Wi-Fi alone rarely does this. |
| Problems recur at the same time each day | Correlated with a process, appliance or shift pattern — very diagnosable. |
| Only one band or a few channels affected | Points to a specific fixed-frequency source rather than a general design fault. |
| Unexplained channel changes in 5 GHz | Likely DFS radar detection. |
| Utilization high but client traffic low | Airtime is being consumed by something outside your visibility. |
3 — Do this first
Safe checks you can run yourself
These are non-disruptive checks a competent network engineer can complete with the controller or cloud dashboard already in place. Do them before changing configuration — they frequently identify the cause, and they always make an external investigation faster and cheaper.
- 1
Read the controller's air-quality and interference metrics
Most enterprise platforms report an interference or air-quality index per radio; treat it as a pointer, not a diagnosis.
- 2
Record the noise floor per radio and per band
Compare affected and unaffected areas at the same time of day.
- 3
Correlate timing with operations
Shift changes, kitchen use, production runs and equipment schedules frequently explain intermittent RF problems.
- 4
Check DFS event history
Radar detections and subsequent channel changes are logged by most controllers.
- 5
Scan for rogue and neighbour BSSs
Establishes how much of the utilization is simply other Wi-Fi.
- 6
Note the physical environment
Kitchens, imaging suites, battery chargers, conveyor motors, wireless cameras, and legacy point-to-point links are worth listing before anyone arrives on site.
4 — Watch out
Common mistakes and misleading indicators
“The controller says interference is low, so there is none”
Infrastructure radios serve clients and sample the spectrum only briefly; low-duty-cycle or intermittent sources are easily missed.
“A Wi-Fi scanning app found the interference”
Wi-Fi adapters decode 802.11 frames. They cannot see non-Wi-Fi energy at all, whatever the app label says.
“Changing channels solved it”
It may have moved you away from a fixed-frequency source — useful, but the source is still there and may move or expand.
“The spectrum analyzer named the device”
Classifiers give a probable category. Confirming a specific physical device normally needs directional hunting on site.
5 — Escalation point
When normal troubleshooting is no longer enough
- The noise floor is elevated and you have no spectrum analyzer or nobody trained to interpret the captures.
- Problems are intermittent and you cannot be on site when they occur.
- The environment contains medical, industrial or process equipment where coordination, not channel changes, is the only safe remediation.
- Repeated DFS events are disrupting production and you need a channel strategy rather than a reaction.
- You need documented evidence to take to another team, a vendor or a landlord.
6 — Professional investigation
What a professional wireless investigation should measure
- Spectrum capture across bands
- 2.4, 5 and 6 GHz raw RF capture in the affected areas, recording occupancy, duty cycle, bandwidth and signature over a representative period.
- Interference classification
- Separating Wi-Fi contention from non-Wi-Fi sources and characterising each by category and impact, within what the measurements support.
- Impact correlation
- Relating measured RF energy to retries, SNR, data rates and the specific symptoms and locations reported.
- Directional source hunting
- Where the engagement allows, locating physical sources on site using directional measurement.
- DFS analysis
- Reviewing radar-triggered channel changes and defining a channel plan that keeps critical services stable.
- Remediation options
- RF-side changes, physical mitigation, equipment coordination or channel strategy, with the trade-offs stated.
7 — Relevant service
Which NetRobin service applies
Spectrum Analysis & RF Interference
Spectrum analysis measures raw RF independently of what the wireless network reports, which is the only way to separate non-Wi-Fi interference from ordinary Wi-Fi contention and to characterise the source.
Often combined with
8 — Deliverables
What you should expect to receive
- Spectrum findings per band and affected area, with captured evidence
- Classification of identified interference categories and their measured impact
- Correlation between RF measurements and reported symptoms
- Remediation options: RF-side, physical, coordination or channel strategy
- Clear statement of what the measurements do and do not establish
Direct answers
Frequently asked questions
- How do I know whether interference is Wi-Fi or non-Wi-Fi?
- If the airtime being consumed can be attributed to identifiable BSSs, it is Wi-Fi contention. If the noise floor is elevated, retries are high and utilization cannot be accounted for by 802.11 traffic, it is likely non-Wi-Fi energy — and only a spectrum analyzer measuring raw RF can confirm and characterise it.
- How do I find RF interference?
- Capture raw spectrum in the affected areas across the bands in use, record occupancy and duty cycle over a period that includes the problem window, classify the signatures, correlate them with retries and SNR, and where possible locate the source with directional measurement on site.
- Can a Wi-Fi analyzer app detect non-Wi-Fi interference?
- No. Wi-Fi adapters decode 802.11 frames, so they can show neighbouring networks and channel usage but are blind to microwave, motor, video-sender and other non-802.11 energy. That requires spectrum analysis hardware.
10 — Next step
Request an Interference Investigation
Tell us the affected areas, bands and timing pattern — intermittent problems need to be measured while they are happening.