Eco mode not working properly

[snetekombinerke]

Hi,
I'm experiencing some issues with eco mode, I have setup watering time 7 min, wait time 5 min with 7 repeats. The program is ended after 2 times of watering for 5 min.

Can someone else test eco watering mode.

config_entry-irrigationprogram-01JTKJ4CPNJFDR3RYXVC9PGMA3.json

Thank you for your time.
Best regards

[petergridge]

Hi I have tested this and I am getting the correct number of iterations of the watering cycle.

Are you seeing and notifications or errors in the log file?

[snetekombinerke]

I don˙t get any notifications also nothing in log.
What else can I check?

[petergridge]

I can't see anything in the code that would fail silently like this, do you have any other automations that may be stopping the underlying valve switch in HA?

The program will stop if the switch is turned off outside of the irrigation custom control.

[snetekombinerke]

Hi,

now I found this in log

in esphom device is nothing unusual, no disconect or else

any thoughts?

[petergridge]

This is a warning message, while the program is running it is monitoring the state of the switch, if the switch does not return the expected state for on (True) it will write out this message, if it continues for 5 cycles (seconds) the switch will turn off. Resulting in the symptoms you have experienced.

[snetekombinerke]

I do not know why the switch would be unavailable or in different state then turned on. There is nothing in log, it has stable wifi connection.

I have tested different setting on wait time.
If I set 10 min then always there is a problem.
I have tested the wait time settings with 4 minute wait then it was working as expected.

Can you test with different wait time?

[petergridge]

Can you share your ESPhome yaml definition. My config for the irrigation controllercan be found here esp irrigation

I am adding an option to the advanced setting to disable the termination of the program when a latency issue is detected. This will be enabled by default.

The warning message will remain so users can check that they are confident that their systems are stable.

Events are created when the program detects that a switch has not behaved as expected so users have control of any actions that may be need in their own environment.

I am testing the changes at the moment and expect to have the update soon

[snetekombinerke]

I use simple switch to control the valve

switch:

• platform: gpio
  name: "VENTIL"
  id: ventil
  pin:
  number: D7
  icon: "mdi:sprinkler"
  on_turn_on:
  • output.turn_on: led_indikator
  • delay: 900s
  • switch.turn_off: ventil
    on_turn_off:
  • output.turn_off: led_indikator

[petergridge]

• Remove strict validation and termination when latency issues are detected.
  • remove the termination of zones if not reporting the correct status, i.e. reporting a state of on when it is expected to be off.
    • User can control actions by using the events fired to initiate automations to perform the actions required locally.
    • This functionality has been causing issues with some implementations.
  • Attempts to align the state by continuing to send an Off or On command for several cycles
  • Log a debug message when this occurs
  • Report and handle failure when a zone is renamed or removed, but the program not updated