Flume: Add flume.list_notifications service

[tronikos]

Proposed change

Add a service to return all user notifications. Goal is to alert in Home Assistant for any usage alert and not just the low flow leak or high flow for which we already have binary sensors. Using service response, automations can use the title and message in the response as is to call notify services in Home Assistant.

To avoid hitting the API quota, the service returns previously fetched notifications that are refreshed every 5 minutes.

This is an alternative to #100583

Example:

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: Document flume.list_notifications home-assistant.io#29543

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 @ChrisMandich, @bdraco, @jeeftor, mind taking a look at this pull request as it has been labeled with an integration (flume) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of flume 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 flume 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, @tronikos 👍

../Frenck

[tronikos]

Can this please be merged before Wednesday to make it in the next release?

[edenhaus]

Thanks @tronikos 👍

[edenhaus]

@tronikos Please open a docs PR, where you document the new service and link the PR in the description

[tronikos]

@tronikos Please open a docs PR, where you document the new service and link the PR in the description

home-assistant/home-assistant.io#29543