Motion Blinds dhcp discovery

[starkillerOG]

Breaking change

Proposed change

Add DHCP discovery for the MotionBlinds integration

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)
• 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
• The code has been formatted using Black (black --fast 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[starkillerOG]

@bdraco could you review this PR since it is based on the comments you gave me in this merged PR: #68589

[starkillerOG]

@bdraco does the mac need to be formatted to ab:cd:ef:gh:ij:kl in order for the DHCP discovery to correctly match using the {"registered_devices": true} ?

edit: currently the mac of the Motion Blinds integration is formatted as abcdefghijkl

[bdraco]

Registered devices matches against the device registry, if you filled out connections, in device info, it will match

[starkillerOG]

I did, although the mac is formatted as abcdefghijkl in the device registry connections.
So it will match then.

[bdraco]

async_set_unique_id in the user path needs to set raise_on_progress=False so it doesn't abort if they choose the manual path over discovery

[starkillerOG]

@bdraco I just added the raise_on_progress, thanks for the explanation, I did not know why I would have needed that :)

[bdraco]

Looks good.

[starkillerOG]

@bdraco any more feedback?

[bdraco]

LGTM 👍