Catch client connection error in Honeywell

[mkmer]

Proposed change

Catch client connection error at startup (and retry)
Improve typing in config flow

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:

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]

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

Code owner commands

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

[PeteRager]

This looks like two pull requests, as the changes in config_flow.py appear to have nothing to do with catching the client connection error during startup. If so, consider breaking this into two pull request.

Also the changes should be reflected in the tests for the integraiton.

[PeteRager]

Changes look good to me, though I'd prefer the minor formatting changes to config_flow.py to be in a seperate PR

[mkmer]

Once I've touched the file, ruff reformatted it to the newer rules and won't let me put it back - might as well just accept the future at this point :) I know i can jump through hoops to rewind the commit... but is it really worth it?

[PeteRager]

I'm ok with it.

[edenhaus]

Normally you would need to split the config flow changes to a new PR. But it's okay for this time. In the future please add unrelated changes to a new PR :)
Please add to the description that you improved the typing of the config flow

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

[PeteRager]

LGTM

[edenhaus]

Thanks @mkmer 👍