[BUG] Internal Commands not working

[mryanbigscreen]

Make sure you're on the latest stable or beta build

• [x] I have tested this on the latest stable or beta release

Is this a bug in companion itself or a module?

• [x] I believe this to be a bug in companion and not a specific module

Is there an existing issue for this?

• [x] I have searched the existing issues

Describe the bug

We have a streamdeck running via companion on a PC. The streamdeck is controlling a novastar LED controller via hex commands.

The hex commands are working, but all of a sudden the internal commands are not. For example internal: surface: increment page number etc.

I have also tried this through the web gui and get the same result. I have re-scanned USB etc.

Thanks

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

- OS:
- Browser:
- Companion Version:

Additional context

No response

[Julusian]

What version of companion?

Did you change anything that could explain this?
Perhaps the actions are set with a specific streamdeck serialnumber, and you are using a different streamdeck?

I have also tried this through the web gui and get the same result

Through an emulator? Without knowing anything about which actions you are using or how, that could be expected.

[mryanbigscreen]

Version 4.1.4.

Did you change anything that could explain this? Perhaps the actions are set with a specific streamdeck serialnumber, and you are using a different streamdeck? <

Nothing has changed since installation. The streamdeck is the same.

I have tested using the 'test' button. Such actions are 'internal: Surface: Increment page number' & 'internal: Surface: Decrement page number'.

These previously worked without an issue.

Thanks

[Julusian]

I have tested using the 'test' button. Such actions are 'internal: Surface: Increment page number' & 'internal: Surface: Decrement page number'.

Are the actions using the specific serialnumber of your streamdeck?
If so, try changing the selected surface to something else then back to the correct thing. Maybe it has become unlinked somehow.
If not, then it is expected that the test buttons wouldnt work, as there is no 'current surface'