Wi-Fi signal strength is usually reported as RSSI, a measurement in dBm (a negative number, where a value closer to zero means a stronger signal and a larger negative number means a weaker one). There is no single universal cutoff for “too weak,” because different chipset makers and device vendors scale and report RSSI differently from each other, which is exactly why one app’s “two bars” and another device’s raw dBm reading aren’t directly comparable. What’s genuinely useful is understanding the shape of the scale, checking a number if your device exposes one, and treating a signal in the roughly -70 dBm range and beyond as the zone where problems become more likely, according to how major platform vendors define their own connection thresholds.
Why there’s no single “too weak” number
RSSI (Received Signal Strength Indication) is fundamentally a relative measurement, not a standardized absolute one. The Wi-Fi standard doesn’t mandate exactly how a chipset must calculate or scale it, which is why, according to networking documentation from Cisco’s own community engineering resources, different manufacturers use different scales entirely: some report on a 0 to 100 range, others on a 0 to 60 range, and consumer devices typically convert this into the more familiar negative-dBm figure, but not always using the same formula to get there. Two devices sitting in the exact same spot, from two different manufacturers, can genuinely report different numbers for what is physically the same signal.
This is also why a device’s on-screen “signal bars” indicator and a raw dBm reading from a network analyzer tool can seem to disagree. The bars are usually a simplified, vendor-specific translation of the underlying number, tuned by that manufacturer’s own judgment about what counts as good, fair, or poor for their hardware.
What the scale actually means
Despite the lack of a single universal cutoff, the shape of the scale is consistent: RSSI values in dBm are negative, and the value closer to zero is always the stronger signal. A signal in roughly the -30 to -50 dBm range is generally considered strong, close to the source. Moving further away or through more obstructions pushes the number down (more negative), and by the time a signal reaches somewhere around -70 dBm and beyond, many devices and platforms start treating that connection as marginal.
That’s not folklore. Apple’s own deployment documentation for Wi-Fi roaming describes its Mac hardware as maintaining a connection to an access point until the signal crosses a defined threshold before actively looking to roam to a stronger one, and its iPhone and iPad hardware uses a similarly defined, though not identical, threshold of its own. The specific numbers differ between Apple’s own device categories, which is itself the point: even one manufacturer treats “acceptable” differently across its own product line, so a threshold from one ecosystem shouldn’t be assumed to apply universally to every smart home device.
How to actually check a device’s signal
If the manufacturer’s app shows a signal indicator, that’s the most directly relevant number for that specific device, since the manufacturer has presumably tuned it against their own hardware’s real-world behavior, even though it isn’t comparable across brands.
If you want a raw, comparable dBm reading, a Wi-Fi analyzer app on a phone or laptop, checked while standing at or near the device’s actual location, gives you a number for that spot rather than for the device itself. This tells you about the location’s signal quality, which is a reasonable stand-in for what the device is likely experiencing, without requiring the device to expose its own reading.
If your router’s admin interface lists connected devices with a signal strength column, that’s often the closest thing to the device’s own actual reading, reported from the router’s side of the connection rather than estimated from a nearby phone.
What counts as “workable” rather than “perfect”
A signal doesn’t need to be excellent to be reliable for most smart home purposes. Low-bandwidth devices like sensors, plugs, and switches send small, infrequent bursts of data and tend to tolerate a weaker signal better than something streaming continuous video, like a camera, which needs a more consistently strong connection to avoid dropped frames or buffering. Treat a marginal reading as a flag worth investigating for a camera and as something to keep an eye on, but not necessarily fix immediately, for a sensor or plug that’s otherwise behaving normally.
If a device sits in the zone most vendor guidance treats as marginal or worse and is also genuinely misbehaving (dropping intermittently, slow to respond, failing to update), that combination is a real signal problem worth addressing through placement or by identifying what’s physically blocking the signal in that spot, rather than continuing to guess.
What signal strength doesn’t explain
A weak signal reading explains intermittent drops, slow responses, and devices that fall off specifically in one part of the house. It doesn’t explain a device that’s fully unreachable despite a strong signal reading, which points toward AP isolation, blocked mDNS discovery, or a different cause entirely. Checking the signal number first is still worth doing, since it’s one of the fastest ways to rule a whole category of problems in or out.
FAQ
What’s a “good enough” signal for a smart plug or sensor?
There’s no single verified number that applies across every device, but a reading in the stronger half of the scale, well short of the marginal zone most vendors flag, is a reasonable target for low-bandwidth devices like these, which tend to tolerate weaker signals better than cameras do.
Why does my phone show full bars in the same spot where my smart camera struggles?
Different devices have different antenna quality and radio sensitivity, so two devices in the same physical spot can genuinely experience different effective signal strength, even though they’re receiving the same broadcast from the same router.
Is 5 GHz signal strength read the same way as 2.4 GHz?
The RSSI measurement concept applies the same way to both bands, but 5 GHz signals generally weaken faster over distance and through obstacles than 2.4 GHz does, so a “good” reading at a given distance on one band doesn’t predict the same reading on the other.
Can a strong signal reading still mean a bad connection?
Yes. Signal strength measures how well the radio signal itself is received, not the quality of the connection overall. Interference, network congestion, and the discovery or addressing problems covered elsewhere in this series can all affect a device with a strong signal reading.
Do I need a special tool to check this, or does my phone already do it?
A phone’s own Wi-Fi settings sometimes show signal quality in a simplified form, but a dedicated Wi-Fi analyzer app gives a more precise, comparable dBm reading if you want to check a specific spot in more detail.
Sources referenced in this article
- Cisco Community, Measuring Signal Strength: RSSI and dBm.
https://community.cisco.com/t5/network-platform-api/measuring-signal-strength-rssi-and-dbm/td-p/5410395(accessed 2026-07-24). Source describing RSSI as a relative, vendor-defined scale rather than a single standardized measurement. - Apple, Wi-Fi roaming support in Apple devices (Apple Support / Deployment documentation).
https://support.apple.com/en-tj/guide/deployment/dep98f116c0f/web(accessed 2026-07-24). Source of the Mac and iPhone/iPad roaming-threshold example illustrating that even one vendor defines “acceptable” differently across its own devices.
Review interval: 12 months (vendor-specific thresholds and app behavior can change).