[BUG] Not connecting to atem

[m2bcTraining]

Is this a bug in companion itself or a module?

• [X] I believe this to be a bug in companion

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the bug

After the latest update, the connection from companion to atem is not working anymore. He tries to connect but nothing happens. After several newstarts it is working.

Steps To Reproduce

1. Go to connection
2. See the atem configuration
3. Try to reconnect but nothing happens

Logs: system: Connection stopped system: Starting Connection from "C:\Program Files\Companion\resources\bundled-modules\bmd-atem\main.js" system: Connection started Starting up module class: la Sentry disabled Module-host accepted registration ThreadedClass (3352) Skipping exit handler registration as no exit handler is registered

Expected Behavior

Connection is working

Environment (please complete the following information)

- OS: Windows 10
- Browser: Chrome Version 119.0.6045.124 (Offizieller Build) (64-Bit)
- Companion Version: 3.1.2 (3.1.2+6243-stable-05c37a10)

Additional context

No response

[rapPayne]

Same problem here on MacOS Monterey 12.7.1

[Markpre81]

is there no solution till now?!

[Nickish90]

Has a fix for this bug been released? I have a Constellation 2M/E HD running 9.4 ATEM Software Controls. Version 3.3.1 on Companion. Cannot get ATEM to connect to Companion.

[Julusian]

Have you checked the section of the help titled 'Diagnosing connection issues'? https://github.com/bitfocus/companion-module-bmd-atem/blob/main/companion/HELP.md#diagnosing-connection-issues

There are tens of thousands of users of this module, and only a handful have this 'bug'. So if there is in fact a problem, and this isn't misconfiguration, this wont be quick or easy to diagnose and fix.

[dragon788]

I have a suspicion that this is related to mDNS or similar and a broadcast storm on the local network. I had a macOS Companion instance and had imported the exact same config (IPs/buttons/etc) to an arm64 Linux machine running Companion-Pi and for some reason while the Atem software worked from the Mac and Companion on the Mac could also communicate with one of my two Atem devices, the arm64 one kept sitting in the connecting status, but even after restarting the Atem and the Companion-Pi instance it wasn't showing as being connected, but I was actually able to send a few commands via a StreamDeck attached to the Companion-Pi, so it seems like there was a disconnect between the "(m)DNS resolution" (using the mDNS/Avahi/Bonjour hostname) and the actual IP address that I'm betting is used for sending the commands rather than the DNS name. The IP hadn't changed so it makes sense that it worked even if the hostname wasn't available on the network for some strange reason. Eventually after a few more restarts of the Companion-Pi and disabling some other services