Forum Replies Created
-
Posts
-
I’d like to up-vote this too…
Currently I do pretty much the same as Oleengr with multiple season tagged programs and manually enable/disable as and when.
I do use the water level calculations, which are great, but still prefer different overall scheduling for our different seasons…I haven’t seen OS v3 but assume the interface is basically the same as my v2.1…
On your OS base web page there should be a “block of little blocks” in the lower right corner.
Click that and you should get a menu, one entry of which should be “Change Rain Delay”, select that and you should be presented with a dialog that you can enter a manual rain delay in days/hours that will disable the running of programs during that defined period…
HTHIt looks like it could be an issue with the OpenSprinkler server running the weather.py scripts.
I sniffed on my LAN to see what my OS was trying to do and captured the URL it uses to get the latest weather update, then tried accessing that directly in a browser (which has worked previously) but am getting a “502 Bad Gateway” error from a box running “nginx/1.12.1“. This ties with the same error I was seeing int he sniffed traffic from my OS, even on the outside interface of my firewall so I figured it was not an issue on my side…Hopefully they’ll sort it out soon…
So, this issue is directly related to the OS being able to make successful weather calls which include the sunrise/sunset times…
https://opensprinkler.com/forums/topic/water-level-not-calculating/#post-53460Thank you for the reply, Ray.
The diagnostics showed that it was not getting a successful weather call which is strange as I captured the traffic on my network from the OS and could see the calls to weather.py and could even see the reply with the same data I get if I put the call URL into a browser.
The only strange thing is that both my capture and proxy see the URL as “http://*/weather.py” which seems a little odd…
Based on my test I knew my firewall was not the issue so I then looked at my proxy and setup a bypass rule for the OS.
Now OS gets successful weather calls and the water level calculations are happening, so I guess my proxy is not happy with something. I’ll leave it with the bypass for now until I figure out its issue…the logs from yesterday show that the program ran at 18:00 as the weather forecast shows as sunset, incorrectly, and not as the preview programs showed…
It’s interesting, if I look at the logs (prior to 2.1.7 upgrade) it shows that the schedule ran at 18:00 on the scheduled days but I I go look at the “Preview Programs” now (after 2.1.7 upgrade) it shows the schedules set for the correct sunset times, will see this evening as it’s due to run today…
I’ve managed to set the timezone to +02:00
I exported the settings to the json file and found the tz value and changed it from 28 (seems to be the default) to 56, saved the file and then imported settings using that file and not my timezone is correct, still can’t set it from the web/app interface anywhere…Still have the water level not re-calculating issue (and and issue with current day sunrise and sunset times – posted separately)…
okay, so I finally got my DIY OS 2.1 firmware upgraded to 2.1.7 using the instructions from here
https://openthings.freshdesk.com/support/solutions/articles/5000668400-updating-opensprinkler-2-1-to-firmware-2-1-6-and-beyond-
but with a minor change. The instructions show to use chip type m644p which didn’t work on my DIY OS, having a look at the chip I saw 644A printed on it so used the m644 option with avrdude and then it could read the chip…
Thankfully I didn’t brick my OS and it booted back up after the upgrade, with factory reset as per the instructions so I started setting up the options again…
I also see the app version is now 1.8.2
The water level recalculations still do not seem to be working but I now also have another issue…The clock time zone is set to -05:00 and I can’t find a way of setting it to my timezone (+02:00). I tried turning off “Use NTP” and I could set the date and time if wanted but timezone is still disabled.
This has effectively put my OS 7 hours “behind” and my scheduled programs will be off…
The Location in the options is set to my correct location…Anyone know how I can set the timezone?
Just upgraded to 2.1.3, thank you…
the logs all look great now, times all correct to local settings and great to have the disabled stations excluded from the keysHi Ray,
Is it possible to have a “sticky” topic in the forum with a subject along the lines of “OpenSprinkler Firmware release” (possibly separate for OSPi, Beagle etc) so that we could subscribe to the topic and new releases are announced in it, probably restricting replies to admins only???
I found out about the new 2.1.2 release when I logged onto the web interface of my OS, which was great to see there, but I because my OS runs so well I don’t need to login to it all that often but I’d get the subscribed topic notice when a new release notice is posted.Hi Ray,
Just curious if you’ve implemented the changes to “reduce the call frequency so that at least it won’t exceed the limit even in the worst case” in firmware version 2.1.2 as I’ve had similar emails from Wunderground, not many but a few???Firmware 2.0.5 added the feature of selecting which stations should ignore the rain delay.
I have a similar setup with plants under an awning that will never get rain so I’ve got a program set for the relevant station and have set the “ignore rain?” flag for that station, so now those plants get their water allocation as per my program setting regardless of whether it has rained or is raining.Hi Ray,
The RTC is a DS1307 with the small crystal (as in the picture in the build instructions http://rayshobby.net/wordpress/wp-content/uploads/2013/12/IMG_0003.jpg).
I read in another post (regarding the faulty chips) about shortening the connection from the crystal to the chip. I have mine soldered as shown in the build instructions but I could try solder the crystal directly to the chip if you think it’s worth a try?My script seems to be working well so far so I’m not overly concerned at this point.
Hi Ray,
Thank you for such a terrific product. I very recently purchased an OS v2.1u and was lucky enough to save a reasonable amount on the shipping (I’m in South Africa) as my wife happened to be in Chicago when I decided to buy it 😀
It didn’t take long to solder the components to the board and have it up and running with no issues.
This has got to be the best irrigation controller I’ve used and especially love it when I’m out in the garden with my wife and she comments that “the flower beds are looking a little dry”, out comes the phone and on comes the water 😛Just curious about this topic (Rain Delay only selectable Stations) as it’s about the only feature I’d dearly love to have at the moment as I have a zone that is under cover and does not get any rain so if I activate the rain delay (absolutely love that feature) this particular zone would not get watered.
I see this feature seems to be in the OSPi already http://rayshobby.net/phpBB3/viewtopic.php?f=28&t=337&hilit=rain+delay and was wondering how close the OS is to getting this option too?
I did see your comments above about coding in a bypass for the specific station and may just look into that as we’re just coming into our rainy season here, but if it will only be a short wait for this to be added to the OS then I may just wait.
