Add unifi power stats for PDU outlets

[Cisien]

Proposed change

This PR adds support for the Unifi component to pull power statistics from power outlets on PDU devices that support providing power data.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

This change was developed against the USP-PDU-Pro device, and tested with the USP-Plug as a device that shows up in the outlets API, but does not support power reporting. Additionally, the PDU-Pro has four outlets that are USB-C ports, which do not report power. In all cases, outlets that don't support this function are not included as power sensors.

My setup includes two PDU-Pro devices which properly associate their respective plugs.

• This PR fixes or closes issue: N/A
• This PR is related to issue: N/A
• Link to documentation pull request: Adds documentation for unifi PDU power sensors feature home-assistant.io#28524
• This PR fulfills the requirements in this feature request: https://community.home-assistant.io/t/support-for-usp-pdu-pro-in-the-ubiquity-integration/550746

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @Cisien

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Hey there @Kane610, mind taking a look at this pull request as it has been labeled with an integration (unifi) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of unifi can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign unifi Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[Cisien]

I did notice one issue when I run this locally in my "production" instance of HA, but suspect it's related to how I'm overriding.

The localized strings don't show up in the "Configure" wizard for the integration. I am testing this locally by simply copying the unifi folder from my branch to custom_components and adding a version to the manifest.

Please let me know if this doesn't sound like something related to my local hacked up setup and i'll dig into it further.

[Kane610]

Thanks!

Im mostly worried about properly matching devices supporting metering as with if looking at caps would be enough.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Cisien]

the PDU device has a few metrics that are exposed that provide info about the power budget and utilization all-up. I'm going to expand this PR to include diagnostics for those counters as well.

[Kane610]

the PDU device has a few metrics that are exposed that provide info about the power budget and utilization all-up. I'm going to expand this PR to include diagnostics for those counters as well.

If it's small else it's better to do a small separate pr

[Cisien]

I'll create a new PR for it

[Kane610]

Awesome! Now only an update to the integration documentation is needed.

[Cisien]

Ok, i'll look into what is needed to make that happen.

I also just noticed that the PDU outlets don't get switch entities. I'm guessing because they are missing the "has_relay" property, so i'll probably look into a separate PR to address that.

[Kane610]

Ok, i'll look into what is needed to make that happen.

I also just noticed that the PDU outlets don't get switch entities. I'm guessing because they are missing the "has_relay" property, so i'll probably look into a separate PR to address that.

You can create a documentation PR in less than five minutes from github directly and you have two weeks to go :).

Maybe investigate if we can utilize caps for the switch? This is what I got stuck on last time trying to figure out the common denominator.

[Cisien]

Maybe investigate if we can utilize caps for the switch? This is what I got stuck on last time trying to figure out the common denominator.

That would be convenient, wouldn't it? Unfortunately, the USP-Plug devices don't expose an outlet_caps property.

[Cisien]

PR for docs repo: home-assistant/home-assistant.io#28524