Make IPP protocol version configurable

[LorbusChris]

Proposed change

ipp: Make IPP protocol version configurable
Adds a checkbox to optionally configure a printer with legacy IPP v1.1 instead of the default v2.0.

Fixes: #93211

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

• Continuation of ipp: Make IPP protocol version configurable #115661
• This PR fixes or closes issue: fixes IPP version incompatibility #93211
• 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 @ctalkington, mind taking a look at this pull request as it has been labeled with an integration (ipp) you are listed as a code owner for? Thanks!

Code owner commands

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

[LorbusChris]

This is a simple rebase of the closed and locked #115661
I'll fix up remaining linting issues as they are reported here.

@emontnemery requested to change the checkbox to a drop-down menu over in #115661 (comment). However, I disagree with that as this is a simple binary choice and I'd like to keep this change simple. This does obviously not preclude anyone from introducing such a change later.

[LorbusChris]

The linter config seems broken:

$ ruff format homeassistant tests
ruff failed
  Cause: Failed to parse /var/home/lorbus/code/hass-core/pyproject.toml
  Cause: TOML parse error at line 693, column 1
    |
693 | [tool.ruff.lint]
    | ^^^^^^^^^^^^^^^^
Unknown rule selector: `ASYNC220`

Edit: nevermind, looks like I had an outdated version of ruff installed

[LorbusChris]

This is ready for review. Could someone please start the CI pipeline?

@ctalkington could you approve this?

[emontnemery]

@LorbusChris Please change to a select selector which allows picking version 1.1 or 2.0 instead of a checkbox as requested in #115661

Here's an example of how to do that:

core/homeassistant/components/airzone_cloud/config_flow.py

Lines 66 to 78 in f428958

	data_schema=vol.Schema(
	{
	vol.Required(CONF_ID): SelectSelector(
	SelectSelectorConfig(
	options=[
	SelectOptionDict(value=k, label=v)
	for k, v in options.items()
	],
	mode=SelectSelectorMode.DROPDOWN,
	)
	),
	}
	),

Note that the selections can be translated too, but I guess that's not needed in this case

core/homeassistant/components/group/strings.json

Lines 219 to 233 in f428958

	"selector": {
	"type": {
	"options": {
	"last": "Most recently updated",
	"max": "Maximum",
	"mean": "Arithmetic mean",
	"median": "Median",
	"min": "Minimum",
	"product": "Product",
	"range": "Statistical range",
	"stdev": "Standard deviation",
	"sum": "Sum"
	}
	}
	},

[emontnemery]

@LorbusChris Please click the "Ready for review" button when you've updated

[LorbusChris]

@emontnemery see #128997 (comment)

Again, this is a binary choice and a dropdown menu for it complicates things unnecessarily.
I do not intend to make that change. If this change is unacceptable as-is, feel free to close this PR.

[ctalkington]

I'm aware of this PR and know there's been a bit of back and forth. I will do my best to review/approve before the end of the year.

[joostlek]

Is it possible to autodetect by connecting with v2, and if that fails go back to v1?

[ctalkington]

Is it possible to autodetect by connecting with v2, and if that fails go back to v1?

thats an idea for manual additions (zeroconf should mean it supports IPP 2.0 per spec) and possibly set a flag on the client for that "session". I might be able to do that upstream with a new parameters that catches first version exception and tries 1.0

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
If you are the author of this PR, please leave a comment if you want to keep it open. Also, please rebase your PR onto the latest dev branch to ensure that it's up to date with the latest changes.
Thank you for your contribution!