Skip to content

S7 MaxV Ultra: Dock Dryer Module (HADM02RR) on Empty Wash Fill Dock (o3_dock) not detected - no mop dryer trait #1037

Open

Description

@thomaswitt

Device

  • Robot: Roborock S7 MaxV (roborock.vacuum.a27), firmware 02.59.36
  • Dock: Empty Wash Fill Dock (dockType: 3 -> RoborockDockTypeCode.o3_dock)
  • Accessory: official Roborock Dock Dryer Module for S7 MaxV Ultra (MPN HADM02RR) installed
  • python-roborock 7.12.0 via Home Assistant 2026.11.1 (core roborock integration)

Problem
RoborockDockFeatures.is_dryable is False for o3_dock, because it is in _COLLECT_WASH_DOCK_TYPES and therefore excluded from is_collect_wash_dry. As a result MopDryerTrait is never set up and Home Assistant does not create the dock "Mop drying" switch. The "Mop drying remaining time" sensor is created but is always unknown.

The device itself does advertise drying support:

  • device_features.isSupportedDrying: true
  • the product schema contains DPS 134 drying_status
  • get_status currently returns no dryStatus / rdt, and deviceStatus has no 134 key (robot idle/docked; not checked during an active drying cycle)

For comparison, a second robot on the same account (roborock.vacuum.a144, dockType: 16) reports dryStatus / rdt and gets the switch.

Expected
The dryer is an optional add-on for the o3 dock, so drying support cannot be derived from the dock type alone. Suggestion: for o3_dock, treat the dock as dryable when isSupportedDrying is true and/or when APP_GET_DRYER_SETTING returns a valid MopDryerSetting (probe once at setup).

Diagnostics can be provided on request, and I can test app_get_dryer_setting / app_set_dryer_setting / app_set_dryer_status on the device.

Activity

  1. ryanmac8 commented on Nov 18, 2026

    @ryanmac8

    Independent confirmation on the same hardware combo, plus the probe result the issue mentions as untested.

    Setup: S7 MaxV (roborock.vacuum.a27), firmware 02.59.36, o3_dock, HADM02RR module installed.

    • device_features.is_supported_drying is True
    • APP_GET_DRYER_SETTING returns a valid MopDryerSetting on this device, so the module is detected and configurable over RPC:
    {"status": 1, "on": {"cliff_on": 1, "cliff_off": 1, "count": 10, "dry_time": 10800}, "off": {"cliff_on": 2, "cliff_off": 1, "count": 10}}
    • APP_GET_DRYER_STATUS and get_dock_summary are not recognized by this firmware (RoborockUnsupportedFeature), so APP_GET_DRYER_SETTING is the one to use for detection.
    • get_status still carries no rdt/dry_status while the robot is docked and idle, which is why the remaining-time sensor stays unknown until a cycle runs.

    I implemented the is_supported_drying part of the suggestion in #1065, which makes is_dryable true for o3_dock when the device advertises drying, and verified the trait now appears on the hardware above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions