EMC for IoT Devices: A Practical CE Marking Guide for Engineers and SMEs

Electromagnetic compatibility is one of the most misunderstood hurdles in the CE marking process for IoT products — and one of the most expensive to get wrong. If your connected device emits interference or can’t withstand it, you’ll face failed tests, costly redesigns, and delayed market entry. This guide cuts through the complexity and gives you a clear, actionable path through EMC compliance for IoT devices.

---

Why EMC Compliance Is More Challenging for IoT Devices

Traditional EMC compliance was relatively straightforward: one device, one radio frequency, predictable emissions. IoT devices break that model. A typical smart home sensor might combine Wi-Fi, Bluetooth, Zigbee, and a cellular modem in a form factor smaller than a matchbox — all while connected to cloud services, drawing power from a USB supply, and running firmware that toggles GPIOs unpredictably.

This multi-radio, multi-interface nature creates several compounding problems:

• Broadband noise sources from switching regulators and fast digital clocks sit right alongside intentional radio transmitters
• Multiple antenna structures interact in ways that are difficult to simulate in pre-compliance testing
• Software-defined behaviour means emissions can vary significantly between firmware versions
• Novel form factors make shielding difficult and put PCB traces close to enclosure edges

The result: IoT devices consistently show higher EMC failure rates than conventional electronics at accredited test houses. Understanding the regulatory framework before you design — not after — is the single highest-return investment you can make.

---

The Regulatory Framework: Which Directives Apply to Your IoT Device?

The Radio Equipment Directive (RED) — 2014/53/EU

The Radio Equipment Directive (RED) 2014/53/EU is the primary legislation for almost every IoT device that includes a radio transmitter or receiver. This covers Wi-Fi, Bluetooth, Zigbee, Z-Wave, LoRa, NB-IoT, LTE-M, and any other intentional radiator.

RED replaces the old R&TTE Directive (1999/5/EC) and has been fully in force since June 2017. Critically, RED Article 3 sets three essential requirements:

• Article 3.1(a) — protection of health and safety (essentially the Low Voltage Directive requirements, applied to radio equipment)
• Article 3.1(b) — electromagnetic compatibility, aligned with the EMC Directive
• Article 3.2 — efficient use of the radio spectrum (radio performance, spurious emissions, frequency accuracy)

For most IoT devices, RED covers everything in a single directive. You do not need to separately apply the EMC Directive if RED applies.

The EMC Directive — 2014/30/EU

The EMC Directive 2014/30/EU applies to electrical and electronic apparatus that does not contain an intentional radio function. If your IoT product is, for example, a wired industrial sensor, a Ethernet-connected gateway with no radio, or a power line communication device, the EMC Directive is your primary instrument.

The two essential requirements under EMC Directive Article 6 are:

• The apparatus must not generate electromagnetic disturbance beyond a level that prevents other equipment from operating as intended
• The apparatus must have an adequate level of immunity to allow normal operation

The Low Voltage Directive — 2014/35/EU

If your IoT device operates between 50–1000 V AC or 75–1500 V DC, the Low Voltage Directive (LVD) 2014/35/EU also applies. Many IoT devices fall below these thresholds and are out of scope, but mains-connected IoT gateways, smart plugs, and industrial controllers typically need LVD as well.

Overlap and the “ONE directive” question

A mains-powered Wi-Fi thermostat will need RED (for the radio), and its safety requirements are addressed through RED Article 3.1(a). If the product also falls under sector-specific legislation — for example, medical device regulation (MDR 2017/745/EU) for a connected health monitor — those additional requirements layer on top.

---

Harmonised Standards: The Technical Backbone of Compliance

Harmonised standards provide a presumption of conformity with the essential requirements. Meeting these standards means you are presumed to comply with the directive — which is why choosing the right standards is critical.

Key standards for IoT devices under RED

EN 301 489-1 (V2.2.3) is the common EMC standard for radio equipment — the foundational document that sets general emission and immunity requirements for all radio apparatus. It is almost always used in conjunction with device-specific parts:

• EN 301 489-3 — short range devices (Zigbee, Z-Wave, 868 MHz ISM band sensors)
• EN 301 489-17 — wideband data transmission systems (Wi-Fi 2.4/5 GHz, Bluetooth)
• EN 301 489-52 — LTE/5G IoT categories including NB-IoT and LTE-M

