Forum Replies Created
It looks like the latest version of Dan’s Interval Program from October 4th does not work with your Mobile Web App. I had the same issue and had to revert back to the September 23rd rev. It will show that the system is disabled.
Thanks Dan. I will check it out and let you know if anything comes up.
Everything looks great! I ran some tests and it is working with no issues so far. I set a program at 00:00 hours and another at 23:00 hours. It is showing the correct program preview all day and has been running the schedule on time. Thank you for the fix.
I am still having the issue after 17:00 hours. The issue seems to be at… devday = int(now/86400) # Check day match it is not compensating for the time difference and gets stuck at if (devday %prog) != (prog – 128): return 0. Also the program schedule devday=’+str(int(t/86400))+ needs to pull from the local time as well. Thanks. I was playing around learning something new, but it has been fun. 😀
OK here is my fix so that it will calculate your local timezone in ospy.py. It will add or subtract the time depending on where you live.
devday=’+str(int((t – time.timezone)/86400))+
def prog_match(now, prog):
devday = int((now – time.timezone)/86400)
I think I found the problem. It looks like an issue with devday in ospy.py, I manually subtracted the 7 hours with 25200 seconds and it looks like it works. I made a change to the graph_programs and the prog_match. It just needs to calculate the selected time zone in order to fix the issue. Hopefully this helps.
def prog_match(now, prog):
devday = int((now -25200)/86400)
I am still having the same issue where it is off by 7 hours. If I set the watering schedule for 16:15 it will water that day on time. If I set it for 17:15 it will not water that day. Some how there is an issue with the localtime and gmtime. I suspect it is reading the gmtime, but it is showing the localtime on the interface. I wish I could be more help, but my programming skills are very limited.
My main watering device is Ray’s Opensprinkler V1.2U, so I run this one virtually just for testing. I like the work you are doing and hopefully I have been of some help. In the future I may switch to the Pi because of the Wifi and flexibility. 😀
After running date +%Z I am showing PDT (Pacific Daylight Time). I am in SoCal so it looks good.
@Dan in CA wrote:
I have set up some test programs as you described. I’ll see how it goes and get back to you when I have some results.
After playing around with the time on the Pi I noticed that the change happens at 17:00 hours, it show the correct running time before 17:00 hours and then it shows the next day after 17:00 hours. It seems to be the opposite issue as last time. My watering schedule starts at 22:00 hours for a duration of 12 minutes on each station.
It has to do with the timezone on the interval program. It looks like it is not syncing with the Pi.
I have noticed that the interval portion of the program seems to be buggy. I have it set for 2 Days and the Starting In is set to 0, but it will show the next day and run then. If the Starting In is set for 1 day it shows that same day and runs. If I let it run so it will count down to 0 then it will show the next day as running, when that day comes. I installed it as a fresh install and followed your directions. Can you check to see if you are getting the same issue. Thank You.
My schedule ran normally tonight as usual. Not sure why I didn’t notice that before, maybe I was only checking it at night. I appreciate the work you have put into this project and for your quick response. The interval program is really nice and has been working great so far.
It looks like before 17:00 hours it shows it will run on the 16th, but after 17:00 hours it shows the 17th. Could this be something weird on my end?
I checked my schedule again and now it shows that it is not going to run until tomorrow the 17th. Weird huh? It must have past a certain time and now it is showing correctly on the preview screen.
Everything has been working great since August 5th. I have configured my system to water every 2 days for 12 minutes. It has watered every other day with no issues and it last watered yesterday August 15th, the system now shows that it is going to water again today August 16th. Is it just me or has anyone experienced this? It looks like it counted too many times on the countdown and shows 0 days, when there should be 1 day left. The Pi has been running normally and has not been rebooted.
I honestly liked the original theme better with the 3D buttons, these colors seem a little to loud. Maybe you could add an option for the original theme or have a slider that would allow you to change to whatever color you want, with flat or 3D buttons. Just my two cents, so it may not be worth much. 😉
Works great for me. Sorry if it seems like I am being critical. It must have been the years of hardware/software compatibility testing that I use to do, so I tend to be a little anal. So hopefully it has helped a bit. But I feel at this point you have a rock solid app that really surpassed my expectations. Thank you for all of your hard work. Please donate to Samer’s if you find this app useful.
Thanks Samer’s for all the great updates. I have been using the logging and it is a nice addition. However I did notice that if it goes over the minute by one second it will log it as another minute, so essentially it will show two minutes. Can you give it a grace period of a second or two, because I notice my 12 minutes cycles will also show 13 on some stations?
Looks like when you bridge the Raspberry Pi it will use the same MAC address for both the bridged connection and the Wifi connection. I have tried setting it manually with no luck. You cannot set a rule for the MAC on the AP because of this issue, that is why I had to set it on the Opensprinkler itself. If you look at your AP you will see it flop between the ip address connected to the NIC and the ip address connected to the Wifi connection itself. When I hard-wire the Opensprinkler it functions with no issue. For some weird reason the Opensprinkler locks up hard with this configuration.
I am running a Raspberry Pi as a WiFi bridge. I have had a static ip set on the Opensprinkler and for some reason the combination of the two causes the Opensprinkler to lock up. I never had this issue before, but it could be that after updating the Pi something may have changed. So after it locked up again today with the Static IP, I pulled the network connection and the Opensprinkler still did not respond even after a few minutes. Any ideas why the NIC would cause it to lock up? I am going to set it to DHCP and see if I get the same results.
I am having an issue with the first time run. I have deleted and reinstalled with the same issue. The install.php file is pointing to the old version of jquery 1.3.1. Is this an issue with Github not updating all of the files properly?
Everything looks great. I love all the changes. But I am having an issue with the Program Preview not showing the station names correctly, it shows S1, S2, S3 and so on when using Safari on my iPhone. However it does works fine on my iPad and other devices. I have tried it on a iPhone 4 and iPhone 4S. Strange one I guess?
Also what do you think about adding the Opensprinkler Firmware Version under the Settings under Device Options. (I probably think too much. 🙄 )
I am also having a weird issue with the logging after I Clear the Logs. The first station shows that it has run, but you do not see the Runtime or Date/Time. I am assuming that it needs a starting reference in the log and it does not have that, when I add it manually then it is fine. Have you seen this issue?
Also the Run-Once Program is now working great with the new Interval program. Thanks.
It looks like with the new release of the Interval Program for July 19 2013 there are some issues with the last station on the Run Once program. It works directly from the OSPi application, but not on your mobile app for some strange reason. It did work before. Please let me know if it is me or there is an issue. Thanks.
I finally added a running timer to the status page @kenbob. I honestly have not been able to test it accurately because I do not want to test on a live system and the OSPi interval program (latest copy) is giving me issues with runonce programs. Please let me know how it works, thanks!
I reverted back to the Jun 26 2013 interval program. The running timer on the status page looks great and seems to work with no issues. I really think this app has already exceeded a lot of expectations and really gives the Opensprinkler a nice polished front end. Thank you for all your hard work.July 15, 2013 at 11:59 pm in reply to: OpenSprinkler Interval Program now available for OSPi! #24445
I am using your latest 7-10-13 copy and having issues doing a run-once program. I see it appear in the queue then it just disappears. Not sure what is going on, is it just me?
I am also having the same issue. It looks like all the station count down at the same time, but only one station is running. When it is done, the Log of the last station shows some crazy time that it ran.
Could you also have it pull from the water_log.csv file on the Interval program? That would be a nice feature. It looks like it is built into jquery http://jquery-csv.googlecode.com/git/examples/basic-usage.html. The log already gets created when enabled and would be a nice addition to this program for the Raspi.