![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
As an experiment I ported my local UI to the sprinklers_pi code base.
Sprinklers_pi is an alternative control software, it is intended to run on Rasberry Pi, but it also compiles and runs on the standard Arduino Mega - class hardware. This control software is considerably more sophisticated than the base OpenSprinkler code (at least in comparison with OS 2.0), but unfortunately it does not have any local UI - all display and control is strictly via the WEB browser.
I ported my local UI implementation to the sprinklers_pi code base, and got it working. The code is posted on my Github repository. The base code is indeed pretty good, I like more flexible and comprehensive scheduling capabilities, also the code is self-containing - it does not rely on the rayshobby.net site for HTML. Instead, sprinklers_pi code is serving all necessary pages locally, from an SD card.
Local UI (on the local LCD) makes sprinklers_pi functionally similar, and in many ways a super-set of the original OpenSprinkler code. I'm inclined to stick with sprinklers_pi code as the base since it will be easier to build on.
The only potential problem with the sprinklers_pi code is the license. The code author (Richard Rimmerman) did not include any license with it, but in e-mail conversation he stated that this code is free for personal/non-commercial use, so for my own private experiments it should be fine. But generally I would prefer some form of an OpenSource code and broader contributors base.
I will probably try to write my modules to be fairly independent and portable, to allow easy use of this code on both sprinklers_pi and on OpenSprinkler code base.
Sprinklers_pi is an alternative control software, it is intended to run on Rasberry Pi, but it also compiles and runs on the standard Arduino Mega - class hardware. This control software is considerably more sophisticated than the base OpenSprinkler code (at least in comparison with OS 2.0), but unfortunately it does not have any local UI - all display and control is strictly via the WEB browser.
I ported my local UI implementation to the sprinklers_pi code base, and got it working. The code is posted on my Github repository. The base code is indeed pretty good, I like more flexible and comprehensive scheduling capabilities, also the code is self-containing - it does not rely on the rayshobby.net site for HTML. Instead, sprinklers_pi code is serving all necessary pages locally, from an SD card.
Local UI (on the local LCD) makes sprinklers_pi functionally similar, and in many ways a super-set of the original OpenSprinkler code. I'm inclined to stick with sprinklers_pi code as the base since it will be easier to build on.
The only potential problem with the sprinklers_pi code is the license. The code author (Richard Rimmerman) did not include any license with it, but in e-mail conversation he stated that this code is free for personal/non-commercial use, so for my own private experiments it should be fine. But generally I would prefer some form of an OpenSource code and broader contributors base.
I will probably try to write my modules to be fairly independent and portable, to allow easy use of this code on both sprinklers_pi and on OpenSprinkler code base.