← statichum.studio

A brand-agnostic local-control plus open mapping/scheduling layer for retail robot mowers (Husqvarna, Worx, Eufy, Mammotion, Ecovacs, Sunseeker), so your zones and schedules aren't trapped in each vendor's cloud app

other real project •• multiple requests

Owners of Wi-Fi/Bluetooth robot mowers want local, manufacturer-independent control plus portable mapping, zones, and scheduling, because every brand ships its own cloud app and locks the data inside it. Right now this is served only by a swarm of separate per-brand reverse-engineering projects (one repo per manufacturer), so no unified, local, cross-brand control and mapping layer exists. The value is for homeowners and home-automation users who want their mower in Home Assistant and want maps that survive a vendor shutting down its cloud.

builder note

Don't try to boil the ocean across 20 brands at once; pick the 3-4 fastest-growing cloud-locked brands (Mammotion, Eufy, Sunseeker) and nail portable maps plus local scheduling, because the real moat - and the reason per-brand hacks keep dying - is sustained reverse-engineering as vendors rotate cloud auth.

landscape (4 existing solutions)

Robot mowers are as fragmented as early smart plugs: every brand has its own cloud app and no neutral layer offers cross-brand local control or portable mapping/scheduling over mowers you already own, which is why a Home Assistant forum thread tracking 18-20 brands and a swarm of single-brand repos keep re-solving the same problem separately.

Home Assistant lawn_mower entity platform Provides a unified entity type but every brand still needs a bespoke integration, mapping and zones are not standardized, some mowers are mis-exposed (Ecovacs GOAT shows up as a vacuum), and it requires running Home Assistant.
OpenMower Excellent open RTK-GPS control, but only for hardware you physically convert yourself, not the retail cloud-connected mowers people already own.
Per-brand community integrations (Mammotion-HA, Sunseeker, eufy-robomow-ha) Each one reverse-engineers exactly one brand and re-breaks when that vendor rotates cloud auth or firmware; the constant per-brand duplication is itself the evidence of the missing cross-brand layer.
Vendor cloud apps (Automower Connect, Worx Landroid, Mammotion) Walled gardens whose mapping and zones are non-portable and stop working if the manufacturer discontinues the cloud service.

sources (3)

other https://github.com/Sdahl1234/Sunseeker-lawn-mower/issues/67 "is it possible to use your integration with local MQTT?" 2026-06-15
other https://github.com/jnicolaes/eufy-robomow-ha/issues/5 "Can confirm, the setup works with a C15" 2026-05-18
other https://github.com/home-assistant/core/issues/169723 "Ecovacs GOAT A3000 LiDAR robotic lawn mower exposed as robot vacuum cleaner?" 2026-05-04
smart-homerobot-mowerhome-assistantinteroperabilityiot