Add solax inverter model selector in config_flow to bypass discovery

[brew-your-own]

Proposed change

Add a selector for the type of Inverter in the solax integration config flow.
This will bypass the inverter discovery code which tends to crash some of the dongles out there.
This was made possible by release 3.1.0 in the upstream solax library which introduced a revamped
discovery code and the ability to only discovery a subset of all inverters, see
squishykid/solax#145

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: SolaX Power integration can't access inverter information (Failed to connect) #66617
• This PR is related to issue: SolaX Power integration can't access inverter information (Failed to connect) #66617

Checklist

• [x ] 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 @brew-your-own

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

Code owner commands

Code owners of solax 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 solax 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.

Stale

[Darsstar]

You beat me to it 😄

PS. you might want to remove the spaces before/after the xs in the Checklist section. Github isn't handling that correctly.

[Darsstar]

Sorry, I meant to click 'Request changes', not 'Approve'...

[brew-your-own]

made a few more changes following your feedback, WDYT?
I could not make ALL_COMPLETED work on my installation, I think some inverters do not like it...

[Darsstar]

Looks good.

Mind opening an issue on the solax repo about ALL_COMPLETED not working for you?

[emontnemery]

@brew-your-own the PR has merge conflicts, can you fix them or rebase the PR and click the "Ready for review" button when done please?

[frenck]

Because there hasn't been any activity on this PR for quite some time now, I've decided to close it for being stale.

Feel free to re-open this PR when you are ready to pick up work on it again 👍

../Frenck