Fix config entries not recovering from IP address changes in Midea

[chemelli74]

Proposed change

Fix config entries not recovering from IP address changes in Midea

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 Midea config entries do not recover after DHCP IP address changes #179698
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes 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.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[home-assistant]

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

Code owner commands

Code owners of midea can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign midea Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[rokam]

@chemelli74 I think you can create a repair to prompt for new IP if the IP isn't auto discovered. What do you think about this?

[chemelli74]

@chemelli74 I think you can create a repair to prompt for new IP if the IP isn't auto discovered. What do you think about this?

Looks like a good idea, but I'm not sure it's allowed.
Will investigate.

[gjohansson-ST]

Should this not be a discovery flow?

I think you can create a repair to prompt for new IP if the IP isn't auto discovered. What do you think about this?

That would trigger if the entity would be turned off, doesn't sound like a good idea.

[chemelli74]

Should this not be a discovery flow?

Unfortunately the device won't send any data until force a discover(), so I don't think discovery applies

[gjohansson-ST]

It does sound like you speak about dhcp which can be used for discovery flows.

[chemelli74]

It does sound like you speak about dhcp which can be used for discovery flows.

Unfortunately not as you will have a infinite list of MAC addresses taking into account Midea is used by 15+ brands; and not all device for the same brand use this protocol 🙃