You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lawn_mower entity was introduced back in Home Assistant 2023.9 as a building block integration, supporting states of Mowing, Docked, Paused, Returning, and Error, with three core actions start_mowing, pause, and dock.
Since then, several integrations have built on top of it (e.g. Husqvarna Automower, Mammotion, Worx Landroid, SunSeeker, and others via HACS), but the default more-info dialog has received almost no dedicated UI attention. Consequently, users consistently reach for custom cards to fill the gap.
This opportunity can be seen as a continuation of #35, but for lawn mowers.
Community signals
The vacuum dialog redesign as a direct template (issue Refined more info screen for vacuum cleaners #35 / frontend #51380)
The most immediately relevant reference is the work already in flight for vacuum cleaners focusing on purely cosmetic "modernisation", alignment with recently designed dialogs (Cover, Thermostat, Light, etc.), and exposing the segment cleaning feature on the dialog.
PR #51380 introduces a new SVG illustration of the vacuum with state-driven animations (cleaning rotation, returning, docked glow, error shake), a unified action button row with battery moved into the header, a new "Clean by area" sub-view to start cleaning specific HA areas mapped to the vacuum, an empty state in that view prompting admins to add area mappings, and a shortcut from the dialog header for admins to configure the area mapping.
This is the closest existing precedent for what a lawn mower dialog should become. Almost every element maps directly: the illustration, state animations, unified controls, battery in header, and zone/area selection are all equally relevant for robotic mowers.
Community workarounds reveal unmet default UI needs
The fact that multiple independent community custom cards exist is a clear signal that the built-in more-info dialog is insufficient. Two mature HACS cards in particular reveal what users often refer to as good / working solutions:
lawn-mower-card (bhuebschen/cociweb): By default, Home Assistant provides no dedicated card for controlling lawn mowers. This card displays state, supports a battery sensor, custom stats (area mowed, mowing time, blade life), context-sensitive stat views depending on state, camera stream support for live map, and override-able action shortcuts for zone-specific mowing scripts.
landroid-card (Barma-lej): Supports fully customisable shortcut buttons, zone-specific mowing actions (e.g. mowing zone 2 via a script), rain delay display, and four distinct info panels: battery, connectivity, schedule, and configuration — triggered by dedicated toolbar buttons.
These custom cards collectively point to six UI needs not served by the current default dialog:
Battery level prominently displayed
Context-sensitive stats (different data shown while mowing vs. docked)
Zone/work area selection for targeted mowing
Cutting height adjustment
Schedule visibility
Custom action shortcuts
Integration-level features the UI doesn't surface
The Husqvarna Automower integration reflects one of the most feature-complete examples and reveals how much is already supported at the data layer with no UI path:
The integration exposes work areas (e.g. Front lawn, Back lawn), per-work-area cutting height, stay-out zone switches, a schedule enable/disable switch, a calendar entity, inactive reason (e.g. searching for satellites), restricted reason (e.g. frost, daily limit), and an override schedule action.
None of this surfaces in the more-info dialog today. Instead, users need to navigate to the device page or build their own cards. The parallel for vacuum is strong: the vacuum dialog was similarly leaving segment cleaning entirely inaccessible.
Automation-driven usage patterns that suggest UI needs
Community members are building sophisticated mowing automations, like weather-based pausing, solar surplus triggering, child/pet presence detection, frost prevention, but, mostly by hand. A more representative community example uses per-zone schedule input selects, last-mow tracking, and rain delay logic to create a fully hands-off mowing scheduler.
This suggests the default UI should at minimum make it easy to see:
current state and reason (especially why it's not mowing),
battery, and next scheduled mow.
The scheduler complexity itself is probably out of scope for the dialog, but surfacing schedule status clearly (like the vacuum's "Clean by area" view) would reduce the motivation to build these workarounds.
Hardware ecosystem context
The community identifies a large number of mower brands (Antbot, Ecovacs, Kress, Sunseekers, Dreame, Mammotion, Navimow, Eufy, Airseekers, Husqvarna, Worx, and more), with local communication being a rare exception as most rely on cloud APIs.
This matters for UI design because it means graceful degradation is important: the dialog should look good and behave sensibly even when not all capabilities are available (no work areas, no cutting height, etc.), which is a common pattern for the vacuum cleaners redesign too.
Finally, as of the 2025.4 release, lawn mower devices gained support in Google Assistant and HomeKit which amplifies our efforts for a more revamped more-info redesign, like started in #35 for vacuum cleaners.
State-driven SVG illustration with animations (mowing, returning, docked, error)
Battery level in the dialog header
Unified action button row (start/pause, dock, with correct disabled states per state)
Modernised visual style matching e.g. vacuum cleaners
Lawn-mower-specific additions with strong community signal:
"Mow by zone/work area" sub-view (analogue of vacuum's "Clean by area") as heavily requested across Husqvarna users and custom cards
Contextual status text surfacing inactive/restricted reason (e.g. frost, daily limit, low battery) especially interesting to users when the mower isn't running
Cutting height control where supported (already modelled in Husqvarna integration)
The appetite in #35 is framed as "small, 1–2 weeks max" for cosmetic work, with the area cleaning sub-view as the main functional addition. A lawn mower dialog could reasonably be scoped the same way, with work areas as the functional centerpiece.
Problem statement
The lawn_mower entity was introduced back in Home Assistant 2023.9 as a building block integration, supporting states of Mowing, Docked, Paused, Returning, and Error, with three core actions start_mowing, pause, and dock.
Since then, several integrations have built on top of it (e.g. Husqvarna Automower, Mammotion, Worx Landroid, SunSeeker, and others via HACS), but the default more-info dialog has received almost no dedicated UI attention. Consequently, users consistently reach for custom cards to fill the gap.
This opportunity can be seen as a continuation of #35, but for lawn mowers.
Community signals
The most immediately relevant reference is the work already in flight for vacuum cleaners focusing on purely cosmetic "modernisation", alignment with recently designed dialogs (Cover, Thermostat, Light, etc.), and exposing the segment cleaning feature on the dialog.
PR #51380 introduces a new SVG illustration of the vacuum with state-driven animations (cleaning rotation, returning, docked glow, error shake), a unified action button row with battery moved into the header, a new "Clean by area" sub-view to start cleaning specific HA areas mapped to the vacuum, an empty state in that view prompting admins to add area mappings, and a shortcut from the dialog header for admins to configure the area mapping.
This is the closest existing precedent for what a lawn mower dialog should become. Almost every element maps directly: the illustration, state animations, unified controls, battery in header, and zone/area selection are all equally relevant for robotic mowers.
The fact that multiple independent community custom cards exist is a clear signal that the built-in more-info dialog is insufficient. Two mature HACS cards in particular reveal what users often refer to as good / working solutions:
lawn-mower-card (bhuebschen/cociweb): By default, Home Assistant provides no dedicated card for controlling lawn mowers. This card displays state, supports a battery sensor, custom stats (area mowed, mowing time, blade life), context-sensitive stat views depending on state, camera stream support for live map, and override-able action shortcuts for zone-specific mowing scripts.
landroid-card (Barma-lej): Supports fully customisable shortcut buttons, zone-specific mowing actions (e.g. mowing zone 2 via a script), rain delay display, and four distinct info panels: battery, connectivity, schedule, and configuration — triggered by dedicated toolbar buttons.
These custom cards collectively point to six UI needs not served by the current default dialog:
The Husqvarna Automower integration reflects one of the most feature-complete examples and reveals how much is already supported at the data layer with no UI path:
The integration exposes work areas (e.g. Front lawn, Back lawn), per-work-area cutting height, stay-out zone switches, a schedule enable/disable switch, a calendar entity, inactive reason (e.g. searching for satellites), restricted reason (e.g. frost, daily limit), and an override schedule action.
None of this surfaces in the more-info dialog today. Instead, users need to navigate to the device page or build their own cards. The parallel for vacuum is strong: the vacuum dialog was similarly leaving segment cleaning entirely inaccessible.
Community members are building sophisticated mowing automations, like weather-based pausing, solar surplus triggering, child/pet presence detection, frost prevention, but, mostly by hand. A more representative community example uses per-zone schedule input selects, last-mow tracking, and rain delay logic to create a fully hands-off mowing scheduler.
This suggests the default UI should at minimum make it easy to see:
The scheduler complexity itself is probably out of scope for the dialog, but surfacing schedule status clearly (like the vacuum's "Clean by area" view) would reduce the motivation to build these workarounds.
The community identifies a large number of mower brands (Antbot, Ecovacs, Kress, Sunseekers, Dreame, Mammotion, Navimow, Eufy, Airseekers, Husqvarna, Worx, and more), with local communication being a rare exception as most rely on cloud APIs.
This matters for UI design because it means graceful degradation is important: the dialog should look good and behave sensibly even when not all capabilities are available (no work areas, no cutting height, etc.), which is a common pattern for the vacuum cleaners redesign too.
Finally, as of the 2025.4 release, lawn mower devices gained support in Google Assistant and HomeKit which amplifies our efforts for a more revamped more-info redesign, like started in #35 for vacuum cleaners.
Scope & Boundaries
In scope
Lawn-mower-specific additions with strong community signal:
Not in scope
Foreseen solution
wip
Risks & open questions
None know at the moment
Appetite
Small - 1-2 weeks
The appetite in #35 is framed as "small, 1–2 weeks max" for cosmetic work, with the area cleaning sub-view as the main functional addition. A lawn mower dialog could reasonably be scoped the same way, with work areas as the functional centerpiece.
Execution issues
No response
Decision log