New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid probing ipp printers for unique_id when it is available via mdns #99982
Conversation
We would always probe the device in the ipp flow and than abort if it was already configured. We avoid the probe for most printers.
Hey there @ctalkington, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
I had some stability issues with my printer and tracked it down to this. I also have 12 HA test installs on my network though |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
Thnx @bdraco 👍
It looks like |
thanks @bdraco sorry just saw this |
#99982) * Avoid probing ipp printers for unique_id when it is available via mdns We would always probe the device in the ipp flow and than abort if it was already configured. We avoid the probe for most printers. * dry * coverage * fix test * add test for updating host
Proposed change
We would always probe the device in the ipp flow and than abort if it was already configured. We avoid the probe for most printers.
This can cause some printers to lock up when there are many HA instances on the network.
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: