Add the device of the source entity in the helper entities for Utility Meter

[dougiteixeira]

Breaking change

None

Proposed change

Adds the device of the source entity in the helper entities for Utility Meter.

It was inspired by this comment (link).

Summary of the implementation in all helpers:

Helper	Helper Domain	PR
Derivative sensor	derivative	#94751
Integration - Riemann sum integral sensor	integration	#94727
Threshold Sensor	threshold	#94753
Utility Meter	utility_meter	#94734
Combine the state of several sensors	min_max	Can contain many source entities... how should it be handled?
Group	group	Can contain many source entities... how should it be handled?
Change device type of a switch	switch_as_x	Already implemented
Counter	counter	Does not come from a source entity
Toggle	input_boolean	Does not come from a source entity
Button	input_button	Does not come from a source entity
Date and/or time	input_datetime	Does not come from a source entity
Number	input_number	Does not come from a source entity
Dropdown	input_select	Does not come from a source entity
Text	input_text	Does not come from a source entity
Schedule	schedule	Does not come from a source entity
Timer	timer	Does not come from a source entity
Times of the Day Sensor	tod	Does not come from a source entity

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 PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

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]

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

Code owner commands

Code owners of utility_meter 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 utility_meter Removes the current integration label and assignees on the pull request, add the integration domain after the command.

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

[frenck]

Thanks, @dougiteixeira 👍

../Frenck