[Pat]

Hey that page looks familiar 🙂

Perfect, I can host my own fork of this. How do I point OSPi to my hosted weather aggregator instead of OpenThings? Edit: found it. ospi/su.

Edit: There’s even support for weewx? Even better!

[Pat]

My last reply didn’t go through it looks like? Must be stuck in a moderation queue somewhere.

It suggested that the documentation should be updated since it currently says it still supports Wunderground, and since I have a PWS I also have a wunderground key. Would be great to use that hyperlocal info since my PWS is in my backyard.

[Pat]

@samer I hope it works out. As mentioned I moved all my FOSS stuff to Dark Sky and it was quick and (mostly) painless. And with 1,000 free calls a day, that’s *almost* 1 call a minute (ok maybe 1 call every 2 minutes). Plenty of wiggle room though depending on how often it’s used per user/station

[Pat]

Just to throw another option into the fold, you can check out Dark Sky API for integration. Users get 1000 API calls a day for free. Should be more than enough for OpenSprinkler’s needs

https://darksky.net/dev

I just moved everything I could to Dark Sky and the documentation was great and very similar to wunderground (with obvious changes since it’s a different platform).

[Pat]

Thanks. I forgot I had a Raspberry Pi B (not B+), and it’s working just fine even with the WiFi.

Good to go, thanks again

[Pat]

The github link in the first post has very detailed instructions. https://github.com/drsprite/OpenSprinkler-Push-Notifications

Further, OpenSprinkler has something built in, too. https://openthings.freshdesk.com/support/solutions/articles/5000716372-creating-an-ifttt-key-and-applet

I can’t speak to the level of detail that the built in function has compared to the script we’ve been running for the last couple of years.

[Pat]

Just to close the loop on this thread. The problem was not with OpenSprinkler, but instead with my outdoor wiring. I discovered my irrigation installers did not use waterproof wire nuts on any connections. All outdoor wire connections were corroded. $10 on waterproof wire nuts and an hour of stripping back new clean wire and it’s back up and running.

Thanks for the troubleshooting Ray!

[Pat]

+1 here again, too. Had a situation yesterday where the neighbors stopped by and I turned the program off to be nice. Would have been great to pause it, chat with them, then resume so I didn’t miss total time per station (without thinking too hard)

[Pat]

I agree it’s strange behavior. Everything else being port forwarded to the Pi is going fine. Even port 80. It’s just OSPi on 8080 that’s not playing well with the port forward anymore.

I’ll roll back and see how it goes. Looks like commit 29f3b65 is 2.1.5. I’ll roll back to that and play around with some of it to see if I can nail it down.

[Pat]

Looking forward to it!

[Pat]

Thanks Samer! I’m happy you were able to fix it.

Do I need to do a pull from github or will it automatically be applied?

[Pat]

@Andreas, Since you don’t have a Raspberry Pi, I put together a script which could help you out.

You didn’t specify if you were on Windows or Mac or Linux, so I put together a PowerShell script that’ll run on Windows.

You will need to run it using Scheduled Tasks. Run it once a day (or twice a day, whatever you want). It will check your external IP address and log it to c:\ip.txt. When the script runs again, it’ll compare your external IP to the saved text file IP. If they do not match, then your IP has changed.

If it detects that your IP changed, it’ll send you an email.

Requirements:
1. Windows
2. A GMail account to send the email from. Unless you have your own SMTP server, then that can be used instead.

Simply copy and paste the script to your computer and run it with PowerShell (e.g. from command line or Scheduled Task: powershell.exe & “c:\Check_External_IP.ps1”).

Here’s a link to the script: https://gist.github.com/drsprite/6b172d1698b42edcef5c

Hope this helps!

[Pat]

Yep, my OpenSprinkler is running on a Pi B+

[Pat]

For those tracking the script for updates, I just updated it again with some bugfixes to the rain sensor and the email error alerting.

[Pat]

@nystrom I just pushed to Github an update for part of your request #2 – station name from the OSPi (instead of my old “Zone #” notification).

[Pat]

Some good thoughts. I’ll have to see how to include it – but if you’ve been tinkering already and have the code good to go (and working), feel free to do a pull request on github and I can review it and easily merge it in with the script!

[Pat]

Works great! Just pushed it up to github, as well as updated the README to include instructions on how to setup the maker channel and add a new recipe for the event.

https://github.com/drsprite/OpenSprinkler-Push-Notifications

The beauty with IFTTT is you can do whatever you want with this. Doesn’t have to be a push notification. Could be an SMS, an email. So many options! 🙂

Here’s the quick push notification recipe I setup:

[Pat]

Love IFTTT. Great addition. I’ll add it in! Thanks!

[Pat]

Glad it’s working! Just curious what the fix was?

I’ll leave those troubleshooting tips up just in case someone needs it in the future.

[Pat]

@jchiar Interesting. I’m not seeing this error, and the only way I could replicate it was by messing up the YAML spacing. Once I did that, I see that exact error. I’ve learned that YAML can be picky about it’s spacing.

For YAML, the first sub-item is 2 spaces, then 2nd subitem is 4 spaces from the left margin.

There’s 3 things we can try:
1) Re-download the config.yaml from github. This time we can use wget to get an exact copy.
Save a copy of your existing config.yaml and run wget https://raw.githubusercontent.com/drsprite/OpenSprinkler-Push-Notifications/master/config.yaml from inside /home/pi

2) Run this on the command line. It should tell you which line and column is invalid.
python -c "import yaml; yaml.load( open('config.yaml', 'r'), Loader=yaml.Loader )"

For example, if there is an extra space in front of “port”, it’ll return expected <block end>, but found '<block mapping start>' in "config.yaml", line 3, column 4

3) Lastly, paste your config file into this site to validate it. http://www.yamllint.com/
(You should remove your API keys just in case they track those kinds of things).

It should tell you whether it’s OK or if it failed, and where it failed.

[Pat]

I just pushed to github a pretty big update for this little script.

I re-wrote the sprinkler station check so now you can get notifications when the zone starts and stops. I added the water level notification that @jchiar was looking for.

I added more options to the config file, too. You can now select which notification you want to receive, as well as change the notification message from the config file.

Added more syslog logging – never know when it’s needed.

Let me know if you find any bugs!

https://github.com/drsprite/OpenSprinkler-Push-Notifications

[Pat]

Great md5 tip, I’ll add it to the README. I’ll also fix my typo, thanks for spotting that!

With the last update I started to think about “Stop” notifications and put a variable in there as a placeholder to get my mind thinking. I think if I set a variable for the current station that’s on, then if a new station comes on, that means the old one is off and send a notification.

Something I’m thinking about.

[Pat]

I just pushed up to github a rather large update. Broke the script out into a config file, which will make future enhancements a little easier. I also added syslog debugging, which will log messages to /var/log/messages if it’s needed for reference later on.

I’ve been running the new version for most of today and it’s worked great. Try the new version and let me know if there’s any glitches!

Also as part of this update, you’ll need to install the Python YAML library. sudo easy_install pyyaml

https://github.com/drsprite/OpenSprinkler-Push-Notifications

[Pat]

Updated with the port variable. Feel free to “upgrade” and try it out 🙂

I should probably move all of these settings into an external config file to make it easier to keep track of them.

[Pat]

Glad you figured it out! The port variable isn’t a bad idea either. I’ll work it into an update

[Author]

Posts