Skip to content

Add Missing Q10 Feature support #767

Open

Description

@lboue

This issue is an omnibus of all the missing features from Q10 devices.

Higher Priority

  • Map (multi-map, restricted zones, virtual walls, room management)
  • Cleaning history
  • Battery
  • Cleaning mode
  • Fan level

Lower Priority

  • Basic vacuum control (start, pause, resume, stop, dock)
  • Empty dustbin
  • Consumable status (main brush, side brush, filter, rag life)
  • Consumable Resets
  • Mop state
  • Carpet Cleaning Settings (carpet clean prefer, auto boost, carpet clean type)
  • Floor Material / Ground Clean settings
  • Robot voice volume
  • DnD (Do Not Disturb)
  • Valley Point Charging (Off peak)
  • Child lock
  • Button lights
  • Remote Control
  • Timers
  • Unit settings (area unit, time zone)
  • Clean line preference
  • Self-identifying carpet
  • Obstacle avoidance settings

Activity

  1. TangerineNightmare commented on Apr 23, 2026

    @TangerineNightmare

    for what it is worth there is a new open source project at https://codeberg.org/zcodeberg/roborock-q10-utils-gpl that implements a subset of the Q10v+ mobile app functionality as a self-hostable python web interface. It includes some API information that may or may not be of use?

    https://codeberg.org/zcodeberg/roborock-q10-utils-gpl/src/branch/main/Q10_API_REFERENCE.md

  2. hCoureau commented on Aug 31, 2026

    @hCoureau
    Contributor

    Q10 map and cleaning contribution stack

    Tracking the current contribution sequence here so each change can remain small and independently reviewable:

    The stack is deliberately sequential so each upstream PR shows only its own logical diff against main.

  3. tprommi commented on Oct 11, 2026

    @tprommi

    Environment: Home Assistant Core 2026.9.4, python-roborock 7.12.0, Roborock Q10 S5 (ss07), firmware 03.11.26.

    I’m using a Roborock Q10 S5 with three saved maps for the basement, ground floor, and upper floor. Home Assistant currently receives the room segments for the active map with numeric room IDs only. When I switch maps and configure the area mapping again, the mappings for the other floors are replaced. The same room IDs can refer to different rooms on different maps. For example, on my ground-floor map, segment 1 is “Corridor” and segment 3 is “Kitchen”, while those IDs were previously mapped to other areas.

    Could the Q10 API expose the map ID together with the room segments for all saved maps? Home Assistant could then use stable segment IDs containing both the map ID and room ID, preserving area mappings across floors and avoiding incorrect room cleaning after a map switch.

    One additional observation: the Roborock app shows six rooms on my ground-floor map, but Home Assistant receives seven segments and reports “Relax” twice (IDs 4 and 7).

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