fix(Zigbee): Add missing direction to report commands [3.0.X]

P-R-O-C-H-Y commented 3 days ago

Description of Change

This PR fixes Zigbee reporting command which is missing direction attribute.

Tests scenarios

Related links

github-actions[bot] commented 3 days ago

	Warnings
:warning:	Some issues found for the commit messages in this PR: - the commit message `"fix(Zigbee): Add missing direction to report commands"`: - scope/component should be lowercase without whitespace, allowed special characters are `_` `/` `.` `,` `` `-` `.` Please fix these commit messages** - here are some basic tips: - follow [Conventional Commits style](https://www.conventionalcommits.org/en/v1.0.0/) - correct format of commit message should be: `(): `, for example `fix(esp32): Fixed startup timeout issue` - allowed types are: `change,ci,docs,feat,fix,refactor,remove,revert,test` - sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter - avoid Jira references in commit messages (unavailable/irrelevant for our customers) `TIP:` Install pre-commit hooks and run this check when committing (uses the [Conventional Precommit Linter](https://github.com/espressif/conventional-precommit-linter)).
:warning:	The target branch for this Pull Request must be the default branch of the project (`master`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

Warnings

:warning:

**Some issues found for the commit messages in this PR:** - the commit message `"fix(Zigbee): Add missing direction to report commands"`: - *scope/component* should be lowercase without whitespace, allowed special characters are `_` `/` `.` `,` `*` `-` `.` *** **Please fix these commit messages** - here are some basic tips: - follow [Conventional Commits style](https://www.conventionalcommits.org/en/v1.0.0/) - correct format of commit message should be: `():

`, for example `fix(esp32): Fixed startup timeout issue` - allowed types are: `change,ci,docs,feat,fix,refactor,remove,revert,test` - sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter - avoid Jira references in commit messages (unavailable/irrelevant for our customers) `TIP:` Install pre-commit hooks and run this check when committing (uses the [Conventional Precommit Linter](https://github.com/espressif/conventional-precommit-linter)).

:warning:

The **target branch** for this Pull Request **must be the default branch** of the project (`master`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project!

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by :no_entry_sign: dangerJS against 3d3d7655917a60b0a0366a514d56bbe228887ace

github-actions[bot] commented 3 days ago

Test Results

56 files 56 suites 4m 16s ⏱️ 21 tests 21 ✅ 0 💤 0 ❌ 134 runs 134 ✅ 0 💤 0 ❌

Results for commit 3d3d7655.

:recycle: This comment has been updated with latest results.

github-actions[bot] commented 3 days ago

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.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32C6	:green_heart: -10K	0	:green_heart: -2.00	0.00	:green_heart: -308	:warning: +12	:green_heart: -0.93	:warning: +0.04
ESP32H2	:green_heart: -11K	0	:green_heart: -2.13	0.00	:green_heart: -336	0	:green_heart: -1.04	0.00

Click to expand the detailed deltas report [usage change in BYTES]

Target	ESP32C6		ESP32H2
Example	FLASH	RAM	FLASH	RAM
Zigbee/examples/Zigbee_Color_Dimmable_Light	:green_heart: -10K	:green_heart: -12	:green_heart: -11K	:green_heart: -40
Zigbee/examples/Zigbee_Color_Dimmer_Switch	:green_heart: -2K	:warning: +12	:green_heart: -3K	:green_heart: -32
Zigbee/examples/Zigbee_On_Off_Light	:green_heart: -10K	:warning: +4	:green_heart: -11K	:green_heart: -40
Zigbee/examples/Zigbee_On_Off_Switch	:green_heart: -2012	:green_heart: -4	:green_heart: -3K	:green_heart: -32
Zigbee/examples/Zigbee_Scan_Networks	:green_heart: -392	:green_heart: -4	:green_heart: -1430	:green_heart: -32
Zigbee/examples/Zigbee_Temp_Hum_Sensor_Sleepy	:green_heart: -10K	:warning: +4	:green_heart: -11K	:green_heart: -40
Zigbee/examples/Zigbee_Temperature_Sensor	:green_heart: -402	:warning: +12	:green_heart: -1462	:green_heart: -32
Zigbee/examples/Zigbee_Thermostat	:green_heart: -292	:green_heart: -308	:green_heart: -1348	:green_heart: -336

espressif / arduino-esp32