Entity IDs are generated by Home Assistant from the mower name. The examples below use a generic mower name.
lawn_mower.<mower>_kosiarka/ mower controlworx_vision_cloud.start_one_time_mowing/ service for one-time mowing with runtime, edge cutting and optional RTK zonesnumber.<mower>_czas_koszenia_jednorazowego/ one-time mowing runtimeselect.<mower>_strefy_koszenia_jednorazowego/ one-time mowing zone or zone groupswitch.<mower>_krawedzie_koszenia_jednorazowego/ start one-time mowing with edge cuttingbutton.<mower>_uruchom_koszenie_jednorazowe/ start one-time mowing using the selected runtime and zonesbutton.<mower>_odswiez/ request refreshbutton.<mower>_reset_czasu_pracy_nozy/ reset blade runtimebutton.<mower>_reset_cykli_baterii/ reset battery cycle counterbutton.<mower>_uruchom_przycinanie_krawedzi/ start edge-only cuttingupdate.<mower>_firmware/ firmware version, release notes and OTA install when supported
sensor.<mower>_harmonogramsensor.<mower>_nastepne_zaplanowane_koszenie/ next enabled native weekly schedule startcalendar.<mower>_harmonogram_koszeniaswitch.<mower>_harmonogram_kosiarki/ enable or disable the mower's native schedulenumber.<mower>_wydluzenie_czasu/ schedule time extensionnumber.<mower>_powierzchnia_trawnika/ lawn areanumber.<mower>_obwod_trawnika/ lawn perimeternumber.<mower>_dystans_krawedzi/ Vision border-cut distance, when supported
camera.<mower>_mapa_rtkdevice_tracker.<mower>_pozycja_rtksensor.<mower>_mapa_rtksensor.<mower>_punkty_sladu_rtk/ disabled by default, recent RTK trail pointssensor.<mower>_adres_rtk/ disabled by default, reverse-geocoded with OpenStreetMap Nominatim when enabled
- battery percentage
- status
- error
- mowing readiness / reason why mowing should or should not start
- cloud connection status
- API capabilities / disabled by default
- push notification state / disabled by default
- current zone / legacy zone value or RTK map zone containing the live mower position
- RSSI
- rain delay
- rain remaining
- configurable rain delay number
- battery voltage
- battery temperature
- battery cycle count
- battery cycles since reset
- battery cycle reset time
- blade runtime
- blade runtime reset time
- mower runtime
- mower time at home, charging and in error
- lawn area
- mowing efficiency
- maintenance status
- pitch, roll and yaw
- last update
- last update age
- total covered area / cumulative Worx cloud counter
- area mowed today (cloud) / daily delta from a persisted midnight baseline
- daily progress (cloud)
- remaining progress (cloud)
- estimated area mowed today / local blade-active time multiplied by long-term efficiency
- estimated daily progress
- cloud statistics updated / timestamp of the last successful product-statistics fetch
Cloud statistics can lag behind the mower because the private Worx endpoint may return an old cumulative value. Estimated statistics update from locally observed mower states and are explicitly approximate. Covered area includes overlapping passes and is not the same as unique physical lawn area.
- online
- IoT registered
- MQTT registered
- locked
- rain precipitation sensor
- robot lifted alarm
- party mode active
- pause mode active
- PIN setting capability
- Vision disable capability
- random mowing pattern capability
- map training capability
- diagnostic upload capability
- Smart edge cutting
- Save the hedgehogs
- One-time mowing edge cut
- Firmware auto update
- Mower lock
- Native schedule
- Rain delay
- Time extension
- Lawn area
- Lawn perimeter
- Vision border distance
- One-time mowing runtime
- One-time mowing zones
- Firmware
Starts one one-time mowing run.
entity_id- mower entity.runtime- mowing time in minutes, from0to120. Use0withedge_cut: truefor an edge-only run; on Vision Cloud this is sent as the dedicated edge-cut command.edge_cut- edge cutting flag. Useruntime: 0withedge_cut: truefor a dedicated edge-only run on Vision Cloud. The smart mowing blueprint starts edge cutting first, waits for a confirmed dock return, and then starts normal one-time mowing.zones- optional RTK zone ID list, for example[1, 2]. Leave empty for default/all-zone mowing.
Example:
action: worx_vision_cloud.start_one_time_mowing
data:
entity_id: lawn_mower.halina_kosiarka
runtime: 60
edge_cut: false
zones:
- 1Raw payload entities are disabled by default. They are useful while reverse-engineering API fields, but they can be noisy and may expose private data.
Blueprints and automations are maintained separately from the integration code: