2017-05-04, 01:54 AM
(2017-05-02, 04:20 PM)Sailoog Wrote: There are some linux arguments that the python interpreter can not digest and this is an example. It does not like the symbol >. There would be a solution changig the way these arguments are interpreted but it could create a security issue. Let me try something.
Anyway, what you are trying to do it will be possible soon. When you define a GPIO output in GPIO tab it will appear as a new action to set this GPIO to High or Low. On next update.
(2017-05-03, 10:47 AM)PaddyB Wrote:(2017-05-03, 05:34 AM)Littlechay Wrote: Sounds great. Looking forward to trying it.
On the case of my plotter I have an red illuminated button (momentary close). When I get an alarm condition the I illuminate the button via the above GPIO pin. I haven't connected it yet but the idea is to have another action which resets the alarm condition when the button is pressed. Ideally the first press will silence the buzzer (also activated via a relay on the GPIO pin) and turn the light off - I would then like a second press to completely clear any existing messages.
Is there a way to implement this second press situation in OP ?
Maybe node-red would be a way to do this?
I don't know. Can Node-Red interact with physical controls?
Or are you suggesting that Node-Red get passed the physical button action from OP/Signal K and then return an action to OP to clear the messages?
I haven't played with Node Red much yet. I need to get all my instruments accurately reporting into Signal K first before I get fancy.
