-
Notifications
You must be signed in to change notification settings - Fork 7.7k
feat(zigbee): Add stop/start methods + add missing license headers #11791
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.
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
Conversation
👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project! 📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more. 🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project. Click to see more instructions ...
Review and merge process you can expect ...
|
Memory usage test (comparing PR against master branch)The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.
Click to expand the detailed deltas report [usage change in BYTES]
|
Test Results 76 files 76 suites 13m 10s ⏱️ Results for commit 2a04b1a. |
Description of Change
This pull request introduces new lifecycle management capabilities to the Zigbee stack, allowing it to be started and stopped programmatically. It also adds standardized Apache 2.0 license headers to all Zigbee source files for improved legal compliance and clarity. The documentation is updated to reflect the new API methods.
start()
andstop()
methods to theZigbeeCore
class, enabling the Zigbee stack to be paused and resumed as needed. These methods update the internal state and suspend or resume the main Zigbee task accordingly (libraries/Zigbee/src/ZigbeeCore.cpp
,libraries/Zigbee/src/ZigbeeCore.h
). [1] [2]start()
andstop()
methods, including example usage and scenarios for stopping the stack (e.g., saving power or freeing the radio for other tasks) (docs/en/zigbee/zigbee_core.rst
).Test Scenarios
Tested using edited Zigbee example and HomeAssistant.
After stopping and starting again, device continue to work normally.
Related links
Closes #10871