`Mle::AnnounceHandler::HandleAnnounce` previously executed the `kAnnounceAttachAfterDelay` action on an attached node even when the announced channel and PAN ID already equaled the current MAC parameters. The `!channelAndPanIdMatch` guard was only consulted in the `IsDetached()` branch. For an attached node this scheduled `StartAnnounceAttach`, which calls `Stop()` then `Start()` with the same channel/PAN ID -- accomplishing nothing while disrupting attached children. This causes an endless role flap in a topology where two FTDs share channel, PAN ID, and network credentials but hold different Active Dataset Timestamps, and where their RF link is too weak to merge partitions (Advertisements rejected with LinkMarginLow at `mle_router.cpp`). Each side restarts on every Announce received from the higher-timestamp peer; the reactive `kSendAnnouceBack` path further amplifies this because the lower-timestamp side's own outgoing Announces draw Announce responses from the peer. Apply the channel/PAN ID match guard unconditionally in `kAnnounceAttachAfterDelay`. Mirror it on the FTD `kSendAnnouceBack` path (matching the existing `isFromOrphan` behavior) so peers sharing MAC parameters are not prompted to migrate to the channel/PAN ID they already use. Add `addon_test_announce_no_flap_on_unmergeable_partitions.py` which builds the topology above and asserts that both nodes retain their original partition IDs across a 20-minute simulated window. Without this change the lower-timestamp node is repeatedly demoted from leader during that window.
What is OpenThread?
OpenThread released by Google is...
...an open-source implementation of the Thread networking protocol. Google Nest has released OpenThread to make the technology used in Nest products more broadly available to developers to accelerate the development of products for the connected home.
...OS and platform agnostic, with a narrow platform abstraction layer and a small memory footprint, making it highly portable. It supports both system-on-chip (SoC) and network co-processor (NCP) designs.
...a Thread Certified Component, implementing all features defined in the Thread 1.4.0 specification, including all Thread networking layers (IPv6, 6LoWPAN, IEEE 802.15.4 with MAC security, Mesh Link Establishment, Mesh Routing) and device roles, as well as Border Router support.
More information about Thread can be found at threadgroup.org. Thread is a registered trademark of the Thread Group, Inc.
Who supports OpenThread?
Getting started
All end-user documentation and guides are located at openthread.io. If you're looking to do things like...
- Learn more about OpenThread features and enhancements
- Use OpenThread in your products
- Learn how to build and configure a Thread network
- Port OpenThread to a new platform
- Build an application on top of OpenThread
- Certify a product using OpenThread
...then openthread.io is the place for you.
Note: For users in China, end-user documentation is available at openthread.google.cn.
If you're interested in contributing to OpenThread, read on.
Contributing
We would love for you to contribute to OpenThread and help make it even better than it is today! See our Contributing Guidelines for more information.
Contributors are required to abide by our Code of Conduct and Coding Conventions and Style Guide.
License
OpenThread is released under the BSD 3-Clause license. See the LICENSE file for more information.
Please only use the OpenThread name and marks when accurately referencing this software distribution. Do not use the marks in a way that suggests you are endorsed by or otherwise affiliated with Nest, Google, or The Thread Group.
Need help?
OpenThread support is available on GitHub:
- Bugs and feature requests — submit to the Issue Tracker
- Community Discussion - ask questions, share ideas, and engage with other community members























