![opensprinkler tutorial opensprinkler tutorial](https://rayshobby.net/wordpress/wp-content/uploads/2013/07/IMG_0008.jpg)
This is just in case OSPi goes haywire and does not turn off as scheduled or someone makes a mistake of turning the sprinklers on for too long. Looking for a relay to turn the pump on and off I decided to go with an off delay relay as an extra safety that will automatically turn off after the selected period of time. I disabled the integrated card and configured the wpa_nf to connect to the dedicated WiFi extender AP as a priority. After checking compatibility lists and reviews for RPi compatible USB WiFi adapters I went with Edimax EW-7811UN. The built in WiFi on RPi would not work even half of the required distance and was simply horrendous. Assembling the OSPi was also not problematic, other than drilling some holes into the supplied enclosure for the USB cable and WiFi adapter. Installing raspbian and OSPi firmware was easy with no problems encountered. I ended up using the official RPi charger and the 24VAC charger at the same time. This was confirmed while testing where I saw dmesg errors about voltage not being sufficient and RPi rebooting endlessly. It is mentioned in OpenSprinkler documentation that a separate power supply for RPi is recommended. OpenSprinkler offers fully assembled systems but I decided to go the DYI route using my own RPi and just buying the OSPi hat.įinding a 24VAC power supply with EU plug was quite a challenge, the listed model from Orbit was one of the rare ones I could find online (on Amazon). Pump that drives the water must be turned on automatically with each zone valve.Each zone must be turned on separately due to the pressure requirement for the sprinklers to work.Three separate zones around the house, max 7 sprinklers per zone.In the end, programming the sequences myself and trying to make a decent UI would be just too much work for a small pet project so I went with a ready solution.
#Opensprinkler tutorial android
OpenSprinkler seemed to have everything I needed, a RPi hat with all the correct electrical outputs and an open source firmware and android app I could modify myself if needed. I was also not quite ready diving deep into embedded programming and OpenHAB programming model.
#Opensprinkler tutorial code
The initial plan was to go with plain RPi, OpenHAB and some GPIO code driving the sprinkler valves but the problem was creating a useful UI to control the system since OpenHAB is too clunky and generic looking. Ps: at this moment I have activated a VPN within my router, Fritzbox, so I do not open any port on domoticz and go thru it.I wanted to automate the watering system at home preferably using open-source and DIY systems.
![opensprinkler tutorial opensprinkler tutorial](https://i.ytimg.com/vi/m5O_xZdhgfs/maxresdefault.jpg)
├─xxx nginx: master process /usr/sbin/nginx -g daemon on master_p.įirst question is if from now on I have to go thru nginx also from my internal network doing something on the computers and tablet that will always remain home.Īnd, main thing is what I have to do and how on tablet/smartphone/Computers I will use externally. Process: xxx ExecStartPre=/usr/sbin/nginx -t -q -g daemon on master_process on (code=exited, status=0/SUCCESS) Process: xxx ExecStart=/usr/sbin/nginx -g daemon on master_process on (code=exited, status=0/SUCCESS) Loaded: loaded (/lib/systemd/system/rvice enabled)Īctive: active (running) since Wed 12:48:09 CEST 11min ago
![opensprinkler tutorial opensprinkler tutorial](https://rayshobby.net/blog/wp-content/uploads/2011/12/img-17.jpg)
guess what you cant do when the system time is set to zero, well before your cert was issued. ProTip: Get a battery backed up RTC if you setup x509 on a Pi. then it just took a few lines of code to get Domoticz to accept a x509 commonName for credentials. I've been using x509 for a couple years like this, I decided to add a shared tablet to the house I wanted to lock it down so it could not access protected switches/configs. all configuration is done in nginx really. The next stable release will simply detect when nginx's x509 token and associate it with any matching users. then you can still enable the built in auth and do it after providing a cert, still works just not automatically. Until the next stable (coming soon I believe) you can just disable domoticz auth and rely on Nginx, unless you really need the user accounts. all that does is associate certificates with user accounts. You can enable x509 in the current stable, the only thing thats been added since then is SSO. What configuration parameters? There are none. Thanks for the feedback, Ive updated that screenshot in the Wiki (force refresh) so people use the https_server template.