Open moverholt31 opened 5 months ago
Are you sending rosstalk from the dashboard to control companion, or is companion sending the rosstalk?
Is there anything in the companion log when this fails?
We don’t use rosstalk. We’re just changing some routing through the mk-router
On Sat, Feb 10, 2024 at 8:36 AM Julian Waller @.***> wrote:
Are you sending rosstalk from the dashboard to control companion, or is companion sending the rosstalk?
Is there anything in the companion log when this fails?
— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-rossvideo-nkrouter/issues/5, or unsubscribe https://github.com/notifications/unsubscribe-auth/BF6MZU6545SNUFBOE6RPIWLYS6AYNAVCNFSM6AAAAABC4LUKL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGAZDEMJQGQ . You are receiving this because you authored the thread.Message ID: @.***>
Oh right, its a module you are using. Ill transfer this to the module repository then
Is this a bug in companion itself or a module?
Is there an existing issue for this?
Describe the bug
We have several triggers set up to change some routing in our Ross Dashboard Router. These triggers are no longer working after updating to 3.2.
Steps To Reproduce
No response
Expected Behavior
Router changes aren't happening any longer after update to 3.2
Environment (please complete the following information)
Additional context
No response