Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Easy Manual Zone Feature? #38727

    Tails86
    Participant

    For anyone who is interested, I branched ospi_plugins from Dan-in-CA and added my keypad plugin here. I still still don’t have hardware, so I have only tested it using the web interface. Please don’t judge too much as this is my first time working with python.

    The keypad can be used for the following functions.
    -Start Manual Station
    -Start Manual Program
    -Set Water Level
    -Set Manual Station Time
    -Set Rain Delay Time

    -Activate Rain Delay
    -Deactivate Rain Delay
    -System On
    -System Off
    -Restart System
    -Reboot OS

    in reply to: Easy Manual Zone Feature? #38416

    Tails86
    Participant

    I find the documentation fairly straightforward so far. I’m new to python, so most of the time that I have spent building a plugin has been learning python syntax. I have a fairly simple working plugin now (attachedattachment failed). I don’t actually have the OSPi hardware yet, but I have confirmed that it works through the web interface. I still need to flesh it out and clean it up. What would be the best way to share this?

    in reply to: Easy Manual Zone Feature? #37910

    Tails86
    Participant

    My neighbor usually hooks up his air compressor to the main line, and than runs each zone on the control box for a minute or so. I suppose that he could go over to each valve to turn each one on manually after powering down the system. That is a good fallback if I fail to implement something that is easy to use.

    Thanks for offering your help, Dan. I have a lot of questions, but I’m still digging through the project. proto.py seems to be where I need to start. I see you even have documentation on that 🙂

    in reply to: Easy Manual Zone Feature? #37743

    Tails86
    Participant

    I thought about it some more. The terminal would be capturing keystrokes. I could have a program capturing those keystrokes and sending signals to the interval program, but that seems messy. It would probably be better/easier to implement a scanning keyboard on 8 of the unused GPIO. I can have a separate thread monitor the keys within the interval program. Then a flag can be set for timing_loop() to poll for. A buzzer would probably be nice to provide feedback on a valid entry too. Does that seem simple enough or am I overlooking something?

Viewing 4 posts - 1 through 4 (of 4 total)