Not sure if this is a bug, or I’m just missing something, but I’m trying to use one of the rotary encoder knobs to change Streamdeck group, and it’s just not working.
I created a set of groups, and in each group I create two actions, knob rotates left is set to select the previous group by name, and right to select the next, so if you continue to rotate the knob it should cycle through all the groups. A is set to go to B, B is set to go to C and C is set to go to A.
However rotating either way does not seem to do anything. The same action applied to a button works fine.
I believe that you need to call the BTT function
'Close currently open Stream Deck group'
before you can open a new group. Try that and see if it helps.
Things may have changed since I got my setup working, but I use the the Streamdeck+ touch screen swipe to change groups (and also the Streamdeck Neo touch points).
Looking back at my config I had actually set close group first. I haven’t had a chance to revisit it, but I’ll try setting some other actions and see if they trigger or not as it goes through the flow.
I recommend using the BTT HUD and/or javascript console logging in order to try and see what actions are happening. With both you have some control over the output if you want to show some state information.
You could also export a minimal example of your preset and share it here so we can take a look at the details of what you are doing.
I’ll have a play, unfortunately it appears there’s a bug in the latest versions so the Stream Decks aren’t working at all. Soon as I clear that I’ll dig back into this.
The latest version fixed the button issue and I think I know what’s going on.
I created a test profile (I’ve attached) and found that the knobs only seem to work when they are at the root level, if they’re in a group they don’t fire. The log shows BTT acknowledges the input, but does not trigger.
The test profile has two groups, each with a button to identify which one you’re in. Knob 1 does brightness, and works, knob 2 switches between groups at the top level, and that works. Knob 3 is set in each group to change to the other, and does not work.
Not sure if this would be a bug or just not implemented yet though.
I got this working in a bit of a roundabout way, as the touchscreen and knobs appear to need to be specified at the root level, not in a group.
I have a button for each ‘mode’ I want the Streamdecks in, and I created a variable so when that mode is selected, it also changes the variable to that name. Those buttons are set to always appear, and select the first group for that mode.
Then I create top level groups for each ‘page’ of options I want to select from under that mode.
Then at the top level I create a trigger for the knob I want to use for turning the knob right and create an if condition to match the variable name, followed by a cycle through multiple actions item.
Each item in this list closes the current group, and opens another for that mode.
Copy this trigger, swap to turning the knob left, then reverse the order under the multiple options.
Then when you press the button for the mode, the variable is set and the first page of buttons is displayed. When you turn the knob, the dial actions that match the variable are cycled through.
I think you are correct about knobs only working at the top level. I also would like to be able to swap knob functions in and out using groups. If you file a Feature Request on this I’ll vote for it.
The SD+ Touchscreen support is distinct from the knobs in that there is a “Touch Screen Configuration Group” item (found under the Stream Deck + part of the menu) that you can add at top level. This is a bit like a group/folder, but you can define a set of things to go on the touch screen in one of these and they will all be activated/display together.
The semantics of “Touch Screen Configuration Groups” are a little strange, because there is an Open trigger, but no Close trigger. (This seems like it could be improved!).
(Not sure that the behavior remains the same as it was when I started that thread, but have a look…)
I think maybe there are not that many BTT users who have SD+ and SD Neo models, as the amount of discussion around features specific to these models isn’t very high…
