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

Difficulty in determining control names for components #7

Open
rafaelcorsi opened this issue Nov 25, 2023 · 1 comment
Open

Difficulty in determining control names for components #7

rafaelcorsi opened this issue Nov 25, 2023 · 1 comment

Comments

@rafaelcorsi
Copy link

I understand that this feature is still in beta, but I'd like to note that there currently seems to be no way to identify the control name for a given component. For instance, I'm trying to trigger the motion signal on the PIR motion sensor from a test scenario, but I haven't been successful.

I've attempted several keywords such as motion, pressed, emotion, and trigger, but none have worked. It looks like that repository that implement this components is private, so no way to look at the source code.

Example:

  - set-control:
      part-id: pir1
      control: trigger
      value: 1

  - set-control:
      part-id: pir1
      control: trigger
      value: 0

all the best

@urish
Copy link
Contributor

urish commented Nov 25, 2023

Thanks, yeah - we definitely need to improve on that front. The issue is that most interactive parts do not yet implement the controls internally. The implementation is pretty simple on our end, we just need to decide on which names make sense, then implement and document them.

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

2 participants