Native management of robot vacuum cleaner cleaning maps

Objective

Allow Gladys to natively manage zones/rooms of a robot vacuum, in order to launch targeted cleaning by room from the interface and scenes — without depending on a specific widget or the manufacturer’s app.

Following the exchange with @pierre-gilles, the request is reformulated: rather than a simple widget component « clickable zones », it is a matter of adding the notion of service surface (Service Area) at the heart of Gladys, aligning with the Matter – Service Area cluster standard. The widget will then only expose this existing functionality.

The Need

Today, the Roborock integration can display the map (via onWidgetGetImage), but:

  • the map is a static image: no way to detect a click on a room;
  • there is no notion of room/zone on the Gladys core side;
  • it is therefore impossible to launch a targeted app_segment_clean from Gladys, nor to use it in a scene.

Proposal (Core Approach, Aligned with Matter)

1. Core Data Model

  • A vacuum cleaner device can declare a list of service areas (rooms), each with:
    • a stable identifier (segment_id / area_id),
    • a name (« Kitchen », « Living Room »…),
    • optionally a map/floor to which it belongs (multi-map / multi-floor support).
  • These areas are reported by the integration (Roborock, Dreame…) and stored on the Gladys side, based on the Matter Service Area cluster model (SupportedAreas, SelectedAreas, CurrentArea).

2. Selection & Command

  • From the vacuum panel: selection of one or more rooms, then « Start Cleaning ».
  • The integration translates the selection into a native command (app_segment_clean for Roborock, Dreame equivalent…).

3. Scenes

  • A scene action « Clean room(s) X » using the declared areas (e.g. « clean the kitchen at 9 a.m. »).

4. Widget

  • The map widget displays the declared areas and relays the selection (e.g. via onWidgetAction) to this core functionality — it no longer carries the business logic.

Points to Specify / Open Questions

  • Multi-maps / multi-floors: how to model multiple maps per device.
  • Segment Synchronization: room IDs can evolve on the manufacturer’s side (re-mapping) → refresh/reconciliation strategy.
  • Naming: names imported from the manufacturer’s cloud vs names defined in Gladys.
  • Map Interface: display the areas over the decoded image, or settle for a list of checkboxes in a first step (MVP).
  • Matter Mapping: which attributes/commands of the Service Area cluster are exactly exposed.

Proposed MVP Scope

  1. Reporting the list of rooms by the Roborock integration.
  2. Core storage of areas + multiple selection in the vacuum panel.
  3. app_segment_clean command on the selection.
  4. Equivalent scene action.

(The interactive map and multi-floors would come in a second step.)


Mockup (generic house) of the target experience:

Hi @spenceur,

Thanks for the request and the mockup! The need is real, and it aligns with what’s happening on the Dreame side: Robotic Vacuums: A Complete Control Line in the Devices Box.

Instead of generic clickable areas in the widgets, I propose:

  1. Room selection becomes a core vacuum feature, aligned with the Matter Service Area cluster: rooms are declared by device, you select multiple, and « Start » launches the cleaning. This works for Roborock, Dreame, and Matter, in the vacuum panel and in the scenes.
  2. Your widget simply displays this feature: you reference it like a value tile today, and Gladys draws the room pills. The selection is shared across all screens.
  3. The map remains an image: as your integration receives the selection, you can draw the selected rooms on it.

This touches the data model, so we’ll need to start with a clean spec :slight_smile:

Wow, this is a VERY interesting topic!!! :grinning_face:

That would be great. Where can I vote? I’m for it…

here at the title level :wink:

:slight_smile: you guys hid that really well… thanks

@spenceur I updated the title of the request, does that work for you? Can you modify the content of the request? :slight_smile:

I’ve seen that I’m a bit swamped at the moment on a client project, but I’ll look at it as soon as I have 10 minutes.

@pierre-gilles I’ve updated the request content based on your feedback: the proposal is now focused on native management of zones/rooms at the heart of Gladys, aligned with the Matter Service Area cluster, with the widget simply exposing the functionality. I’ve added a « Points to specify / open questions » section and an MVP scope proposal. Let me know if this works for you, or if you’d prefer that I go as far as a full detailed spec.