Bump pyenphase to 1.23.1

[catsmanac]

Proposed change

Bump pyenphase to 1.23.1,

https://github.com/pyenphase/pyenphase/releases/tag/v1.23.1

Changes in this release: pyenphase/pyenphase@v1.23.0...v1.23.1

Select.py updated for possible None from pyenphase for storage_settings.mode.
test_select.py extended with test case.

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 Enphase Envoy Error - "None is not a valid EnvoyStorageMode" #135570
• 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 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.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

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

Code owner commands

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

[joostlek]

what is the mode in this case? considered using .get()?

Anyway, let's wrap multiline lambdas in parenthesis

[catsmanac]

Value_fn will be None and resulting State will be unknown. User can set it to one of the defined states if desired, but in practice the switch will never be created and code not executed. But data in library changed from EnvoyStorageMode to EnvoyStorageMode | None and mypy ci check didn't like it. Hence the added test.

(Issue is with None not being a key in STORAGE_MODE_MAP, .get still returns None)

Parenthesis added for the lambda.

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

[catsmanac]

Thanks for the review Joost, @joostlek