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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long-Term Node Red development #444

Open
1 of 3 tasks
philipp2310 opened this issue May 10, 2021 · 0 comments
Open
1 of 3 tasks

Long-Term Node Red development #444

philipp2310 opened this issue May 10, 2021 · 0 comments
Labels

Comments

@philipp2310
Copy link
Member

philipp2310 commented May 10, 2021

This Epic is used to collect long term ideas regarding the Node Red integration

Feel free to add your Ideas as edit or comment!

馃挷 High effort
馃崕 Low hanging fruit
馃悋 Potential rabbit hole, high effort unforeseen consequences
馃敟 High priority
鉂勶笍 Low priority

General

  • A node for getting a set of devices. These can be used as an input to spare the end user from using UUIDs
    example:
    getDevices(name="Bathroom_Temp") -> Telemetry_get("temperature", device) <"18掳"
    getDevices(name="Bathroom_Window") -> Telemetry_get("contact", device)==False -> Telemetry_get("lastChanged", device)>"20 min"
    => say("What about closing the window again?")

Alternatively: Dropdown/nameInput for all devices build in as a NR "slot type"

  • 鉂勶笍 Re add the "name" field to nodes so that the user can rename each node once deployed to the flow. EG: user can rename "say" node to "speak the temperature". Allows for clarity in reading the flow.

Skills

  • Skill provided hooks - always as an Alice mqtt event?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant