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_cleanfrom 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).
- a stable identifier (
- 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_cleanfor 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
- Reporting the list of rooms by the Roborock integration.
- Core storage of areas + multiple selection in the vacuum panel.
app_segment_cleancommand on the selection.- Equivalent scene action.
(The interactive map and multi-floors would come in a second step.)
Mockup (generic house) of the target experience:

