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>_harmonogramcalendar.<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 perimeter
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
- 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
- daily progress
- remaining progress
- mowed area today
- online
- IoT registered
- MQTT registered
- locked
- rain precipitation sensor
- robot lifted alarm
- party mode active
- pause mode active
- 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
- 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. For the most reliable "normal mowing plus edges" flow, start normal mowing first and then call this service again withruntime: 0andedge_cut: true. The smart mowing blueprint uses that two-step flow.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: