Raise an issue when the Roborock local api is unavailable.

[Lash-L]

Breaking change

Proposed change

Right now we simply put a warning in the logs. I think a lot of users miss this and leave their integration in a less than ideal state. This hopefully will make it clear to them that they should make changes to their networking setup.

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

Code owner commands

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

[Copilot]

Pull Request Overview

This PR raises a Repairs issue when the Roborock integration falls back to the cloud API, guiding users to adjust their network setup to enable local access.

• Add issue creation/deletion in the coordinator when local API fails/succeeds.
• Add localized strings for the new issue.
• Add tests verifying issue creation and cleanup when switching between cloud and local API.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
homeassistant/components/roborock/coordinator.py	Creates a Repairs issue when the integration uses the cloud API and deletes it when local API is reachable again.
homeassistant/components/roborock/strings.json	Adds title and description for the new Repairs issue.
tests/components/roborock/test_coordinator.py	Adds a test to assert issue creation for cloud fallback and removal after returning to local API.

[Copilot]

RoborockLocalClientV1.ping is awaited in the coordinator; patching it without an AsyncMock can cause await errors. Use an AsyncMock for the side effect and import AsyncMock: with patch('homeassistant.components.roborock.coordinator.RoborockLocalClientV1.ping', new=AsyncMock(side_effect=RoborockException()))

[Copilot]

This patch replaces an awaited coroutine with a regular MagicMock, which will raise 'object MagicMock can't be used in 'await' expression'. Patch with an AsyncMock that returns None: with patch('homeassistant.components.roborock.coordinator.RoborockLocalClientV1.ping', new=AsyncMock(return_value=None))

[Lash-L]

I don't think these are necessary, but if a core dev wants me to I will make these changes to AsyncMock

[allenporter]

This is a great change, thank you for doing this.

I think it would be useful to also have something in the integration documentation with additional detail about what this error means and how a user can fix it, since many users may not know practically what to do. Want to send a PR for that and add a more info link to the integration docs in the repair issue text?

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Lash-L]

Almost certainly will conflict with #154837