exred_node_suppress v0.2.0 Exred.Node.Suppress
Suppresses or filters incoming messages for configurable time periods.
###Inputs
topic :: string
if message suppression starts when triggered then a message with ‘_START’ topic triggers the suppression
otherwise topic is ignored
payload :: term | number
if suppressing a band then payload needs to be number (it’ll get compared to the less_then and greater_then limits)
Link to this section Summary
Functions
Returns a specification to start this module under a supervisor
daemon_child_specs/1 needs to return a list of child specs. These child processes will be started under the DaemonNodeSupervisor
fire/1 is called when the user clicks on the play button on a node in the UI (and with that triggers a ‘fire’ event). It should return a new_state
Link to this section Functions
Returns a specification to start this module under a supervisor.
See Supervisor
.
daemon_child_specs/1 needs to return a list of child specs. These child processes will be started under the DaemonNodeSupervisor.
Callback implementation for Exred.NodePrototype.daemon_child_specs/1
.
fire/1 is called when the user clicks on the play button on a node in the UI (and with that triggers a ‘fire’ event). It should return a new_state.
Since this has access to the node’s state it can be used to implement user triggered actions like logging the state, sending messages from the node or creating debug events that are displayed in the debug tab in the UI.
For an example of how to use it see the Trigger node.
Callback implementation for Exred.NodePrototype.fire/1
.