[Samer]

Great news! I actually have the preview working using live data. It’s a bit of a tight fit at the moment but here is a working preview:

The only issues left are stuffing the program ID inside the box and fixing a minor bug rendering the preview on page change. Should hopefully get this pushed out today. I assume everyone prefers this to the boring text that existed before?

[Samer]

@cmwahlqu That’s fantastic! Was actually planning on asking you since I saw beta 2 out today.

Thanks!

[Samer]

@andrew I guess I never tested that. I will see if I can catch the swipe motions over the flip switches and ignore it.

As for the preview programs window that will be incorporated into the current page. Therefore, the current date selector on the top will still be active to change the days. I am actually merging the two as we speak and will hopefully be better to explain it with a visual soon!

[Samer]

@andrew Thank you for the bug report! I updated my code, and pushed the changes, changing the maximum from 1440 minutes (24 hours) to 1439 minutes. Very easy fix as you suggested, thanks again!

[Samer]

I am finally making some progress on the program preview and wanted to show everyone a preview of what I have, so far.

It is perfect on the desktop (ironically enough) but still needs some work on mobiles. Once I finish tweaking everything I will incorporate it into the app and push the update.

Let me know what you think so far!

[Samer]

@Kevin thanks for the kind words! I agree the documentation needs to be more cohesive. At this point, there is information on Ray’s website on how to get the OpenSprinkler Pi setup, documentation on Ray’s blog on how to install the OSPi interval program, and information on my Github page for the web app installation but it is fragmented and could be useful if it all came together. I think Ray is an excellent blogger and hopefully he will post back here with some more information/guidance.

Just to bring everything into one post, these are the steps to get the OSPi up and running with the interval program and web app:

1) Follow the instruction’s on Ray’s website for general hardware installation (Steps 1-5): http://rayshobby.net/?page_id=5874
2) Setup the operating system on the RPi by following the quick-start guide (Boot up into Raspbian): http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2.pdf
3) Install the OSPi software by following Ray’s blog post: http://rayshobby.net/?p=6339

For the web application you have two choices. You can either install and run the web app from your Raspberry Pi (or your own server) OR you can directly use the web application hosted on Ray’s website. Once you make a decision you will continue to step 4a or 4b. Just to give some information to help make a decision, if your using an OpenSprinkler Pi, 4a might be more useful since you already have the hardware to host your own copy. The other advantage of 4a is logging capability.

Option 4b is better suited for users of OpenSprinkler (not the RPi version) and do not have a computer running 24/7 at home. However, option 4b does require a port to be forwarded on your home router.

4a) Install the web app using Ray’s blog post: http://rayshobby.net/?p=6409

–OR–

4b) Navigate to my web app hosted on Ray’s website and using your WAN IP you can access your OSPi: http://rayshobby.net/apps/sprinklers/

Anyone is welcome to bring this information into an easier to present document and I would love to assist with any questions but I doubt I could draft up clearer documentation than the ones linked above.

Thanks!

[Samer]

@Vaughano Thank you very much! I think you make some very valid points and at the very least have brought to my attention how elaborate the system would have to be to account for errors, etc. I’ll be the first to admit I have pushed some updates that broke things and required a subsequent update. For now, I will hold off on the idea and revisit it at a later time.

Thanks again!

[Samer]

I am debating adding an updater to the watcher.php script so that updates from Github are automatically pulled. Is this something people would be interested in? I know some people might find this weird so curious as to how people would want this implemented, if at all. I think by adding a setting during install and in the configuration (ex. $auto_update = 1) then checking against it during watcher.php runs, as such:

if ($auto_update) `git pull`;

Of course, this requires your using git instead of downloading the zip/tar and extracting manually but it should serve it’s purpose just fine, I think.

Let me know what you guys think.

Edit: Also, shell exec would have to be allowed for this to work.

[Samer]

This one is just plain nit-picky but you have a debug on line #594 that can be safely removed:

        print nstlst

[Samer]

The good news is, we reached the exact same fix! Also, Dan got back to me and said he has incorporated the fix into the development version and should hopefully get pushed out soon as part of the official package. The OSPi software has really come a long way and very impressed with Dan’s work.

Absolutely loving the community around OpenSprinkler!

[Samer]

@kenbob I believe that is the same fix I posted above right?

Edit: I just replaced the whole line to make finding/changing it easier.

[Samer]

