#Blueprint automation isn't adopting the runtime of my irrigation

1 messages · Page 1 of 1 (latest)

blazing beacon Sep 24, 2025, 11:47 PM

I wrote this blueprint and it works perfectly other than that the irrigation lasts only 5 minutes, not what I enter as the length. I wonder if I did something wrong or if it's something else. It is a b-hyve hub, in case that makes a difference. Thanks for any help!

  name: Watering Blueprint
  description: Turn on watering based on time
  domain: automation
  input:
    time_start:
      name: Time to start
      description: The time the watering will start
      selector:
        time:
    weekday:
      name: Day of the week to start watering
      default: [mon, tue, wed, thu, fri, sat, sun]
      selector:
        select:
          options:
          - label: Monday
            value: mon
          - label: Tuesday
            value: tue
          - label: Wednesday
            value: wed
          - label: Thursday
            value: thu
          - label: Friday
            value: fri
          - label: Saturday
            value: sat
          - label: Sunday
            value: sun
          custom_value: false
          multiple: true
    target:
      name: Section to water
      description: Select the section that will be watered
      selector:
        entity:
          device_class: switch
    minutes:
      name: Minutes
      description: Amount of Minutes to be watering
      selector:
        number:
          mode: slider
          min: 0
          max: 180
          unit_of_measurement: minutes

mode: single

triggers:
  - platform: time
    at: !input time_start
conditions:
  - condition: time
    weekday: !input weekday
  - condition: state
    entity_id: input_boolean.pause_watering
    state: "off"
actions:
  - service: switch.turn_on
    entity_id: !input target
  - delay:
      minutes: !input minutes
  - service: switch.turn_off
    entity_id: !input target

quiet temple Sep 25, 2025, 2:43 PM

What does the log of the selected target say why it turned off? And what does the automation trace say?

blazing beacon Sep 25, 2025, 4:46 PM

Thanks for responding!
I had to make a new automation because the logs are retained for only 24 hours I guess, which is weird. Anyways, I looked at boththe log and the automation trace of a new test automation I made:
The log entries are:

10:40:09 - 1 minute ago
BHyve changed to auto
10:40:09 - 1 minute ago
BHyve changed to manual
10:35:04 - 6 minutes ago
Sprinklers turned on triggered by automation
NEW AUTOMATION TEST triggered by time
10:35:03 - 6 minutes ago```
The trace is:
```Triggered by the time at September 25, 2025 at 10:35:00
Test If the day is Thursday
Test If Watering Pause is Off
Perform action 'Switch: Turn on'
Delay for 10:00
4 seconds later
(switch.sprinklers_zone) turned on
Still running```
As you can guess by the "still running" I looked at the trace after the 5 minutes, when it shut off, but before the 10 minutes of my test automation, which looks like this:
```alias: New automation TEST
description: ""
use_blueprint:
  path: watering/test.yaml
  input:
    time_start: "10:35:00"
    weekday:
      - thu
    target: switch.sprinklers_zone
    minutes: 10

I hope this is of some help. Thank you!!!

quiet temple Sep 25, 2025, 6:01 PM

As the turn off has no reason behind it (like the turn on) it is not done by HA. HA just received the off status from the device.

And for next time, traces can be downloaded. That will contain way more info 🙂

blazing beacon Sep 26, 2025, 7:34 PM

OK, so I got it fixed. I had to change the command to the bhyve. For some reason it turns itself off after 5 minutes if you only use the switch.turn_on. But if using bhyve.start_watering it works with the time added, so this script works fine (only the actions-part changed):

blueprint:
  name: Watering Blueprint
  description: Turn on watering based on time
  domain: automation
  input:
    time_start:
      name: Time to start
      description: The time the watering will start
      selector:
        time:
    weekday:
      name: Day of the week to start watering
      default: [mon, tue, wed, thu, fri, sat, sun]
      selector:
        select:
          options:
          - label: Monday
            value: mon
          - label: Tuesday
            value: tue
          - label: Wednesday
            value: wed
          - label: Thursday
            value: thu
          - label: Friday
            value: fri
          - label: Saturday
            value: sat
          - label: Sunday
            value: sun
          custom_value: false
          multiple: true
    target:
      name: Section to water
      description: Select the section that will be watered
      selector:
        entity:
          device_class: switch
    minutes:
      name: Minutes
      description: Amount of Minutes to be watering
      selector:
        number:
          mode: slider
          min: 0
          max: 180
          unit_of_measurement: minutes

mode: single

triggers:
  - platform: time
    at: !input time_start
conditions:
  - condition: time
    weekday: !input weekday
  - condition: state
    entity_id: input_boolean.pause_watering
    state: "off"
actions:
  - service: bhyve.start_watering
    data:
      entity_id: !input target
      minutes: !input minutes```

hazy jungle Sep 27, 2025, 8:10 PM

My zigbee water valve has an auto-shut-off so that if automation fails after the thing is started, it doesn't flood the garden.
Is yours set to 6 minutes, by any chance?