Add RainMachine config option to use default run times from app

[shbatm]

Proposed change

Adds an option to RainMachine for the integration to use the default per-zone run times a user has set in the RainMachine app when turning on a zone from Home Assistant.

Currently, the user can specify a default run time that all zones share when toggling the switch from the front end. If the new option is enabled, the integration uses the last manual watering time for each zone from the app.

Defaults to False to prevent breaking changes.

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 #n/a
• This PR is related to issue: Add additional sensors to RainMachine #80914 (comment)
• Link to documentation pull request: Add RainMachine config option to use default run times from app home-assistant.io#24706

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

Code owner commands

Code owners of rainmachine can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant unassign rainmachine Removes the current integration label and assignees on the issue, add the integration domain after the command.

[shbatm]

@bachya Take a look and let me know if you can think of a better way to store/grab the values. I'll try and explain my reasoning here:

The zoneDurations is from the /provision endpoint, so it's not updated at the same time as the zones. It's also only a unreferenced array of times, in the same order as the list of zones.

Because it's in a different update coordinator, and to not have to perform any intensive lookups at the time of a turn_on call, I went with the plan to store the duration for each zone as an attribute for that zone entity if this option is turned on. It's updated whenever the zone is updated. The turn_on call just uses this attribute if no other duration is provided.

[bachya]

Initial comments.

[bachya]

Looks good to me! @bdraco, you want to weigh in further?