For radio performance (the Article 3.2 requirement), the corresponding radio standards apply alongside the EMC standard:

• EN 300 328 — Wi-Fi and Bluetooth in 2.4 GHz band
• EN 301 893 — Wi-Fi 5 GHz band
• EN 303 413 — GNSS receivers
• EN 301 908 series — LTE and NB-IoT / LTE-M

Key standards for non-radio IoT under the EMC Directive

• EN 55032 — emissions for multimedia equipment (the successor to EN 55022)
• EN 55035 — immunity for multimedia equipment (the successor to EN 55024)
• EN 61000-3-2 — harmonic current emissions (mains-connected equipment)
• EN 61000-3-3 — voltage fluctuations and flicker

For industrial IoT products, the EN 61000-6 series (generic standards) is commonly used — specifically EN 61000-6-4 for industrial emissions and EN 61000-6-2 for industrial immunity.

Always verify you are referencing the current published version of each standard and check the Official Journal of the EU for up-to-date harmonised standard lists, as versions are revised regularly.

---

Step-by-Step: Getting Your IoT Device Through EMC Compliance

Step 1: Define your product scope and applicable directives

Before any testing begins, document exactly what your device is. Write down:

• All radio interfaces and their frequency bands, modulation types, and output power levels
• Power supply method (battery, USB, mains)
• Intended environment (residential/commercial class A or B, industrial)
• Whether it forms part of a larger system or is standalone

This scoping exercise determines your directives, standards list, and ultimately your conformity assessment path.

Step 2: Choose your conformity assessment route

Under RED, most IoT devices use internal production control (Annex II of RED) combined with a technical file. This means you are self-certifying using harmonised standards. However, if you are using non-harmonised standards, or if no harmonised standard covers your device’s radio type, you must use a Notified Body (Annex III or IV of RED).

Critically: a Notified Body is not required for most standard Wi-Fi/Bluetooth IoT devices if you test against harmonised standards. This is a common misconception that leads SMEs to spend money they don’t need to.

Step 3: Pre-compliance testing — do this early

Pre-compliance testing at an in-house or third-party pre-compliance lab saves significant cost. A full accredited test campaign at an ISO 17025 lab can cost €5,000–€20,000 depending on complexity. Finding problems early, before that campaign, is always cheaper.

Focus pre-compliance effort on:

• Radiated emissions scans — identify unexpected harmonics from clocks, switching regulators, or radio transmitters
• Conducted emissions — measure noise on power leads
• Basic ESD checks — a surprisingly common failure mode for IoT devices with exposed USB or sensor ports

Step 4: Manage your test configuration carefully

One of the most frequent EMC failures for IoT devices is poor test configuration management. The device you test must match the device you sell. Before attending a test house, define:

• The final PCB revision and all populated components
• The firmware version — lock it before testing
• All cables and peripherals that will ship with the product
• Power supply configuration (battery state, mains adapter brand and model)

Any significant change after testing may invalidate your test report and require retesting.

Step 5: Compile your technical file

Your technical file is the document package that demonstrates compliance. Under RED, it must include:

• A general description of the device and its intended use
• Conceptual design and manufacturing drawings
• A list of harmonised standards applied
• Test reports from an accredited lab (or documented in-house test results if using internal production control)
• A copy of the EU Declaration of Conformity
• Radio frequency information (frequencies, power levels, modulation)

This file does not go to any authority unless requested — but market surveillance authorities can demand it, and it must be available for ten years after the last unit is placed on the market.

Step 6: Draft and sign the EU Declaration of Conformity

The EU Declaration of Conformity (EU DoC) is a legal document signed by the manufacturer or their EU authorised representative. It must reference the specific directives and standards applied. A single EU DoC can cover multiple applicable directives (RED, LVD, etc.).

After this, affix the CE mark to the product. For radio devices under RED, the CE mark must also be accompanied by the radio equipment alert symbol if the device is not approved for use in all EU member states — though most standard ISM band IoT devices are EU-wide.

---

Common EMC Mistakes for IoT Devices

Testing the wrong product variant. IoT products often ship in multiple SKUs — different enclosure colours, accessories, or regional firmware variants. If you tested SKU A but the one that ships to Germany is SKU B with a different PCB revision, your test report may not cover it.

Ignoring the power supply. The power adapter or charger that ships with an IoT device is part of the apparatus for EMC purposes. Testing with a different supply than the one in the box is a serious test configuration error.

Overlooking firmware-dependent emissions. A device in idle mode often behaves very differently from one under load. Test with the device running its most electromagnetically active operational state — active data transfer, all radios transmitting simultaneously.

Assuming module certification covers the system. Using a certified Wi-Fi or cellular module does not automatically certify your end product. Module testing covers the module alone. Placing it on your PCB, in your enclosure, with your antenna arrangement creates a new electromagnetic environment that requires its own testing.

Missing the UKCA requirement. Post-Brexit, the UK is a separate market. Products sold in Great Britain need UKCA marking under the UK Radio Equipment Regulations 2017. Northern Ireland retains CE marking under the Windsor Framework. Plan for both if you sell across the UK and EU.

---

Frequently Asked Questions

Q: My IoT device uses only a pre-certified Bluetooth module. Do I still need EMC testing?

Yes. Module certification (FCC ID, CE, Bluetooth SIG listing) covers the module as a standalone component. Your finished product — with its PCB, enclosure, antenna routing, and firmware — is a new radio apparatus and must be tested and assessed as a complete system under RED. You may benefit from reduced testing scope if the module’s test data is well-documented, but you cannot skip the conformity assessment process.

Q: What is the difference between Class A and Class B for EMC limits?

Class B limits are stricter and apply to devices intended for use in residential environments (homes, small offices). Class A limits are less strict and apply to industrial environments where professional users accept more electromagnetic noise. Most consumer IoT devices — smart home, wearables, connected appliances — must meet Class B limits under EN 55032 or the EN 301 489 series.

Q: Can I CE mark an IoT device without using an accredited test house?

For radio equipment under RED, the standard conformity assessment route (Annex II) allows you to use your own test results if you apply harmonised standards. However, in practice, self-testing is only credible if you have properly calibrated equipment and a competent internal team. Most SMEs are better served by using an accredited ISO 17025 test house, as this produces a defensible test report and significantly reduces market surveillance risk.

Q: Do I need a Notified Body for my IoT device under RED?

Only if you are not using harmonised standards, or if the Commission has specified that your device category requires Notified Body involvement (under RED Article 17). For the vast majority of IoT devices using standard Wi-Fi, Bluetooth, Zigbee, or LoRa radios covered by existing harmonised standards, Notified Body involvement is not mandatory.

Q: How long are EMC test reports valid?

Test reports themselves do not expire, but they are only valid for the exact product configuration tested. Any hardware, firmware, or mechanical change that could affect electromagnetic performance requires reassessment — which may mean partial or full retesting. A good rule of thumb: document the exact tested configuration thoroughly, so you can accurately judge whether a future change is material.

---

Conclusion: Build EMC Into Your IoT Development Process

EMC compliance for IoT devices is not a checkbox you tick at the end of development. By the time you reach a test house with a finalised design, your options for fixing failures are expensive and slow. The engineers who consistently get IoT products to market on time are the ones who treat EMC as a design discipline — choosing components for their electromagnetic properties, involving test partners at prototype stage, and building compliance documentation in parallel with hardware development.

The regulatory framework — principally RED 2014/53/EU, EMC Directive 2014/30/EU, and the harmonised standards under EN 301 489 and EN 55032 — is more coherent than it appears once you understand the structure. Most standard IoT devices have a clear, well-trodden path to the CE mark.

The key is knowing exactly where your product sits in that framework, which standards apply, and what your technical file needs to contain.

---

Ready to take the guesswork out of CE marking your IoT device?

The CE Marking Compliance Kit (€97) gives you everything you need to manage your own compliance process confidently — including pre-compliance checklists, technical file templates, Declaration of Conformity drafts, and directive applicability guides built specifically for hardware engineers and product managers. It’s the structured resource that saves you hours of regulatory research and helps you walk into a test house — or a notified body meeting — fully prepared.

→ Need a ready-to-use EU Declaration of Conformity? Download the EU Declaration of Conformity Pack 2026 — 5 directive-specific templates (EMC, LVD, Machinery, RoHS, RED), field-by-field completion guide, and harmonised standards reference. €67, instant download.