Is it possible to start/stop/pause the lawn mower’s schedule via the integration?

[tomasenskede]

Hi!

I’m using the integration for my lawn mower (lawn_mower.shaun) in Home Assistant and wondering if there is support for controlling the lawn mower’s schedule via services in Home Assistant?

Currently, I can use services like lawnmower.start, lawnmower.pause, and lawnmower.stop, but these only control the mower directly—that is, to start, pause, or stop the mowing immediately.

My question is if there is any way to start, stop, or pause the automatic mowing schedule through the integration? In other words, to control whether the mower follows its planned schedule or not, without having to manually start or stop it every time.

I haven’t found anything about this in the documentation and would appreciate any help or tips!

Thanks in advance!

[sabbatho]

Hi,
I have setup all the scheduling in automations in Home Assistant.
I do not use the scheduling in Gardena app at all, even if it is there.

I only use action: lawn_mower.pause and action: gardena_smart_system.start_override
With these actions the schedule is overriden.

Hope this is what you meant? :)

[tomasenskede]

Hmm, so the smart scheduling isn’t in use then – you’re starting and stopping everything via Home Assistant automations? I’ve noticed the integration isn’t very stable at the moment… it often stops working. Are you still relying on Home Assistant for the scheduling, or have you had issues with it too?

[sabbatho]

That is correct, everything is handled by Home Assistant automations.
Probably you have beta5 installed which gives a problem with reaching the roof of api calls per week, there is several issues related to that and error 429 here on git. do a downgrade and remove and create a new api key and secret so the counter resets. For me the integration is rock solid and have been for several years now.
I have everything handled by Home Assistant with a few conditions like no rain, being home, sun is up and so on, could'nt be more happy with how everything works. :)

[grm]

The beta 5 seema to have issues indeed, i ll try to revert the code to beta 4 today Le dim. 15 juin 2025, 11:31, Jimmy ***@***.***> a écrit :

…

*sabbatho* left a comment (py-smart-gardena/hass-gardena-smart-system#274) <#274 (comment)> That is correct, everything is handled by Home Assistant automations. Probably you have beta5 installed which gives a problem with reaching the roof of api calls per week, there is several issues related to that and error 429 here on git. do a downgrade and remove and create a new api key and secret so the counter resets. For me the integration is rock solid and have been for several years now. I have everything handled by Home Assistant with a few conditions like no rain, being home, sun is up and so on, could'nt be more happy with how everything works. :) — Reply to this email directly, view it on GitHub <#274 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAARGI3OLSWXNQ5UWB7U33T3DU4QDAVCNFSM6AAAAAB63N4V6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZTGYYTOMBTHA> . You are receiving this because you are subscribed to this thread.Message ID: <py-smart-gardena/hass-gardena-smart-system/issues/274/2973617038@ github.com>

[tomasenskede]

Which is the latest stable version?

[tomasenskede]

I’ve set up an automation using the following controls:
• To start the mower, I use: button.shaun_start_override
• To set the number of minutes it should run, I set this as duration in the automation
• And if I want to stop it manually, I use: button.shaun_return_to_dock

Are these the same controls you’re using?

In addition to that, I also monitor:
• sensor.shaun_battery_level
• binary_sensor.gardena_smart_system_connection
• binary_sensor.uptimekuma_gardena_smartsystem_gateway

Let me know if you’re using any other entities or commands I might have missed!

[sabbatho]

To start i use:
- action: gardena_smart_system.start_override metadata: {} data: duration: 10800 target: entity_id: lawn_mower.sileno
To stop i use:
- action: lawn_mower.pause metadata: {} data: {} target: entity_id: lawn_mower.sileno

I monitor battery aswell.
I have no other controls for the start and stop of the mower.
There are a few conditions in my start automation thou, like sun elevation, temperature, weather and if we are home.
Nothing else.
I do not use return to dock, because i wan't any schedule that might be there to be overriden, thats why i use lawn_mower.pause
The Gardena smart system connection is used to restart home assistant if it is unavailable, that usually works for me.

[tomasenskede]

When the battery reaches 60%, the mower returns to charge — but once it's fully charged, it doesn’t resume mowing.

Do I need to manage this with automations?
I was under the impression that the mower would continue the cycle of mowing → charging → mowing until it was manually stopped.

[sabbatho]

I might over complicate this but it works for me :)
For me it is not continuing because i choose it that way.
Here is my whole "start" automation:

`
triggers:

• trigger: time
  at: input_datetime.sileno_start
• trigger: state
  entity_id: input_boolean.bad_weather
  to: "off"
• trigger: state
  entity_id: input_boolean.sileno_override
  to: "off"
• trigger: numeric_state
  entity_id:
  • sensor.sileno_battery_level
    above: 99
• trigger: numeric_state
  entity_id: sensor.ute
  above: 8
• trigger: numeric_state
  entity_id:
  • sensor.sun_elevation
    above: 7
• trigger: state
  entity_id: person.him
  to: home
• trigger: state
  entity_id: person.her
  to: home
  conditions:
• condition: time
  after: input_datetime.sileno_start
  before: input_datetime.sileno_stop
• condition: state
  entity_id: input_boolean.bad_weather
  state: "off"
• condition: numeric_state
  entity_id: sensor.sileno_battery_level
  above: 98
• condition: state
  entity_id: input_boolean.sileno_override
  state: "off"
• condition: numeric_state
  entity_id: sensor.ute
  above: 8
• condition: numeric_state
  entity_id: sensor.senast_det_kom_nederbord
  below: 14
• condition: numeric_state
  entity_id: sensor.sun_elevation
  above: 5
• condition: or
  conditions:
  • condition: state
    entity_id: person.him
    state: home
  • condition: state
    entity_id: person.her
    state: home
    actions:
• action: gardena_smart_system.start_override
  metadata: {}
  data:
  duration: 10800
  target:
  entity_id: lawn_mower.sileno
  `

Edit: not sure why the code does not format even when i use the code, thing

[tomasenskede]

Surprisingly, it started again after being docked for 1 hour and 43 minutes... any idea why?

You automation looks interesting, I will have a look... how to you maintine the schedule? when to starta and stop?

condition: time
after: input_datetime.sileno_start 
before: input_datetime.sileno_stop

Are these input_datetime values calculated dynamically?
And if so, what are they based on?

[sabbatho]

those two input_datetime is helpers where i can choose easily in a card how i want the start and stop.
no calculations, just manual input.

That it started after 1h and 43min seems strange, depending on how your automation looks like?

[tomasenskede]

those two input_datetime is helpers where i can choose easily in a card how i want the start and stop.
no calculations, just manual input.

So you only have the times set, like start at 08:00 and stop at 10:00 each day—so it runs like that every day?

[sabbatho]

Exactly, nothing more complex with those two :)

[tomasenskede]

I thought this would work...

`actions:

• target:
  entity_id: button.shaun_start_override
  action: button.press
  data: {}
• delay:
  minutes: "{{ states('sensor.mower_run_time') | int }}"
• target:
  entity_id: button.shaun_return_to_dock
  action: button.press
  data: {}`

But my mower might not work like expected...

[sabbatho]

so those are automation actions?
what are those button.press you are using? think those might be the problem?