search

wokwi / wokwi-cli

Wokwi Command Line Interface (for CI use cases)
MIT License
14 stars 5 forks source link

Difficulty in determining control names for components #7

Open rafaelcorsi opened 7 months ago

rafaelcorsi commented 7 months ago

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 commented 7 months ago

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.