Sequencing and zones

[RTAeroHASS]

Hi i have an irrigation pump that i need enabled during the entire run. I'm not to sure where to insert the entity_id of the pump to have it switch on during the entire sequence

[rgc99]

It should be under the controller. When any of the zones are on, the controller will be on. Hint: If you have a delay between zones in your sequence then consider using preamble and or the postamble settings to avoid the irrigation pump turning off and on. The setting should be at least the longest delay. For example:

# Example configuration.yaml entry
irrigation_unlimited:
  controllers:
    preamble: '00:01' # Cover the delay between zones and prevent pump on/off
    entity_id: 'switch.my_irrigation_pump'
    zones:
      - entity_id: 'switch.my_valve1'
      - entity_id: 'switch.my_valve2
    sequences:
      - duration: '00:10' # Without preamble the pump will turn off
        delay: '00:01'
        schedules:
          - time: '06:00'
        zones:
          - zone_id: 1
          - zone_id: 2

[RTAeroHASS]

Thanks Robert, I will test it today.

…

On 15 Dec 2021, at 3:05 AM, Robert Cook ***@***.***> wrote:  It should be under the controller. When any of the zones are on, the controller will be on. Hint: If you have a delay between zones in your sequence then consider using preamble and or the postamble settings to avoid the irrigation pump turning off and on. The setting should be at least the longest delay. For example: # Example configuration.yaml entry irrigation_unlimited: controllers: preamble: '00:01' # Cover the delay between zones and prevent pump on/off entity_id: 'switch.my_irrigation_pump' zones: - entity_id: 'switch.my_valve1' - entity_id: 'switch.my_valve2 sequences: - duration: '00:10' # Without preamble the pump will turn off delay: '00:01' schedules: - time: '06:00' zones: - zone_id: 1 - zone_id: 2 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[RTAeroHASS]

Hi Robert I tested it with a Manual Run. The pump (switch_4) comes on but none of the zones activate, any idea what I’m doing wrong? irrigation_unlimited: controllers: - name: "Auto" preamble: '00:01' entity_id: 'switch.irrigation_switch_4' zones: - name: 'Front Trees' entity_id: 'switch.irrigation_switch_2' show: timeline: true - name: 'Front beds' entity_id: 'switch.irrigation_switch_1' show: timeline: true - name: 'Back Garden' entity_id: 'switch.irrigation_switch_3' show: timeline: true sequences: - name: ‘Auto Run' duration: '00:20' delay: '00:01' schedules: - name: 'Summer' time: sun: 'sunset' before: '00:30' weekday: [mon, wed, fri] month: [dec, jan, feb] duration: '00:40' - name: 'Winter' time: sun: 'sunset' before: '00:30' weekday: [sun] month: [jun, jul, aug] duration: '00:10' - name: 'Spring and Autumn' time: sun: 'sunset' before: '00:30' weekday: [mon, thu] month: [mar, apr, may, sep, oct, nov] zones: - zone_id: 1 - zone_id: 2 - zone_id: 3

…

On 15 Dec 2021, at 3:05 AM, Robert Cook ***@***.***> wrote: It should be under the controller. When any of the zones are on, the controller will be on. Hint: If you have a delay between zones in your sequence then consider using preamble and or the postamble settings to avoid the irrigation pump turning off and on. The setting should be at least the longest delay. For example: # Example configuration.yaml entry irrigation_unlimited: controllers: preamble: '00:01' # Cover the delay between zones and prevent pump on/off entity_id: 'switch.my_irrigation_pump' zones: - entity_id: 'switch.my_valve1' - entity_id: 'switch.my_valve2 sequences: - duration: '00:10' # Without preamble the pump will turn off delay: '00:01' schedules: - time: '06:00' zones: - zone_id: 1 - zone_id: 2 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANJZ2OUUWNSM6O73UIOWS23UQ7SW3ANCNFSM5KBCQDGA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[rgc99]

The log file should have an entry for the manual run call. Please post this. I am thinking if the call was for 1 second instead of 10 minutes you might get something like you describe.

[RTAeroHASS]

The manual run time of 1min was too short, I ran it for 10mibs and it worked perfectly

…

On 15 Dec 2021, at 11:08 PM, Robert Cook ***@***.***> wrote:  The log file should have an entry for the manual run call. Please post this. I am thinking if the call was for 1 second instead of 10 minutes you might get something like you describe. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[RTAeroHASS]

Hi Robert Im trying to set the sequence duration to a variable (input_datetime.irrigation_auto_runtime), but I get the following error in configuration validation: Invalid config for [irrigation_unlimited]: [value_template] is an invalid option for [irrigation_unlimited]. Check: irrigation_unlimited->irrigation_unlimited->controllers->0->sequences->0->duration->value_template. (See /config/configuration.yaml, line 65). Configuration.yaml code: sequences: - name: 'Auto Run' duration: value_template: "{{ states('input_datetime.irrigation_auto_runtime') }}" Fyi, ‘input_datetime.irrigation_auto_runtime is set to 00:30:00

…

On 15 Dec 2021, at 11:43 PM, Ralph Thomas ***@***.***> wrote: The manual run time of 1min was too short, I ran it for 10mibs and it worked perfectly > On 15 Dec 2021, at 11:08 PM, Robert Cook ***@***.***> wrote: > >  > > The log file should have an entry for the manual run call. Please post this. I am thinking if the call was for 1 second instead of 10 minutes you might get something like you describe. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANJZ2OXUA5UBOYLRHSOYILTURD7STANCNFSM5KBCQDGA>. > Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >

[rgc99]

This won't work. The config file is only used at startup or a reload so even if it were able to read the value from the input_datetime, changing it would not have any effect on the operation. The way to dynamically interact with the integration is via service calls. In this situation you would call the adjust_time service in an automation. When the input_datetime control changes an automation is triggered and a service call is made. Here is an example:

automation:
  - alias: Irrigation Unlimited Time Change
    trigger:
      - platform: homeassistant
        event: start
      - platform: state
        entity_id:
          - input_datetime.irrigation_auto_runtime
    action:
      service: irrigation_unlimited.adjust_time
      data:
        entity_id: binary_sensor.irrigation_unlimited_c1_m
        sequence_id: 1
        actual: >
          {{ states('input_datetime.irrigation_auto_runtime') }}

The above will trigger on HA startup or when the input_datetime control changes. Also take a look at the time-picker-card. You can get rid of the am/pm part to turn it from a time of day into a duration control. Note: The example has not been tested but the theory is sound.

[RTAeroHASS]

Brilliant, thanks Robert I will give it a try

…

On 08 Jan 2022, at 6:08 AM, Robert Cook ***@***.***> wrote:  This won't work. The config file is only used at startup or a reload so even if it were able to read the value from the input_datetime, changing it would not have any effect on the operation. The way to dynamically interact with the integration is via service calls. In this situation you would call the adjust_time service in an automation. When the input_datetime control changes an automation is triggered and a service call is made. Here is an example: automation: - alias: Irrigation Unlimited Time Change trigger: - platform: homeassistant event: start - platform: state entity_id: - input_datetime.irrigation_auto_runtime action: service: irrigation_unlimited.adjust_time data: entity_id: binary_sensor.irrigation_unlimited_c1_m sequence_id: 1 actual: > {{ states('input_datetime.irrigation_auto_runtime') }} The above will trigger on HA startup or when the input_datetime control changes. Also take a look at the time-picker-card. You can get rid of the am/pm part to turn it from a time of day into a duration control. Note: The example has not been tested but the theory is sound. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.

[rgc99]

Assume all good now. Closing issue.