Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add input implementation #23

Open
josiah-tesfu opened this issue Oct 27, 2023 · 0 comments
Open

Add input implementation #23

josiah-tesfu opened this issue Oct 27, 2023 · 0 comments
Assignees

Comments

@josiah-tesfu
Copy link
Contributor

josiah-tesfu commented Oct 27, 2023

Currently, any message can trigger the node as input. A more effective and appropriate implementation would have the input dynamically configure the node settings.

Node-RED uses msg.payload and msg.topic to configure input, where msg.payload is used for main data and msg.topic is used for specific sub-categories/ actions. Nodes such as 'change', 'function', or 'switch' can further be used to change node configuations dynamically. For example, if the current node is being set based on temperature change from a temperature node, the temperature node might have a msg.payload set to the temperature. A function node could then translate 'above 25 degrees' to the current node's specific configurations.

Potential input settings for LED:
msg.payload: On/ Off

Currently, the LED node has an option to either configure input from the editor or from input received. These should both be an option and this dropdown configuration should be removed.

@josiah-tesfu josiah-tesfu self-assigned this Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant