Add Balboa spa temperature range state control (high/low)

[kotope]

Proposed change

Adds temperature range switch support (high/low) to Balboa spa integration.

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: Update Balboa spa integration documentation (core PR #115285) home-assistant.io#32236

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 Ruff (ruff format 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 @kotope

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]

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.

[home-assistant]

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

Code owner commands

Code owners of balboa 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 balboa Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[kotope]

Updated documentation PR: home-assistant/home-assistant.io#32236

Stale

[jpbede]

I do find a switch entity somewhat confusing for this use case. I think a select entity would would make more sense here.

[kotope]

I do find a switch entity somewhat confusing for this use case. I think a select entity would would make more sense here.

Thanks for pointing out this @jpbede

I will do the change from switch to select soon and push a new commit :-)

[kotope]

I do find a switch entity somewhat confusing for this use case. I think a select entity would would make more sense here.

Changed to select entity now.

[kotope]

Thanks for reviewing @jpbede!

Issues you mentioned should be resolved now.
Takes a while to get into HA + python. Hopefully my future tasks will go more smooth :-)

[jpbede]

No, worries we all started somewhen 🙂
This looks good now, thanks 👍