ESPHome Irrigation controller with display
ฝัง
- เผยแพร่เมื่อ 6 มิ.ย. 2024
- I am revisiting some parts of my Home Assistant automation kit I did over the last 5 years that are becoming obsolete and re-factoring them to bring them up with the current state of development.
Today, I will revisit the irrigation controller made of Sonoff 4ch Pro with ITEAD color display. This is quite a popular project on the internet. And I am not going to change the solution architecture overall, the hardware will stay, and it will still run ESPHome. But I will update that one to use the ESPHome native sprinkler controller - and I will show you 3 different flavors of this.
Project on GitHub: github.com/bruxy70/Irrigation...
ESPHome Sprinkler controller: www.esphome.io/components/spr...
Join us on my Discord channel / discord
00:00 - intro
01:10 - sprinkler controller
03:47 - configuration - before
04:53 - basic configuration
10:13 - more advanced configuration
13:16 - summary - what has changed
15:05 - my actual config
22:27 - outro - วิทยาศาสตร์และเทคโนโลยี
Nice. I have a sonoff 4ch pro running my irrigation. I'll come back to this a little later. Thanks for the video.
I looked at the ESP_Home sprinkler features. I can do far more advanced features (like rain in the future OR rain in the past, to stop over watering the grass) in a much simpler approach using Node-Red. Much more visual and easy to follow. But as we all say in the IT industry, As long as it passes the functional requirements there is no wrong or right way to approach, They are equally good. Keep the good videos coming.
I also do check rain and weather forecast and whether it run manually, to block the program. I do that in HA (could be node red). But I would not control the actual valve control from there. If you loose connection, or restart HA, you might have the irrigation running for days. That would definitely overeater .. :)
Nice. I prefer opensprinkler and opensprinkler integration with HA. Opensprinkler is running on a docker and valves are controlder by wemos d1 mini (8266). Communication is done via mqtt. Sprinklers programs can be controlled via android app (if needed). Scheduled programs are possible too. Much less configration. Opensprinkler also supports master valve. Best part is that opensprinkler can "read" forcast and stop watering if rain is predicted.
My setup consists of a relay board with 8 relays, an ESP32, and a buck converter to power the ESP32. I used the scripts and scheduling in ESPHome to run the sprinklers. Were I live we have restrictions on what days you can water that vary by season. On September 1st my system automatically switched to three days a week from six days a week. I used one of the relays to shut off the 24VAC going to the relay board so Home Assistant can shut off the sprinklers on the rare occasions that we get rain in Las Vegas. The system is in my garage and I didn't see any need for buttons or a display since I have several other ways to control it.
Hello VegasWayne, you have always comment about someone else project... but I can't see yours. Be helpful to put some code or pictures of your setup for someone to help as I straggling to program mine.
I am on mains supply for water here, so like you I use the "pump control" to switch a master solenoid valve.
I have been interested in updating my irrigation system, the ESPHome control looks like it will be pretty amazing for that. I find ESPHome devices rock solid and reliable, so I think this is a brilliant option.
Are all the graphics for the Nextion Display in ESPHome, or did you create all the Nextion icons separately?
The graphics is basically created in Nextion HMI editor. It is mostly a background image, overlayed with controls such as buttons (that change on touch - also done in HMI editor) or text values. So the only thing ESPHome does is to set value properties. It does not draw any graphics in this case.
I need to do some ReFactoring - 70% of my kit is still on Domoticz with Tasmota- Newer stuff is on HA with mostly ahelly
a question about the nextion display. I made a controller with a esp32, with 3 shift registers, to control 12 relays, and led's to show active valve, and controlling the power supply..... all works great, i used your code and copy pasted things i need....and now want to add the display,i cant use your project completely due i have 3.5inc display, ....my question i looked at your nextion project, but you have 2 backgrounds for weather, and also the controls... but there are no pages...? , and i dont see any buttons on the zones? can you maybe point me in some direction where i can look to figure it out .....thank you for the great content you sharing!!
In the Nextion editor, just add a dual-state-button. I then have 2 copies of the background, normal and inverted. And you configure them as picc and picc2 in the button. And set it to take an image crop. You can nicely debug that in the Nextion editor. Then in ESPHome, just configure it as a switch, platform nextion, with the component name. Then you can just work with it as with a regular switch. As for the weather, I have two pages on my actual controller, I removed that in the version uploaded to GitHub. So I perhaps forgot to remove the background image?
Excellent work! I began migrating the heating control to ESP (underfloor heating, boiler, solenoids). My ESP devices' status changes to "Became unavailable" a few times per hour (WiFi Signal -58 dBm). On restart, all relays turn off and then return to their previous state. How many "Became unavailable" statuses do you have on a daily basis?
I don't😊 If you mean in the ESPHome dashboard, you can use status_use_ping in your add-on configuration.
May need to check the GPIO's you are using for your relay control. Some should not be used as they have special functions. -58dBm is not bad for WiFi, but if there is a lot of 2.4GHz interference, this could cause them to dorp off a lot. You may also check your sketch / ESPHome code to see if you have any watchdog functions enabled. Alos, if you enable Bluetooth Proxy or BLE Scanning on the ESP's this could cause drop off as Bluetooth is time shared with the WiFi.
I have not personally had any ESPHome devices go unavailable on my network, except when there is an actual power failure, so I can only guess at the common things.
@@bruxy70 I added 'status_use_ping' in HA add-on configuration. I have in HA > Logbook > [esphome] entity more than 100 "became unavailable" statuses. On router logs (UDM) Event Time
has connected to with SSID "CojitaNoT" on channel 6 2:06 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 4.59 KB, last ) 2:06 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:06 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 23.4 KB, last ) 2:06 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:05 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 9.42 KB, last ) 2:05 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:05 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 9.74 KB, last ) 2:05 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:05 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 8.41 KB, last ) 2:05 pm 09/12/2022
has connected with SSID "CojitaNoT" on channel 6 2:04 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 8.12 KB, last ) 2:04 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:04 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 0 B, last ) 2:04 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:04 pm 09/12/2022
disconnected from "CojitaNoT" (0m connected, 20.2 KB, last ) 2:04 pm 09/12/2022
has connected to with SSID "CojitaNoT" on channel 6 2:04 pm 09/12/2022
disconnected from "CojitaNoT" (1m connected, 27.6 KB, last ) 2:04 pm 09/12/2022
İ think soil moisture integrated sensor irrigation will be good for this project. Cause everyday you dont need irrigation i think.
Exactly. I do not use moisture, but info from the rain sensor, together with precipitation forecast and info if I run the irrigating manually last 24 hours - to block that. I have really no good place to put the moisture sensor. But definitely great idea!
All this coding and scripting is so much work and too hard to understand unless you fully learn the language. No time for that! Just use Node Red, much easier and quicker!
Different thing. Node Red is a home automation platform that can talk to different devices and tell them what to do. ESP Home is used to program these devices to be able to interface with the physical world and talk back to these automation platforms, such as Node Red. The alternative to ESP Home would be Arduino or micro python. And I'd argue that Esp home is simpler than these (in fact, the first version was in Arduino).
But yes, it is much easier to buy such device somewhere, like in Home Depot. My video is for people that want to make their own.
@bruxy70 are you not doing this in yaml files though? I've stopped trying doing yaml ages ago. I just put Tasmota on all devices and use node red. Would be interesting to try ESP home though.
@@TheFlyingKiwiNZ Tasmota would be an option, but then you do all controls remotely. And for things irrigation, or security system, I'd keep certain level of autonomy. I learned my lesson (when my neighbour called me on my vacation, that the water is pouring for the whole day and whole garden and his entrance is under water - it was not cheap. I also find ESP Home much more predictable than relying on MQTT.
Plus I have the display with local control, that frankly use most of the time. Tasmota does not do that.
@bruxy70 ok so all this coding is on the device not in Home Assistant is what you are saying? Probably too advanced for me unless I can simply copy paste what you have done
@@TheFlyingKiwiNZ Yes, correct, it does not run on HA.