Forum Replies Created
-
Posts
-
I have no experience with SprinklerAce however my mobile app will work out of the box now. If you don’t wish to install the mobile app you can simply use the version hosted on Rays website (requires a port forward but gives you access anywhere) available here: http://rayshobby.net/apps/sprinklers/
If you want it running on your Pi (which brings extra features such as logging) you can follow the instructions on my Github page here: https://github.com/salbahra/OpenSprinkler-Controller
I like @slobrewer’s idea of using Github more. Also, since this is my thread I actually know where everything is and almost everything we’ve discussed so I am fairly certain I have heard and noted everyone’s requests. In the past, these were added/changed same day. It is recently that this stopped happening hence why I listed what I am wanting to work on. If you have issues please do fill out a form on Github.
I do think it would be nice if Ray added a mobile app forum section could help separate out specific questions and also make it easier to find answers down the road.
@PabloS In regards to the run-once program. That would have to be solved by the firmware or interval program. I could technically do it using the server but I think in the end it would work better if the firmware handled that.Ah okay, I see your concern. Are you using the Pi version or not? If your using the Pi version you could just have a script that restores a default config every night like you suggested.
If not, I don’t think you can currently do what your wanting. You either depend on the server or don’t. However, instead of doing a 0% (if your trying to prevent a program running) you can do a rain delay. That has a timer by default. Of course limited but again not sure how aggressively you want to modify your watering.
Of course, you can also modify the actual firmware on the OpenSprinkler to use weather control directly. I know with version 2.0 it has a lot more memory and could possibly accommodate something like that.
I know a wiki is being worked on to aggregate this information however here is some simple answers to your questions.
The Raspberry Pi is the logic for the OpenSprinkler Pi. The OpenSprinkler Pi has no logic or network interface and therefor you don’t need to worry about it at all after attaching it to your Raspberry Pi correctly.
The Raspberry Pi needs several things to properly control your sprinkler system. It needs an operating system which it sounds like you have (eg. Raspbian). It then needs the interval program installed available here: https://github.com/rayshobby/opensprinkler/tree/master/OpenSprinkler%20Pi/software/demos/interval_program
Honestly, thats it. You don’t even need a HTTP server for just that and you also don’t need to worry about the firmware versions. The interval application says it uses 1.8.2 but that is because it is based on the OpenSprinkler 1.8.2 firmware. The only major difference between 1.8.2 and the newer ones (1.8.3 and 2.0.0) is the sequential option which Dan is working to add back in.
I think the confusion arises when you read posts related to my mobile web app which does require a web server and requires a different port (same IP is no problem). If that is something you need assistance with I would be glad to help however I suggest getting a working interval program first then proceeding from there.
You might be over thinking it. You can setup a basic program that runs normally and modify it as parameters come in using the API.
For example, if your program wanted to double the watering times for all stations you could simply change the watering level from 100% to 200%.
If you want to tweak specific programs you also could push those changes each day as appropriate.
This probably arises because the wording was designed for the OpenSprinkler and not the Pi version, intially. The robust Pi support happened afterward. It would be great if we could package the app with the interval program however the development of both of these applications is happening so rapidly it’s hard to produce a package that wouldn’t be outdated within a day. I think this is on the long term goal list just too early right now.
Also, auto updates for either are too early as major changes keep occurring.
0.0.0.0 means its listening on all available IP addresses. This behavior is fine so long you don’t have multiple IPs bound to the same NIC.
No problem and just to clarify the interval program and the web app DO run on different ports. In your example, the web app is on port 80 and the interval application is on port 8080.
Glad it’s working now!
No it’s not. Your web server is installed using apt-get and is separate from the interval program. Common web server’s are Apache (listed in the instructions), nginx, and lighthttpd.
Make sure you specified the right port is the only thing I can think of. Use the same IP:port as the URL to access your interval application.
There should be an update now dated June 26. It addresses some issues in scheduling timers and might fix your problem.
Very glad it’s working! You have exactly the right idea about using your outside IP (which works fine inside since your router know’s its IP and never let your requests leave the house).
By the way, as residency picks up my pace will slow down here. I still want to work out kinks and improve on others. With that said I want to list in priority what I plan to work on.
1) Current status page (needs to focus on status and not random variables)
2) Add active timers in status page
3) Fix firefox bug with green light image being dropped below the text box (caused by a scroll bar appearing because the content has a min-height in place by JQM)
4) Improve user management (add, drop, edit)If there is anything I am missing please remind me.
Thanks!
Nope the hosted version is awesome because you don’t have to tinker with it! So long you know the IP, port, and password you can access your device from anywhere by just going to Ray’s hosted version. All the settings are stored only in your browser and never even cached/stored on the server.
So the only trick is getting the right port forwarded.
What you quoted above was not tailored to the OSPi so let me make a small modification for RPi users. The interval program defaults to port 8080 so just change port 80 in what I said earlier with 8080. When you visit the hosted app and it asks for the device IP you will use your external IP from http://wimi.com and the port 8080 so it looks something like:
208.29.190.24:8080@sjarvis The problem is you have the wrong port setup in my mobile app. I suggest deleting config.php and starting over but this time when putting in the IP add :8080 so it looks like this:
10.0.1.24:8080@sjarvis wrote:
I can run Dan interval program (on port 8080) and control my sprinklers just fine from that.
…file_get_contents(http://10.0.1.24/sn0): failed to open stream: HTTP request failed! HTTP/1.1 404 Not FoundThe last part shows which IP:Port my mobile app tried to use. It doesn’t show the :8080 which your saying is the port used by interval application.
@PabloS this might be your issue as well. In my mobile app your IP should be followed by :8086.192.168.1.12:8086Edit: You can also edit your config.php and add the :8080/:8086 manually after the IP.
I just installed a fresh copy of OSPi from Dan’s repo and a fresh copy of my webapp from my repo and it ran no problems. I am now starting to think you both ran into a network issue at the same time so let’s try to treat them differently, for now.
@PabloS Is your OSPi hosting the interval program and the mobile web app?
If not, is the server in the same house or network as the RPi?
If yes, are you using 127.0.0.1 for the IP (try this if your not) or it’s LAN IP?It seems your setup of the interval program went well, and yes the sn0 is an API call to get the station status for all stations. The problem is your web server (the language my program uses is PHP thats executed by the web server) communicating with the RPi. The most common problem is the server and RPi aren’t on the same network. This means you have to open ports and ensure your using the device’s WAN IP’s.
Hey Kevin just to make a suggestion: If your trying to get your OSPi accessible using the mobile app by doing a port forward, you might be interested in the hosted version. It is available at http://rayshobby.net/apps/sprinklers and works almost exactly the same way except the app is hosted on Ray’s website and speaks directly to your Pi using the port forward for the device. Hopefully im not confusing you more! If so, disregard however I think it might be something you’ll like.
Yes, means everything is working properly on your OSPi the question now becomes: why can’t PHP access the same URL?
I will take a look at this tonight. It’s possible I broke the installer recently and haven’t tested a new install situation in a while. Once I do some testing ill hopefully be able to put a finger on the problem.
Thanks!
Update: The 404 error typically means the IP or requested URL is incorrect. Is 10.0.1.24 correct? Try navigating to http://10.0.1.24/sn0 in your browser tell me if you get a reply.
So the second command is to show you if your interval program is running. You should have it running in the background but what you pasted does not show it running.
@wyone another great suggestion! Just changed the color to green and I like it a lot better! Thanks!
Another thing to keep in mind is the IP/Mac is different for each interface. Which means your wired and wifi both have their own IP/Mac. When setting up port forwards and static DHCP ensure your using the right interface.
When downloading from Github you have to make sure your using the get raw link.
@kenbob Thank you! I noticed the Firefox issue actually but its on the back burner for now, haha. The issue is the min-height on the content after the status bar scrolls in. That will fix the green dot. The other thing is zoom not working on Firefox which is probably just a browser specific prefix issue I should sort out soon.
Update: I fixed the weather for now, the green icon will get fixed soon.
