Improve Roborock exception logging behavior for Zeo/Dyad devices

[allenporter]

Proposed change

Update the coordinator to catch the integration library specific exceptions and raise UpdateFailed to reduce exceptions in the log message

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: #
• This PR is related to issue: Roborock devices a01 dyad/zeo devices unavailable with error "Error starting MQTT session: [code:135] Not authorized" #158294
• 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 @Lash-L, 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 improves exception handling for Roborock Zeo (washing machine) and Dyad (wet dry vacuum) devices by catching library-specific RoborockException and raising UpdateFailed exceptions with translation keys. This prevents raw exceptions from appearing in logs and provides better user-facing error messages.

Key Changes

• Added try-catch blocks in both RoborockWashingMachineUpdateCoordinator and RoborockWetDryVacUpdateCoordinator to catch RoborockException and raise UpdateFailed with proper translation keys
• Added comprehensive test coverage for failure scenarios in both Zeo and Dyad device setup

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
homeassistant/components/roborock/coordinator.py	Added exception handling in _async_update_data methods for both washing machine and wet dry vac coordinators, following the same pattern used in the main vacuum coordinator
tests/components/roborock/test_init.py	Added two new tests to verify that when Zeo or Dyad devices fail during setup, the integration still loads successfully and excludes the failed device from the device registry