@Oasiz37 Thanks for the suggestions! In regards to your first bullet the OS keeps track of only the very last station run but does not report what program/mode is running each station when polled (using http://OS_IP/sn0) so there is no really good way to grab this data via the API (unless I decide to parse the lrun array every minute and try and make sense of it, which is only updated after the station is off). Plus, I really don’t know the best way to display the data if I had it. The logging system is being pushed to it’s limits IMO and would require an overhaul to add even more features as suggested in this forum (graphs, program/mode of each station run, etc). I managed to stuff the rain sensor log in because it was easy but anything else would be too much at this point.

Also, in regard to your previous request about the interval duration (HH:MM vs MM), I looked into it and could not find a simple solution and have deferred that until something comes up allowing the change.

Update: For your second bullet, I added that feature and pushed it to Github! Page title on any page after the home page will be prefixed by the $webtitle variable in the config. Enjoy!

[Samer]

@PabloS/@cmwahlqu I found a fix for the red bar not moving in program preview and submitted it to Dan. In the meantime your welcome to test this fix if your comfortable editing some code.

Inside ospi.py you will find the following line (#796 in the latest code 6/22/2013):

        graphpg += 'n'

And the fix is to change it to the following:

        graphpg += 'n'

[Samer]

@kenbob This has been addressed and fixed in the latest code posted on Ray’s Github. Please update your OSPi program from here: https://github.com/rayshobby/opensprinkler/tree/master/OpenSprinkler%20Pi/software/demos/interval_program

You will notice the Jun 22, 2013 update which addresses every bug that has been discussed in this forum and is 100% compatible with my mobile application.

[Samer]

Fantastic! I suppose I could “pad” all the old entries but that might introduce more problems than its worth. I think for anyone wanting the new rain sensor logging they should just empty their log files like you did, assuming everything works well.

Thanks for the feedback!

[Samer]

@momanz It is very likely the old log entries aren’t mixing well and causing the discrepancy your seeing. I only considered preventing errors with the new code and old log files but didn’t spend much time engineering it to properly display rain sensor data with the mixed log format. I will look into a way to make it work in the mixed environment but unfortunately it might become necessary to “reset” your log data.

Let me know if you have any luck by starting the log over or wait for me to find a way to salvage the logs and get back with you (hopefully).

[Samer]

@kenbob I pushed an update for the RPi interval program to address the sequential mode (rather the lack of it). It will now properly preview programs.

Enjoy!

[Samer]

@momanz I just pushed an update that I believe adds what you are looking for. I patched watcher.php to log rain sensor changes (0/1) to the log file. I updated main.php to show the changes below all the stations as Rain Sensor and shows the duration between changes similar to run times for a station. The header displays the total switches from on/off. Please let me know if this works and more importantly if this is what you were after.

I do not think this change will effect current logs however it might. If anyone has issues please let me know.

Edit: I pushed some minor updates to fix undefined offsets and to also make sure “Use Rain Sensor” is enabled before attempting to display any rain sensor log changes. So be sure you have that option enabled if you intend to view changes (which I think is a requirement anyways for the OS to update the rain sensor status).

Preview (ignore dates/times I made them up to test):

[Samer]

@momanz You are absolutely correct! I will be honest, I do not have a rain sensor nor did I know how they worked. I read through a lot of the forums and the sensor seems to be a hot topic! So basically, you want the rain sensor to show up as a “zone” in the list and show when it was switched on/off and the timestamp as well? I think I can code that up the only problem with the current system is the sn0 data is put into a file next to the time. The script then cycles through the text file and splits the sn0 data and uses the array index to correspond to the station names array. I could add another field after the timestamp displaying the rain sensor state and subsequently when cycling through display the data. I will play with this however without a rain sensor and a good way to test it, I expect it to take some time.

[Samer]

@cmwahlqu Perfect, thank you!

Edit: This is documented on the forums and is being worked on: https://forum.jquery.com/topic/changepage-in-ios-7-appears-to-be-broken

[Samer]

Oh, iOS 7 is unsupported at best. It is in beta and I wouldn’t rely on it for actual use at this point. I know jQuery mobile is not marked as supported for iOS 7 yet. Until then it is hard for me to offer any advice or support. I will do some research but at this point I do not think I will be able to pinpoint the problem especially since I do not have access to iOS 7.

[Samer]

@cmwahlqu I have been testing it on different devices via emulator and had no problem. Also, tested it on my iPhone with no problem. However, based on the symptoms you described I think the pageinit event is not firing after the page is loaded. As an attempted fix, I moved the javascript after the page content in sprinklers.php. I have pushed this update, try it and let me know if it helps.

[Samer]

@cmwahlqu Any error message? If the login fails usually say’s unable to login. Or is it redirecting right after? I am pretty sure I disabled all auto-correction on the login form however that might be the difference between the desktop and mobile. The iPhone likes to auto-capitalize things and the login is case-sensitive. I will scan through the code and attempt to find the problem in the meantime.

[Samer]

@cmwahlqu No problem, can’t believe I keep missing these things haha! Happy that it’s working!

[Samer]

@cmwahlqu Sorry about that! I made a mistake upgrading to jQuery 1.3.1 and forgot to upgrade the installer to match! I just pushed a fix. Try the new files and let me know if that fixes the problem.

Thanks!

Edit: @kenbob that might have been the problem you experienced as well! Glad it’s working now though!

[Author]

Posts