![opensprinkler pi login opensprinkler pi login](https://opensprinkler.com/wp-content/uploads/2015/04/rftoy3.0-1-300x300.png)
Initially I had considered going the OpenSprinkler route, but at the end I decided to save the money or effort and go my tried and tested route. I’d thought I’d add my two penneth worth. I have also started integrating the TTS abilities. I have connected my three aircon units via ESP with infrared LEDs, with an additional RF output to control some power outlets - you guessed it, all via MQTT. I also have my garage door hooked up via a 5v relay and a reed switch to detect state, controlled via MQTT. I will leave this here as vindication of my current thought process! When the “pool level too low” state trips, I could ‘dose’ the pool with a couple of hundred litres to top up. This last* one would combine with my pool water height sensor. Litres used total / litres used per zone.
#Opensprinkler pi login manual
Alerts of water flow outside of a trigger, schedule or manual switching (leak alert).It needs a nice water tight project case, and I could put in a impulse based flow meter at the tap end of the irrigation. Needs to show the success/fail state of irrigation attemptsīut that’s it.
![opensprinkler pi login opensprinkler pi login](https://rayshobby.net/wordpress/wp-content/uploads/2015/01/IMG_0585.jpg)
![opensprinkler pi login opensprinkler pi login](https://rayshobby.net/wordpress/wp-content/uploads/2015/01/IMG_0584.jpg)
![opensprinkler pi login opensprinkler pi login](https://i.ytimg.com/vi/EAsetka1xB4/maxresdefault.jpg)
Upon a successful irrigation the ESP sends a “success” with a “total time watered” back to MQTT.The irrigate time/length means the ESP will count down and switch off of it’s own accord in the event that the ESP can’t communicate with MQTT for an “stop” type message The message sent to the topic has the region name of the garden area to irrigate and the total time to irrigate (in minutes).The ESP boots, connects to wifi and subscribes to an ‘irrigation’ topic on the MQTT server.Each channel is connected in a “normally open” state - so that on a power off state at the controller all relays will be off - it won’t irrigate if the power fails.I have an 8 channel relay board that have hooked to an ESP8266: I can’t see any blockers at this stage that don’t begin with a dollar sign. Well - I’ve racked up some experience on a few things and do feel a lot more comfortable with HASS, Arduino and MQTT. I think I would have some scheduled scripts that have a “start” button in HA somewhere, some over-ride “all stop” command, maybe some weather logic (eg, rain forecast in the next 8 hours, rain has fallen in the last 8 hours, temp forecast over 27c etc) that kicks off extra cycles. Of course the published start events would come from HA - but here is where my details peter out. I’m also thinking of adding a flow meter - so that I will be able to count the litres used, and some alerts if a flow is happening that contravenes the current known/intended state. It will listen for over-riding stop commands. The controller will publish the successful start of a zone and its finish. I plan to have the ESP8266 controller hook up to my wifi and listen for MQTT commands that detail the start, duration and zone for irrigation. I think I’ll be able to control this via an 8 channel relay board and just a little ESP8266 NodeMCU. I’m planning on installing irrigation to 7 separate zones (a combination of vege patch, lawn, garden beds and decks). I’m not seeing much here on garden irrigation and this is something pretty important to me.