Problem with connecting to ATEM

[Ystum]

I did no changes in network and did not update anything but Companion doesn't connect to ATEM anymore. Debug file:

system: ** Connection started **
Starting up module class: ut
Sentry disabled
Module-host accepted registration
debug: ATEM changed model: 0
ThreadedClass (9138) Skipping exit handler registration as no exit handler is registered
debug: reconnect
debug: reconnect
debug: reconnect
debug: reconnect
debug: reconnect

I tried different builds and still have this problem. What can I do?

It works fine on mac with M1 but doesn't work on all PCs with intel chipsets=(

[ttiasg]

Same Problem.

[kklopmann]

Same Problem

[ghowardjr]

I have the same problem. Does anyone have a solution yet?

[Julusian]

I have added a section to the HELP for the most common cause of issues. It will be available inside of companion in some future release. https://github.com/bitfocus/companion-module-bmd-atem/blob/master/companion/HELP.md#diagnosing-connection-issues

There are 1000s of users of this module, with only a handful having issues, it is most likely a misconfiguration rather than a bug in the module.

If that does not help, post back here.

[iRodman]

Well I have the same problem and I have the ATEM connected with a USB cable to the PC running companion!!

[snappy232323]

Same Issue. I plugged in a new stream deck pedal in Mac and now my companion buttons are not working on stream deck plug in . Everything appears to have connection.

[Julusian]

Well I have the same problem and I have the ATEM connected with a USB cable to the PC running companion!!

@iRodman what happens when you follow the new help section? https://github.com/bitfocus/companion-module-bmd-atem/blob/master/companion/HELP.md#diagnosing-connection-issues

Same Issue. I plugged in a new stream deck pedal in Mac and now my companion buttons are not working on stream deck plug in . Everything appears to have connection.

@snappy232323 I don't see how that relates to this thread

[smadds]

Definitely a V3 issue - I had a copy of 2.2 on a RPi and that connects every time. Nothing I tried with V3.1 on Win10 worked

[Julusian]

Definitely a V3 issue - I had a copy of 2.2 on a RPi and that connects every time. Nothing I tried with V3.1 on Win10 worked

I can't explain why that would happen. So little has changed in the core connection code that would explain that. Any error logs? What about 2.2 on Win10 or 3.1 on pi? What model atems are you using?

I have had zero issues using a 2ME, 2ME production studio 4k, 2me constellation hd, tvs, mini, mini pro iso, mini extreme iso and probably more, on win10, win11, macos and linux. I havent tried every combination of those, but everything I have tried has worked fine.

So if you could try different versions on the same pi and win10 machine (ideally without changing anything else about what they are running), that would be really helpful to rule out some possible causes.