[jakestevenson]

Thank you for the update. I guess I’ll go with my own relay board through GPIO.

[jakestevenson]

Thank you, I think this clears everything up now. I just had a hard time, where my brain didn’t understand the concept of “Firmware” on the raspberry pi as just another application being run, but in the context of OpenSprinkler it makes sense.

I understand the system and have all the tools I need now thanks to your help.

[jakestevenson]

Please pardon my ignorance on this. I’m still struggling to figure this all out without just giving up and running the python interval program.

I’ve cloned https://github.com/OpenSprinkler/OpenSprinklerGen2 onto my raspberry pi and followed the build instructions (./build.sh ospi). This generated an OpenSprinkler executable in that folder.

When I run that executable nothing seems to be happening. That may be ok, I’m not certain. Then I went to the firmware documentation at https://opensprinkler.freshdesk.com/support/solutions/articles/5000632570-api-documentation-firmware-2-1-5-current-. It looks like it uses http for the transport layer, so on my raspberry pi I ran “curl http://localhost/jc?pw=dev” I get the message that it cannot connect to host. Is

Does running this application actually enable the API? If so, does it do it on port 80?

[jakestevenson]

I was kind of hoping for something lower level than the API. It looks to me like the API requires running the python software somehow, and I’d prefer to manage that myself.

[Author]

Posts