Forum Replies Created
-
Posts
-
Looks good from my point of view too, automatic programs succeeded last night and manual runs compete with the app forcibly closed. Thanks!
Will report back if any issues persist.
Returning to the commit above sees my scheduled programs working again, which is great. Hopefully this helps with bisecting where the issue was introduced.
That said, I believe this firmware has an issue where programs scheduled for the weekend (Saturday and Sunday) will only run intermittently (see my other post). I’ll be interested to see if this issue returns or can reproduced by others.
Going forward from a dev point of view, if there’s a way to have Open Sprinkler output verbose, debug-level logs and/or tracebacks for errors, then I can assist by digging into the code if/when these issues occur.
Thanks for looking into this!
For the interested, I’ve reverted my OpenSprinklerGen2 code to this revision and manual runs appear to work correctly with the app/website closed. This was the first revision I’d ever checked out and most things appeared to be fine at that specific commit so they should seemingly be fine again now. I’ll report back about scheduled runs tomorrow.
As an update to this, my OS Pi is no longer running any programs automatically & hasn’t for the last 3 days. This sounds similar to others’ issues mentioned on this forum.
Okay, sounds like my issue appears to now the same as yours then, I have the same symptoms. The programs used to run automatically on most days but they’re not running at all now unless I trigger manually. Separately, I tried a manual program this evening for 1 minute and it continued to run forever until I opened the app.
@s3v3n7w0, I’d had issues with my wifi as well but changed from a generic eBay wifi adapter (edup brand, RT5370 chipset) that has known issues with the Raspberry Pi to a TP-Link TL-WN725N & no further wi-fi connectivity issues. However, my scheduling issues persist and appear to be worse, with no schedules running automatically at all now. The OpenSprinkler process is running fine via its init.d script, so the problem I’m experiencing must be internal to the OS code.
This could be related to the previous forum post; where station runs are running forever. It seemed to me in my case (same firmware) that opening the app or website stopped the over-time station, which sounds like it could be related to this issue.
On another similar note, my scheduled runs have seemingly ceased to run automatically & I’m forced to trigger them manually.
I’ve performed the same upgrade & seemingly all went okay. As s3v3n7w0 mentions, though, I never had to restore my settings and my crontabs were empty. Did the upgrade not work correctly?
I’ve been noticing similar behaviour to those above today whereby an 8-minute manual run of one station never stopped, continuing for over 2 hours until I noticed the problem and issued the ‘stop all stations’ command via the app. Curiously, at the time, the interface wasn’t reporting any station running, but the logs now show the true duration.
Separately, this happened again with a 5-minute run — the station ended up running for almost 2 hours. Seemingly, it only stopped when I re-opened the OpenSprinker app on my phone to check if the program had completed. Again, the app wasn’t reporting anything running, but reports the true duration.
Also, I’ve noticed my OpenSprinkler fails to run scheduled programs entirely on certain days, but this might be a different issue. I’ll create a separate forum post for it.
App Version: 1.4.1, Hardware Version: OSPi, Firmware: 2.1.3, Raspberry Pi B, Installed using latest (at the time) image and followed upgrade instructions.
