9 Wireless Modules You Should NEVER Use in a Product
The wireless module you pick can kill your product before it ever ships.
I’m talking about FCC certifications that fall apart at the last minute, cellular networks that shut down mid-production, parts that go discontinued right when you’re scaling, and clone modules that behave differently from the datasheet you designed around.
I’ve helped a lot of product creators sort through wireless module choices, and I keep seeing the same mistakes over and over again.
So in this video, I’m walking you through 9 wireless modules you should never design into a real product.
Module #9 is the HC-05 and the HC-06
These are Bluetooth Classic modules built around something called Serial Port Profile, or SPP, and they’re the wrong choice for almost any consumer product that talks to a smartphone.
iOS doesn’t natively expose SPP to third-party apps, and the HC-05 and HC-06 can’t support Apple’s MFi program at all, so there just isn’t a path to iOS compatibility with these modules.
The market is also flooded with counterfeits, so two modules with the same marking can behave completely differently in the field.
And most units sold have no legitimate FCC modular approval, which means you have no usable grant to inherit when it’s time to certify your product.
Instead, use a real BLE module built on Nordic or Silicon Labs chips, with a verifiable FCC ID and datasheet-backed specs.
I personally tend to lean toward Nordic, and my favorite vendor for Bluetooth products is Fanstel, though Raytac and Laird are solid options too.
Module #8 is the HM-10
The HM-10 is a BLE 4.0 era part with serious clone problems lurking behind it.
The chip inside may or may not be the TI CC2540 or CC2541 the original design used, because the market is full of clones running completely different silicon.
The AT command set everyone designs around is proprietary to the original manufacturer’s firmware, and clones don’t always replicate it correctly.
So picture this, you design around a specific set of AT commands, you scale to production, and your second batch behaves differently because the manufacturer sourced from a different clone supplier.
That problem shows up after you’ve already shipped.
For BLE modules, Fanstel is my go-to recommendation, but Raytac and Laird are solid choices too, all built on modern Nordic nRF52 silicon with real certification.
Module #7 covers the whole category of legacy BLE modules
This includes parts like the Microchip RN4020, the Silicon Labs Bluegiga BLE112 and BLE113, and older TI CC2540-based modules.
I used to love a lot of these modules, and I designed with them frequently, but that was quite a while ago, and they’re all outdated now with better alternatives available.
They’re BLE 4.0 or 4.1 era parts missing features that newer products often need, and many are marked not recommended for new designs or flat out discontinued with SDK support winding down.
You design in something like the RN4020 because a tutorial used it or it was in an old BOM, and two years later you can’t source the part and your firmware is tied to that module’s stack.
Before you design in any BLE module, check what silicon is actually inside it, look at the vendor’s lifecycle status, confirm which BLE spec version it supports, and see how actively the SDK is being maintained.
For new designs, stick to current BLE 5.x modules built on modern silicon from a serious vendor.
Module #6 is the ESP-01
The ESP-01 is a Wi-Fi module built on Espressif’s ESP8266 chip, and it’s everywhere in tutorials and maker projects.
It’s great for learning Wi-Fi basics, but it’s a terrible choice for a real product.
GPIO is minimal and the antenna is a poorly-tuned trace, but the real problem is that the entire form factor lacks an RF shield.
An RF shield is a strict requirement for FCC modular approval, so no standard ESP-01, whether genuine or clone, can hold a valid modular FCC grant.
Even though Espressif’s 15-year longevity commitment for the 8266 runs through 2029, there are better, more capable, more secure options available today.
For a new Wi-Fi product, skip the 01 and use a properly shielded module in the WROOM or MINI form factor built on modern ESP32 silicon like the S3, the C6, or the C3, which actually carry FCC modular approval and are well-documented for production.
Module #5 is the generic nRF24L01
I mean the cheap clones flooding the market, not legitimate Nordic silicon used properly.
These modules use a proprietary 2.4 GHz protocol, not BLE, not Zigbee, not Thread, which means you’re building an island that can’t talk to anything else.
The clones have no inheritable approvals or trustworthy compliance documentation, the range claims on the listings are basically fiction, and there’s no standardized ecosystem for interoperability.
If you’re reaching for an nRF24L01, it usually means you haven’t decided on a real protocol yet.
Protocol selection is actually a bigger decision than module selection, so get the protocol right first and then pick the module to match.
For most point-to-point or small-mesh applications, plain BLE or BLE mesh is probably your best answer.
Module #4 is really a whole category of modules where the antenna and certification story falls apart in practice
This includes raw Semtech SX1276 or SX1262 breakouts and modules with an RF trace pin where the modular grant only stays valid if you replicate the vendor’s exact microstrip layout and stackup, which beginners almost always deviate from.
It also includes modules with a U.FL or SMA connector where the FCC grant lists specific antenna types and maximum gains that integrators either ignore or don’t bother to check before picking a completely different antenna.
The moment you deviate from a module’s FCC grant antenna conditions, the modular approval no longer covers your integration.
That can mean full intentional radiator testing for the US alone running roughly eight to fifteen thousand dollars per radio, with multi-region compliance pushing past thirty thousand.
Antenna matching on RF trace pin modules usually requires a vector network analyzer and RF expertise that most product creators just don’t have, plus impedance-controlled traces and proper antenna placement.
So the rule is, if a module doesn’t ship with an integrated antenna or an FCC grant listing antenna types and gains you intend to use, where you must match the type and stay at or below the listed gain, you’re buying yourself an RF project.
Use modules with integrated PCB or chip antennas and valid modular FCC approval instead.
Module #3 is generic uncertified LoRa modules
LoRa is useful for long range, low bandwidth applications, but the frequency bands vary by region, and cheap LoRa modules often have no legitimate regional certification.
Even when the hardware works fine across frequency bands, the firmware, channel plan, and duty cycle requirements are region-specific compliance gates that no amount of hardware matching can fix.
You design a LoRa product, ship into a region where the module doesn’t meet local compliance requirements, and your product gets pulled.
Use pre-certified LoRa modules with the right regional variant from vendors like Murata, RAK Wireless, or u-blox instead.
Module #2 is the SIM800 and the SIM900
These are 2G cellular modules.
2G networks are shut down or shutting down in most major markets, so any product built on these is basically obsolete the day it ships.
Ship a SIM800 to the US and you have no dependable carrier path.
Ship to Australia and it flat out can’t connect.
Ship to Europe and coverage is fragmented and shrinking.
So skip 2G entirely on new cellular products.
For low-data IoT, use LTE-M or NB-IoT modules from vendors like Quectel, u-blox, or Telit, but check regional coverage carefully because deployment is still uneven.
LTE Cat-1 bis is often a better default for global coverage, and all three of those vendors offer modules that support it.
Whatever you pick, make sure it’s certified for your target regions and carriers.
Module #1 is the uncertified module that claims to be pre-certified
This is the most important one in the whole video because the lesson applies to every wireless decision you’ll ever make.
These are listings claiming “FCC certified” or “CE certified” right in the title, but the paperwork doesn’t hold up.
The FCC IDs may be fake, belong to a completely different module, or have grant conditions that don’t actually cover your integration.
So you design around a module that looks pre-certified, build a thousand units, and at final compliance your lab catches it.
Now you’re either paying for full intentional radiator testing at eight to fifteen thousand dollars per radio, or scrapping inventory.
Here’s how to protect yourself, and this applies to any module you ever consider.
Look up the FCC ID yourself on the FCC equipment authorization database, and check the grant notes and conditions.
Pay attention to whether it’s a full modular approval or a limited one, because limited approvals come with host-specific conditions that may not cover your design.
The rule is simple, buy from manufacturers who publish real certification documentation, and if you can’t find a real FCC ID in the FCC equipment authorization database, it doesn’t count as certified.
