IoT

  • IoT
  • matter
  • Home APP
  • roller shade
  • manifest
  • CSV

How is the Matter DAC pre-provisioning handled, and where is it programmed in the module?

For the pre-provisioned DAC solution, the DAC certificate is programmed into the secure cert partition, and on some chips the DAC private key is programmed into eFuse.

This is handled by Espressif before the chip or module leaves the factory. If you use the pre-provisioned DAC service, customers are generally required to enable both secure boot and flash encryption.

A Matter device is configured as a roller shade, but the iOS Home app always shows it as blinds. How can this be changed?

This may be fixed behavior in the iOS Home app. The iOS Home app does not necessarily provide a distinct UI for every Matter device display type.

Use chip-tool to read the current device configuration and confirm whether the configured type is correct. If the device reports the correct type but iOS Home still displays it as blinds, it usually means the current iOS Home app does not support that specific UI representation yet.

For a Matter no-code module solution, is firmware pre-flashed at the factory, and how should the module, MAC address, and QR code list be matched?

Espressif's Matter pre-provisioning service provides a manifest file, usually in CSV format. It contains each module's MAC address, serial number if available, and corresponding QR code information. During production, this file is used to map module information to certificate information.

The related information can be read by scanning the module QR code. A typical production flow is:

  1. Scan the module QR code on the production line.
  2. Match the scan result against the corresponding row in the CSV file.
  3. Locate and export the production certificate QR code.
  4. Use that QR code for printing, silkscreening, and assembly.

This keeps the module, MAC address, certificate information, and final product QR code aligned.