Skip to content

doc: Added info about Thread child timeout's impact #19121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 29, 2024
Merged

doc: Added info about Thread child timeout's impact #19121

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions doc/nrf/protocols/matter/getting_started/low_power_configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ The following Matter samples and applications use the low power configuration by

* :ref:`Matter door lock sample <matter_lock_sample>`
* :ref:`Matter light switch sample <matter_light_switch_sample>`
* :ref:`Matter smoke CO alarm <matter_smoke_co_alarm_sample>`
* :ref:`Matter window covering sample <matter_window_covering_sample>`
* :ref:`Matter weather station application <matter_weather_station_app>`

Expand Down Expand Up @@ -153,6 +154,18 @@ Switching the Matter :ref:`ug_matter_device_low_power_icd_modes` and frequently
To avoid this issue, set the :kconfig:option:`CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL` and :kconfig:option:`CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL` Kconfig options to the same value (for example, ``500``).
The typical use case that the SSED is best suited for is battery-powered devices that require short response time, such as door locks or window blinds.

Child timeouts configuration
----------------------------

The device working in a Thread child role uses additional mechanisms for periodically ensuring that the communication with the parent is still possible.
These mechanisms lead to waking up the device and exchanging the messages with the parent, if the related timeout expires.
In case of using the SED poll period value greater than any of these timeouts, the device wakes up more often than what is defined by the poll period.
To ensure that the SED device wakes up exactly at every poll period, set the following Kconfig options to the value greater than the poll period value (for Matter ICD :kconfig:option:`CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL`):

* :kconfig:option:`CONFIG_OPENTHREAD_MLE_CHILD_TIMEOUT`
* :kconfig:option:`CONFIG_OPENTHREAD_CHILD_SUPERVISION_CHECK_TIMEOUT`
* :kconfig:option:`CONFIG_OPENTHREAD_CHILD_SUPERVISION_INTERVAL`

Matter over Wi-Fi
=================

Expand Down
2 changes: 1 addition & 1 deletion doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,7 @@ nRF IEEE 802.15.4 radio driver
Thread
------

|no_changes_yet_note|
* Added Kconfig options for configuring the MLE child update timeout, child supervision interval, and child supervision check timeout.

Zigbee
------
Expand Down
2 changes: 1 addition & 1 deletion west.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ manifest:
# https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/modules.html
- name: zephyr
repo-path: sdk-zephyr
revision: b2571927ed316e0ae110bffdc5f35311c80511aa
revision: 6e98d27ad62d03cda299a4e8222829c4485532f6
import:
# In addition to the zephyr repository itself, NCS also
# imports the contents of zephyr/west.yml at the above
Expand Down
Loading