Reduce log level for creating ZHA cluster handler

[TheJulianJES]

Proposed change

This lowers the log level for creating a ZHA cluster handler from info to debug.

IMO, there's little to no value in seeing many lines of ZHA creating cluster handlers during startup, even when you choose to see the more verbose info log level (instead of the default warning level).

As an example, starting my production HA instance with ~150 ZHA devices causes this: https://dpaste.org/ah7Mu
So, a total of 1160 lines of logging just for ZHA cluster handlers. Generally, the info logging isn't spammy otherwise.

The logs were added with the ZHA refactor PR: #91476
I've left this in draft for now. Maybe there's a good reason this was added to info instead of debug in the first place?

"Warning" log

Note: If a cluster handler can't be created, a (more important) warning will still be logged:

core/homeassistant/components/zha/core/endpoint.py

Lines 141 to 145 in df9faea

	try:
	cluster_handler = cluster_handler_class(cluster, self)
	except KeyError as err:
	_LOGGER.warning(
	"Cluster handler %s for cluster %s on endpoint %s is invalid: %s",

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

Code owner commands

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

[dmulcahey]

No reason. Level just wasn’t knocked down before merging. Tagging it for the next milestone and you can mark it ready.

[puddly]

Thanks! These really do contribute a lot to log spam 😄.