companion-module-requests icon indicating copy to clipboard operation
companion-module-requests copied to clipboard

Teradek VidiU Go

Open wedwards22 opened this issue 2 years ago • 2 comments

Vidiu and Vidiu X will not work. Vidiu Go flashes on and off as if it can't make a solid connection to the device.

wedwards22 avatar Apr 24 '22 05:04 wedwards22

The Go probably uses a different protocol than the original and the X, both of which I had to reverse engineer.

josephdadams avatar Apr 24 '22 12:04 josephdadams

Yes, I think so. I don't know exactly how to fix it. But in troubleshooting, i enabled TLS/SSL and it completely kept it from connecting. When its on port 80, it bounces on and off. Let me know how i can help figure it out if you want.

On Sun, Apr 24, 2022 at 7:23 AM Joseph Adams @.***> wrote:

The Go probably uses a different protocol than the original and the X, both of which I had to reverse engineer.

— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-requests/issues/790#issuecomment-1107830457, or unsubscribe https://github.com/notifications/unsubscribe-auth/AY3VW4HR3SZJNPH43MMJKZ3VGU4KDANCNFSM5UFWWJNA . You are receiving this because you authored the thread.Message ID: @.***>

wedwards22 avatar Oct 11 '22 09:10 wedwards22

Has this been resolved? I bought the teradek vidiu X and am unable to connect, see error below, worst case scenario could i downgrade Companion to make it work? appreciate any help i can get, including reverse engineering connection to start and stop stream, that is all i need, i think teradek is using mqtt, but cannot connect to it...

system: ** Starting Connection from "/opt/companion/module-legacy/manifests/companion-module-teradek-vidiux/index.js" **
system: ** Connection started **
Starting up module class: k
Sentry disabled
Module-host accepted registration
error: Error initializing module: WebSocket is not defined

rihani avatar Sep 28 '23 13:09 rihani