You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
, andtrigger
, 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:
all the best
The text was updated successfully, but these errors were encountered: