I think you should add the initial state as suggested by @VikingBlod to avoid reboot loop
input_text:
irrigation_zone1_times:
name: Zone 1 Time Periods
initial: 01:00
irrigation_zone2_times:
name: Zone 2 Time Periods
initial: 01:00
irrigation_zone1_days:
name: Zone 1 Days of the Week
initial: Mon,Wed,Fri
irrigation_zone2_days:
name: Zone 2 Days of the Week
initial: Mon,Wed,Fri
EDIT: got it. I need to define once and the remove it to avoid issues with reboot
if I want to run a zone more than one time the same day, should I configure the time with the comma separator? (eg. what I did in zone 2)
In the ESP32 log I see this INFO Detected timezone 'CET' with UTC offset 1 and daylight savings time from 27 March 02:00:00 to 30 October 03:00:00, but on the scheduled time the zone doesn’t start. any idea on what I’m missing?
if i manually trig the switch (see Zone 1), sounds good
I understood the issue
when you replace the days name in the integration.h file to match your language, you have to put attention to the text specially to match the latest case (Today)
else if (day == "Tod") { //Today in English
because the substitution is taking only 3 char, you have to use only the first 3 char in your language
string day = time.substr(6,3).c_str(); //day text is added to original string
for English “Today” is “Tod”
// Converting days to week numbers, change text based on your Language
if (day == "Mon" || day == "mon" || day == "MON") {
next_wday = 2;
} else if (day == "Tue" || day == "tue" || day == "TUE") {
next_wday = 3;
} else if (day == "Wed" || day == "wed" || day == "WED") {
next_wday = 4;
} else if (day == "Thu" || day == "thu" || day == "THU") {
next_wday = 5;
} else if (day == "Fri" || day == "fri" || day == "FRI") {
next_wday = 6;
} else if (day == "Sat" || day == "sat" || day == "SAT") {
next_wday = 7;
} else if (day == "Sun" || day == "sun" || day == "SUN") {
next_wday = 1;
} else if (day == "Tod") { //Today in English
next_wday = time_wday;
}
HI @bremby Thank! I havent installed yet, i have to make a modification at pump shelter. I tested on my kitchen table everything was working but I dont remeber if I tested that specific function.
thanks for noticing this. Maybe because i am spanish speaker and in spanish today = “hoy”, just 3 letters so i didn’t have that problem when i modified irrigation.h
one to “suspend” the schedule (eg. you want to suspend the irrigation for a period of time, but you don’t want to clean the configurations or turn off the esp)
- platform: template
name: Irrigation Zone 1
id: irrigation_zone_1
icon: mdi:sprinkler-variant
lambda: return id(irrigation_channel_1).state;
optimistic: true
turn_on_action:
# Turn on if not disabled and not running
if:
condition:
and:
- lambda: return id(irrigation_zone_1_duration) > 0;
- binary_sensor.is_off: ui_stop_irrigation_automation
then:
- switch.turn_on: irrigation_channel_1
turn_off_action:
- switch.turn_off: irrigation_channel_1
let me know what you think or if you have made additional configurations or have any suggestions
Hey all, thinking about giving this project a try. I notice the device used for switching is a Sonoff 4 Channel Pro R2. I don’t seem to be able to find one and the link in the blog article says it is out of stock.
Does anyone know if a Sonoff 4 Channel Pro R3 would work or is this something different again?
Thank you for letting me know about the outdated Sonoff link (I am updating the link on my post). The R3 looks to be a direct replacement for the R2, so it should work the same.
So I have everything configured but I’m running into an issue.
I have it scheduled for Saturday @05:53 and Monday @11:00. The next watering for zone 1 should say Monday @11:00 since the watering for Saturday has already ran but it’s showing Saturday @11:00.
Hi! @stinger that’s because the schedule is for every day, you can’t choose the time for each days… So, if you choose Saturday and Monday, and then you set it to run at 5 am and 11am, it will run those two days at those two hours