|
| 1 | +--- |
| 2 | +title: "RED-DA Compliant Matter devices with ESP-ZeroCode" |
| 3 | +date: "2025-11-28" |
| 4 | +# If default Espressif author is needed, uncomment this |
| 5 | +# showAuthor: true |
| 6 | +# Add a summary |
| 7 | +summary: "In this blog we will introduce how combining the Espressif RED-DA compliance framework along with the ESP ZeroCode platform can help accelerate your product development" |
| 8 | +# Create your author entry (for details, see https://developer.espressif.com/pages/contribution-guide/writing-content/#add-youself-as-an-author) |
| 9 | +# - Create your page at `content/authors/<author-name>/_index.md` |
| 10 | +# - Add your personal data at `data/authors/<author-name>.json` |
| 11 | +# - Add author name(s) below |
| 12 | +authors: |
| 13 | + - "anant-raj-gupta" # same as in the file paths above |
| 14 | +featureAsset: "img/featured/featured-announcement.webp" |
| 15 | +# Add tags |
| 16 | +tags: ["REDDA", "Matter", "ZeroCode"] |
| 17 | +--- |
| 18 | + |
| 19 | +With the EU **Radio Equipment Directive Delegated Act (RED‑DA)** now in effect, all radio equipment placed on the EU market must meet the mandatory cybersecurity and update requirements defined in **EN 18031**. |
| 20 | + |
| 21 | +Espressif has integrated RED‑DA support into the **ESP‑ZeroCode** platform, enabling developers and product teams to generate **Matter firmware and a RED‑DA‑oriented documentation package in one step**. This integration reduces manual work, simplifies technical documentation, and accelerates time‑to‑market for EU‑bound Matter devices. |
| 22 | + |
| 23 | +{{< alert icon="circle-info" cardColor="#b3e0f2" iconColor="#04a5e5">}} |
| 24 | + As with all RED‑DA workflows, the **end‑product manufacturer** remains responsible for the final Declaration of Conformity and for ensuring that the complete device (hardware + firmware + cloud/backend) meets the applicable EN 18031 requirements. |
| 25 | +{{< /alert >}} |
| 26 | + |
| 27 | + |
| 28 | +## What’s New: Integrated RED‑DA Support in ESP‑ZeroCode |
| 29 | + |
| 30 | +ESP‑ZeroCode now delivers a **RED‑DA documentation starter package** alongside the generated device firmware: |
| 31 | + |
| 32 | +- **Pre‑filled compliance templates** |
| 33 | + Espressif provides documentation aligned with EN 18031 and our RED‑DA guidance, including: |
| 34 | + - Platform‑level security features and defaults |
| 35 | + - Network stack and secure update mechanisms |
| 36 | + - Standard technical specifications for the ESP‑ZeroCode Matter platform |
| 37 | + |
| 38 | +- **Documentation structured for final use** |
| 39 | + The package is organized to match typical RED‑DA technical documentation expectations, so it can be: |
| 40 | + - Used directly for **self‑assessment and Declaration of Conformity**, or |
| 41 | + - Used as input for **Approved Testing Laboratories (ATLs) or Notified Bodies**, when needed |
| 42 | + |
| 43 | +With this integration, developers no longer have to assemble the technical file from scratch. **Platform‑level conformance** is captured by Espressif’s pre‑filled content, while the manufacturer completes the remaining device‑specific sections as part of their normal product documentation flow. |
| 44 | + |
| 45 | +## How the Integration Works |
| 46 | + |
| 47 | +### Pre‑Filled Compliance Templates |
| 48 | + |
| 49 | +The templates provided via ESP‑ZeroCode are derived from Espressif’s RED‑DA documentation framework described in **RED‑DA Compliance Part 2** and prepared in collaboration with **Brightsight**: |
| 50 | + |
| 51 | +- Based on **EN 18031** mappings for Article 3(3)(d)/(e)/(f), where applicable |
| 52 | +- Include: |
| 53 | + - Platform security configuration and defaults |
| 54 | + - Secure communication and cryptography settings |
| 55 | + - OTA / secure update capabilities |
| 56 | + |
| 57 | +These templates serve as a **starting point** for the final technical documentation package expected by Market Surveillance Authorities and Notified Bodies. |
| 58 | + |
| 59 | +### Product‑Specific Inputs by the Manufacturer |
| 60 | + |
| 61 | +The end‑product manufacturer augments the templates with device‑specific information to complete the technical file. Typical additions include: |
| 62 | + |
| 63 | +- Detailed device description and intended use |
| 64 | +- Target user group and installation environment |
| 65 | +- Mechanical design and PCB schematics |
| 66 | +- Power, radio, and enclosure details |
| 67 | +- Application‑level behavior and any customizations that may affect security or privacy |
| 68 | + |
| 69 | +This ensures that the documentation accurately reflects the **actual device, operational environment, and manufacturing setup**, while still leveraging Espressif’s platform‑level content. |
| 70 | + |
| 71 | +### Documentation Delivered with Firmware |
| 72 | + |
| 73 | +ESP‑ZeroCode exports both the **production‑ready Matter firmware** and the **RED‑DA documentation starter package** in one step: |
| 74 | + |
| 75 | +- The package includes Espressif’s pre‑filled sections for the ESP‑ZeroCode platform |
| 76 | +- Placeholders and headings make it clear where manufacturers should add their own product details |
| 77 | +- Once completed, the package can be used for: |
| 78 | + - RED‑DA **self‑declaration** (Declaration of Conformity issued by the manufacturer), or |
| 79 | + - Submissions to an **ATL or Notified Body**, when a formal third‑party assessment is preferred or required |
| 80 | + |
| 81 | +## Workflow: From Device Design to RED‑DA‑Oriented Package |
| 82 | + |
| 83 | +1. Select or customize a device template in ESP‑ZeroCode. |
| 84 | +2. Configure Matter clusters and device behavior** using the standard ESP‑ZeroCode workflow. |
| 85 | +3. Generate firmware and the documentation starter package in a single step. |
| 86 | +4. Complete product‑specific sections in the provided templates as part of your internal documentation process. |
| 87 | +5. Use the completed package for RED‑DA self‑assessment or as input to an ATL/Notified Body, and proceed to Matter ecosystem certification if applicable. |
| 88 | + |
| 89 | +This integrated workflow reduces manual documentation work and provides a clear, unified path toward EU compliance. |
| 90 | + |
| 91 | +## Benefits for Developers and Product Teams |
| 92 | + |
| 93 | +Espressif’s integrated solution provides concrete advantages for **any developer building Matter devices for the EU market**: |
| 94 | + |
| 95 | +- **Single‑step delivery** of firmware + RED‑DA documentation starter package |
| 96 | +- **Reduced manual effort** in preparing technical files |
| 97 | +- **Clear responsibility split** |
| 98 | + - Espressif: platform‑level documentation and security configuration |
| 99 | + - Manufacturer: product‑specific details and final conformity decision |
| 100 | +- **Faster EU market entry** with pre‑validated platform documentation |
| 101 | +- **Confidence in security and interoperability**: templates incorporate Espressif’s EN 18031‑aligned safeguards at the platform level |
| 102 | +- **Simplified scaling across multiple device variants** without repeating core platform compliance work |
| 103 | +- **Accessible for teams of any size**, from solo developers to larger organizations |
| 104 | + |
| 105 | +This approach allows teams to focus on **innovation and differentiation**, while Espressif provides a strong regulatory foundation at the platform level. |
| 106 | + |
| 107 | +## Example Use Case |
| 108 | + |
| 109 | +A team building a Matter‑enabled smart light for the EU market can: |
| 110 | + |
| 111 | +1. Use **ESP‑ZeroCode** to configure the smart light profile and select an appropriate Matter device template. |
| 112 | +2. Generate the **firmware + RED‑DA documentation starter package**. |
| 113 | +3. Add product‑specific information such as **manufacturer details, PCB schematics, operational environment, and model identifiers** into the templates. |
| 114 | +4. Use this package for **RED‑DA self‑declaration** or as input to an ATL / Notified Body, depending on their chosen compliance pathway. |
| 115 | + |
| 116 | +The result: faster launch, reduced engineering effort, and RED‑DA‑oriented Matter devices with minimal manual documentation work. |
| 117 | + |
| 118 | +## Conclusion |
| 119 | + |
| 120 | +By integrating RED‑DA support into **ESP‑ZeroCode**, Espressif provides a streamlined, end‑to‑end path for Matter device development targeting the EU market. Developers and product teams can now generate **firmware and RED‑DA‑aligned documentation together**, with clear guidance on how to complete the remaining product‑specific sections. |
| 121 | + |
| 122 | +This unified approach reduces engineering effort, minimizes compliance risk, and accelerates time‑to‑market for secure, interoperable, and EU‑ready Matter devices. |
| 123 | + |
| 124 | +--- |
| 125 | + |
| 126 | +## Get Started |
| 127 | + |
| 128 | +- Explore **ESP‑ZeroCode**: |
| 129 | + <https://zerocode.espressif.com> |
| 130 | + |
| 131 | +- Read Espressif’s **RED‑DA guides**: |
| 132 | + - Part 1 – *RED‑DA (EN 18031) Certification Compliance: What You Need to Know* |
| 133 | + <https://developer.espressif.com/blog/2025/04/esp32-red-da-en18031-compliance-guide/> |
| 134 | + - Part 2 – *RED‑DA Compliance (Part 2): Espressif’s Platform Support, Templates, and Pathways for Conformity* |
| 135 | + <https://developer.espressif.com/blog/2025/07/esp32-red-da-en18031-compliance-guide-part2/> |
| 136 | + |
| 137 | +- Learn about the **RED‑DA Assessment Tool** (background and preparation): |
| 138 | + <https://red-da-assessment-tool.security.espressif.com> |
| 139 | + |
| 140 | +*Espressif Systems – enabling secure, compliant, and interoperable IoT innovation, from design to deployment.* |
0 commit comments