Matter Fundamentals – [Lesson 2] – Matter samples and applications – v3.3.0-v3.20

The nRF Connect SDK provides several samples and applications showcasing the Matter protocol. You can build them for a variety of board targets and configure them for different usage scenarios.

The following list presents supported samples and applications grouped by their purpose and use cases:

  • Regular Matter device types
    • Entry control
      • Matter door lock
      • Matter window covering
      • Matter closure
    • Light control
      • Matter light bulb
      • Matter light switch
    • Sensors
      • Matter contact sensor
      • Matter temperature sensor
      • Matter smoke CO alarm
      • Matter weather station (temperature, humidity and pressure sensors)
    • HVAC
      • Matter thermostat
    • Utility
      • Matter bridge
  • Bases for creating custom device type and clusters
    • Matter template
    • Matter manufacturer specific

Note

For more detailed information regarding supported protocols and low power configuration see the table describing all available Matter samples and applications.

Matter sample structure

All Matter samples and applications have a common files structure that is similar to the other samples available in nRF Connect SDK. However, there are also specific files and directories applicable only to Matter, so they are worth explaining. The following list presents the most important elements of Matter application’s structure with an explanation of their purposes:

  • boards/ – directory storing .conf and .overlay files specific to a board
  • src – directory with Matter application source code
    • default_zap/ – directory with generated source files for Matter Data Model
    • app_task.cpp – source file containing Matter application implementation
    • app_task.h – header file for the Matter application
    • chip_project_config.h – header file for changing Matter stack configuration
    • main.cpp – source file for running the Matter application
  • sysbuild/ – directory storing the configuration of non-application images
  • CMakeLists.txt – Cmake file for including header and source files to be compiled
  • Kconfig – File with application specific options and default configuration
  • Kconfig.sysbuild – File that sets default configuration for cross-image options
  • pm_static_X.yml – Files that define memory partitions, where X is specific board name
  • prj.conf – File that can be used to change application debug configuration
  • prj_release.conf – File that can be used to change application release configuration
  • README.rst – Documentation file that describes the application usage

Note

Distinguishing between prj.conf and prj_release.conf for debug and release configurations is not a general nRF Connect SDK rule, but a best-practice method for all Matter samples.

Switch language?

Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.

Your current progress is saved, and you can switch back anytime.

Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.