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
When we enable the trigger, it starts the actions are working as excepted. When we disable the trigger we noticed that this trigger will occasionally fires the buttons in unwired format.
How our trigger works
Events - On any Button Press
Actions - internal: button: Trigger Press
I'm not sure where we can get the triggers logs.
Steps To Reproduce
Unclear. Seems to happen randomly.
Expected Behavior
Actions should not fire when the trigger has disabled.
Environment (please complete the following information)
- OS: Windows 10
- Browser: Microsoft Edge Version 116.0.1938.69 (Official build) (64-bit)
- Companion Version: 3.0.1 (3.0.1+6068-stable-a05a9c89)
Additional context
Trigger also fires multiple time even the trigger has enable. For that reason Reaper is going to stop the sequence.
The text was updated successfully, but these errors were encountered:
Could you try and figure out a STR?
I have tried to reproduce this but have been unsuccessful. I can't see how this could be happening in the code, so without a STR this is a bit stuck
Is this a bug in companion itself or a module?
Is there an existing issue for this?
Describe the bug
When we enable the trigger, it starts the actions are working as excepted. When we disable the trigger we noticed that this trigger will occasionally fires the buttons in unwired format.
How our trigger works
Events - On any Button Press
Actions - internal: button: Trigger Press
I'm not sure where we can get the triggers logs.
Steps To Reproduce
Unclear. Seems to happen randomly.
Expected Behavior
Actions should not fire when the trigger has disabled.
Environment (please complete the following information)
Additional context
Trigger also fires multiple time even the trigger has enable. For that reason Reaper is going to stop the sequence.
The text was updated successfully, but these errors were encountered: