Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm using the Irrigation-V5 integration, but the irrigation program is not starting automatically, even though all conditions seem correct.
Current Setup:
time.tempo_di_inizio → Start time is set to 15:40:00
switch.abilita_il_programma → Enable program switch is on
switch.abilita_la_zona → Enable zone switch is on
number.tempo_di_irrigazione → Watering time is set to a value > 0
number.tempo_di_attesa → Delay time is set > 0
number.ripetizione → Repetition count is ≥ 1
select.frequenza → Watering frequency is set to daily
switch.ignora_i_sensori → Ignore sensors switch is on
switch.irrigazione_outlet → This is the zone switch (off by default)
binary_sensor.irrigazione_stato → Water source status is on
binary_sensor.pioggia_sophisticated → Rain sensor, not blocking due to ignora_i_sensori
sensor.prossima_irrigazione → Next irrigation sensor stays unknown
As a result, the irrigation never starts
I found this error in the logs:
TypeError: '>' not supported between instances of 'NoneType' and 'datetime.datetime'
This happens in zone.py because the integration compares:
self.next_run.native_value > dt_util.as_local(dt_util.now())
But self.next_run.native_value is None, which causes the comparison to fail.
The integration fails to calculate next_run, which causes:
sensor.prossima_irrigazione to remain unknown
and the irrigation program never activates automatically
It seems the issue is related to start_time not being recognized properly as a valid input_datetime, or not being initialized.
Let me know if this is a known issue or if there’s a proper fix/workaround to ensure next_run is calculated and triggers the program.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions