feat(zigbee): Add battery voltage attribute support

[P-R-O-C-H-Y]

Description of Change

This pull request includes updates to the Zigbee Power Config Cluster adding a battery voltage functionality. The most important changes involve adding support for setting and reporting battery voltage in addition to battery percentage.

Enhancements to battery management:

• libraries/Zigbee/examples/Zigbee_Temp_Hum_Sensor_Sleepy/Zigbee_Temp_Hum_Sensor_Sleepy.ino: Updated the setup function to include setting battery voltage along with battery percentage.
• libraries/Zigbee/src/ZigbeeEP.cpp: Modified the setPowerSource method to accept battery voltage as an additional parameter and added a new method setBatteryVoltage to update the battery voltage attribute. [1] [2] [3]
• libraries/Zigbee/src/ZigbeeEP.h: Updated the ZigbeeEP class definition to include the new battery voltage parameter in the setPowerSource method and added a new method setBatteryVoltage.

Note: Battery Voltage attribute is not reportable, that's why there is no report method for that.

Tests scenarios

Tested using Sleepy example and HomeAssistant ZHA integration (only battery % was shown, but I was able to read the voltage value).

Related links

Closes #11177

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "Update libraries/Zigbee/examples/Zigbee_Temp_Hum_Sensor_Sleepy/Zigbee_Temp_Hum_Sensor_Sleepy.ino": summary looks empty type/action looks empty the commit message "Update libraries/Zigbee/src/ZigbeeEP.cpp": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, 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 10 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).

👋 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 ...

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 🚫 dangerJS against 6eed3db

[github-actions]

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
ESP32S3	0	⚠️ +28	0.00	0.00	0	0	0.00	0.00
ESP32S2	0	⚠️ +28	0.00	0.00	0	0	0.00	0.00
ESP32C3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C6	0	⚠️ +24	0.00	0.00	0	0	0.00	0.00
ESP32H2	0	⚠️ +22	0.00	0.00	0	0	0.00	0.00
ESP32	0	⚠️ +28	0.00	0.00	0	0	0.00	0.00

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

Target	ESP32S3		ESP32S2		ESP32C3		ESP32C6		ESP32H2		ESP32
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
libraries/Zigbee/examples/Zigbee_Color_Dimmer_Switch	⚠️ +28	0	⚠️ +28	0	0	0	0	0	0	0	⚠️ +28	0
libraries/Zigbee/examples/Zigbee_Gateway	⚠️ +28	0	⚠️ +28	0	0	0	-	-	-	-	⚠️ +28	0
libraries/Zigbee/examples/Zigbee_On_Off_Switch	⚠️ +28	0	⚠️ +28	0	0	0	0	0	0	0	⚠️ +28	0
libraries/Zigbee/examples/Zigbee_Range_Extender	⚠️ +28	0	⚠️ +28	0	0	0	0	0	0	0	⚠️ +28	0
libraries/Zigbee/examples/Zigbee_Thermostat	⚠️ +28	0	⚠️ +28	0	0	0	0	0	0	0	⚠️ +28	0
libraries/Zigbee/examples/Zigbee_Analog_Input_Output	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_CarbonDioxide_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Color_Dimmable_Light	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Contact_Switch	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Dimmable_Light	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Illuminance_Sensor	-	-	-	-	-	-	⚠️ +24	0	⚠️ +22	0	-	-
libraries/Zigbee/examples/Zigbee_OTA_Client	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Occupancy_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_On_Off_Light	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_PM25_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Pressure_Flow_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Scan_Networks	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Temp_Hum_Sensor_Sleepy	-	-	-	-	-	-	⚠️ +18	0	⚠️ +18	0	-	-
libraries/Zigbee/examples/Zigbee_Temperature_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Vibration_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Wind_Speed_Sensor	-	-	-	-	-	-	0	0	0	0	-	-
libraries/Zigbee/examples/Zigbee_Window_Covering	-	-	-	-	-	-	0	0	0	0	-	-

[github-actions]

Test Results

 76 files   76 suites   12m 41s ⏱️
 38 tests  38 ✅ 0 💤 0 ❌
241 runs  241 ✅ 0 💤 0 ❌

Results for commit 6eed3db.

♻️ This comment has been updated with latest results.

[Copilot]

Pull Request Overview

This PR adds battery voltage attribute support to the Zigbee Power Config Cluster by updating method signatures and implementations to accept battery voltage along with battery percentage.

• Updated ZigbeeEP.h to introduce a new parameter and method for battery voltage.
• Modified ZigbeeEP.cpp to update the setPowerSource method and implement setBatteryVoltage with corresponding error handling.
• Adjusted the Sleepy example to include the battery voltage parameter in the demonstration.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
libraries/Zigbee/src/ZigbeeEP.h	Added battery voltage parameter to setPowerSource and a new setBatteryVoltage method.
libraries/Zigbee/src/ZigbeeEP.cpp	Adjusted method signature for setPowerSource and implemented setBatteryVoltage; contains an incorrect error message for battery voltage.
libraries/Zigbee/examples/Zigbee_Temp_Hum_Sensor_Sleepy/Zigbee_Temp_Hum_Sensor_Sleepy.ino	Updated the example to use the new method signature with battery voltage.

[SuGlider]

LGTM