Videohub route button works only on specific destinations/sources...sometimes[BUG]

[esox87]

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I am using a stream deck with companion and a 40x40 Compact Videohub (the VH is on the latest update 7.0.8). Recently (seemingly after the last companion update 2.3.1) buttons for route on the Videohub aren't working consistently. I will push a button with multiple "Route" functions and only some of the routes change. Sometimes if I hit the button a few times in a row more destinations will change to the desired source but many of them will not change to the desired source. It seems consistent on which sources/destinations change and do not change. I have restarted the Videohub, deleted it out of companion, re-added it via fixed IP and I am still having the same issue.

It seems that if I make a companion button with only one "Route" function it works consistently. Even on the sources/destinations that do not work on buttons with many Route functions. A solutions to this could be that I just make an individual button for each source/destination change but then I would be makes pages and pages of buttons and I might as well just go into the VH software and change it myself.

Let me know if this makes sense. I can provide more info if needed.

Steps To Reproduce

Here's a quick video of what's happening.

20221121_140133.mp4

Expected Behavior

I expect all the "Routes" to change as the button specifies.

Environment (please complete the following information)

- OS:Ventura 13.0
- Browser: Chrome
- Companion Version: 2.3.1 (2.3.1+4641-v2-3.1-dc01ac7c)

Additional context

No response

[Julusian]

Have you tried adding some delays for the later ones? Enable relative delays, and give every 5th a delay of 40ms. Or try diferent numbers/spacing to see if it will work.

I don't know why this would have started recently, I cant see anything which could affect this as having changed since 2.2.1 or probably earlier.

I am thinking that either we are sending too much to the device at once, or some internal logic isnt handling so many being sent at once, and the delays should mitigate both of those scenarios

[esox87]

Thank you Julusian! I will try that.