Forum Replies Created
-
Posts
-
ray, I am sorry, I phrased my problem rather badly. I am not having issues with the rain sensor or operation of my ospi. That is working like a charm. My issue is the notification via IFTTT. Notification about a program start is being sent even if rain sensor is tripped and even if the whole system is deactivated. This is not how it is supposed to be. Why send notification about program start when in fact nothing is happening.
it was quite rainy the last couple of days, rain sensor was constantly tripped. My scheduled programs didn’t run as expected, but the IFTTT notification is sent at the beginning of the scheduled run even if the run is actually omitted. Is there a chance to fix that?
I just realized that the start of a scheduled program is notified indeed. I had only used manual runs up to now. So all is well 🙂
@Samer thank you for your help. I was able to start Richard Zimmermans 1.0.7 firmware which runs without any problems, no powercycling.
So the issue seems not to be with my ospi but with the new unified firmware.
I wonder what is different in my installation from all the others which seem be running fine. Anyone using unified firmware with an extension board?I tried to revert back to the previous working version but seem to be unable to prevent the unified firmware to be automatically startet at bootup. Could someone kindly advise me as to how to make the old version to be loaded at bootup?
Right now my ospi is unusable. 😢I have a similar problem, but only when the valve is turned on.
See http://opensprinkler.com/?post_type=topic&p=37355#post-37513Ok, I did some more testing.
The voltage cycles between on and off regardless of a masterstation.
The off voltage of stations 12-18 is 7v regardless of their disabled status.
Is there anything else I can try?Ray, Thank you for getting back to me.
I tried turning on only one station at a time manually. This opens the selected valve and starts the pump, turns both off after one second, turns them on again and so on.
I will have to try what happens if I dont define any master station. I’ll keep you updated.I bought this one
http://www.conrad.de/ce/de/product/515213/Hutschienen-Stromversorgung-Serie-TBD2-ACAC-24-V-AC-24-W-Comatec-Inhalt-1-St?ref=searchDetail
This one is available in a range of watt ratings. Depending on the number of stations you want to use at same time you might have to choose one with more or less power.I ran into serious issues after updating firmware to the latest version on my ospi. I use one extension board, S1 to S16.
I have a pump on s1. Once i turn on any Station manually, S1 and the Sx cycle between 24v and 0v every second.
I tried to set the masterstation to S11 which I am not using, same result. Using two stations as masterstation and setting Sx to use both again shows same result. Powersupply of ospi is at a stable 24vac.
Any thoughts?I also noticed that the off voltage readings of stations 1 to 11 are 0.5v which seem ok, but station 12 upwards read 6.5v in off mode. These stations are set to disabled.
Current weathercondition on Wunderground “light rain”. Ospi says “no rain sensed”. Rain delay is Not working. 😕
Another question regarding rain delay.
The rain yesterday set the rain delay which will end in 13min.
Guess what! It started to rain again. Wunderground agrees: current weather condition light rain, forecast thunderstorm. How does the logic for adding a rain delay work? I would have expected to see an additional delay in the light of current conditions and forecastI did some more testing. I guess I misunderstood what the suggested code change does.
I thought it would multiply the input value (in seconds) by 60, so in order to get 30min delay I entered 30 as station delay value.
As no actual delay between succeeding runs is visual this is most likely wrong.
I realized that after the code change I can enter values up to 999 (about 16min), and these do show up in the preview.
Alas, no 4 digit values can be entered. But I’m much closer to the 30min I need. 🙂
Regarding my second need to start the master pump 3min before opening a valve I still have no idea how to modify the code.@salbahra
OK, I too did a git pull, restarted and for the first time see “SUPPRESSED BY RAIN DELAY”. Thank you! 😀
I have no idea though why it didn’t work earlier.
@rederikus
I guess we had a similar idea what “rain delay” is.
So in line of your interpretation this would be used by someone without a hardware rain sensor to avoid any program start for the next x hours, right?No, i don’t think so. I did just now. Forecast was right, it’s raining now. No rain delay was added. Did i miss something?
I just realized that zip codes are only supported by wunderground for the us. As I live in Germany I entered “Grafrath,Germany” as location on the options page. Wunderground web page shows a thunderstorm forecast for this afternoon. Still, in the web app I get “no rain sensed”. Log shows the programs were run this morning. Rain delay seems not to be working.
@Ray: I’m afraid I was not successful
@ray wrote:The station delay is in units of seconds. But it’s pretty easy to modify one line of code to change it to units of minutes. Specifically, in ospi.py, around line 151:
accumulate_time += gv.sd # add station delay
just change that to
accumulate_time += gv.sd * 60 # add station delayI modified the line as suggested, in options changed the station delay to 30 wich should give me 30*60s but in the preview I only see 30s delay. Should the delay show up as 30min?
@ray wrote:
About master on adjust time — currently it only supports a positive value. … in ospi.py, around line 135, the function
def schedule_stations(stations)
this is where stations are scheduled (i.e. stations that should turn on are assigned a start time and stop time). You can push the start and stop time by 180 (3 minutes), and that will cause the master valve to be on 3 minutes before any other station turns on. I haven’t tried this myself so I don’t know if there are other changes you need to make. But the idea should work.I changed line 148 to
gv.rs[sid][0] = accumulate_time + 180 # start at accumulated time # pls90: and add 3minand line 164 to
gv.rs[sid][0] = gv.now + 180 #accumulate_time # set start time # pls90: and add 3minNeither in preview nor in my test was the pump started before the valve was activated.
I guess I did something wrong. 😕
Any thoughts on my issue? Thank you!@Dan
Thank you very much for adding my request to the wish list. The idea to realize this as a plugin is brilliant!
Again, thank you for your hard work!@Ray and Dan, thank you very much for your suggestions. I will give it a try next weekend and report back.
@Dan, your solution should definitely work. This would make scheduling a bit more complicated so I’ll try to incorporate Ray’s suggestions. As from a UI point of view everything is already there apart from the restrictions for negative values it would be nice if theses changes could find their way into the “official” source code. I do believe that some people have similar issues with a “weak” well.I just installed the OSPi and set my first programs.
I am really impressed with the functionality. That beeing set I ran into 2 little obstacles.
I wanted to set the delay between the start of different stations (options > station handling > station delay) to 30 min.
The reason is that my well does not supply enough water, so after 15min of watering I have to wait a little while for new water to gather. Max. delay time seems to be 240s. Is there a chance to increase that value? (maybe 30*60s=1800?)
Also, the preassure provided by my pump is very low. In order to get some of my rising sprinklers to work properly I have to turn on the pump with all stations closed to build up pressure on the line, and then open one station. The time to do so would be about 2-3min. Under Options > configure master > master on delay there is no possibility to enter negative values. What I would need is a value of maybe -3. Again, would it be possible to allow negative values?
Thank you.
