[Bug]: 3.0.10 Cloud not working

[asdsh29]

Hi everyone,
I already asked in the TA Facebook group, but got no proper response on that.

I'm trying to get my M5atomMatrix working with my ATEM 2M/E Constallation over the cloud.
In the end I do not need any features like Aux tally or something provided with version 3.0.4 but I need those two pieces of hardware working over the cloud with the M5atom working plug and play. I've downloaded an older version of the TA listener code for the M5 and I got it all working with 2.0.16 but the M5 does forget which camera number it should listen to after restarting and I need to reassign every time in the TA UI. That is not working for me that way, cause my cameras are roaming all day so they will need to reboot and reconnect multiple times during production.

With TA version 3.0.4 and the latest published M5atom matrix code, the M5 got the ability to remember which camera it is supposed to be, the ATEM 2M/E connects also with my local TA server, the cloud server also connects to my local server and it also receives tally commands, but the "source" is not connected properly, showing a red label all the time. Connected clients then (web tally or M5 hardware clients) do not react on those tally commands.

My initial setup was setting up the local TA server on a Raspi 3+ and the clod server on an AWS server. Then I switched to a Macbook as a local server, AWS as cloud, and after that switched to Macbook as local and second macbook as cloud server running on a different internet line. Got the same behavior on all test environments.
Also tested with different "Sources", like vmix and osc. The cloud tally never connects to the sources running on the local Server, although it is receiving the tally commands.

So the bug I'm reporting is, that I don't get the cloud service working at all on 3.0.4.... or, I don't get the latest "official" release (which ist 2.0.16) working properly with the M5atom matrix(latest M5 release does not work atall with 2.0.16)

Does anyone have a solution for all that? I just want to have 2 cameras working on my cloud server with 2 M5 tally lights without reassigning them every time they connect.

I'm not complaining here about anything, sorry if it maybe sounded like that, I just want to find a solution. I'm very thankful that all this exists and appreciate all the work that is gone into it!
I hope someone can help me with that, or maybe some can confirm that issue at least.
Cheers,
Stefan

Version

3.0.4

Distribution

CLI

OS

Linux

What browsers are you seeing the problem on?

No response

If applicable, What Listener Clients are You Using?

No response

TallyArbiter configuration

No response

Relevant log output

No response

Error stacktrace (if applicable)

No response

[github-actions]

Hello there asdsh29 👋

Welcome to TallyArbiter!

Thank you for opening your first issue for the Tally Arbiter project. Tally Arbiter fosters an open and welcoming environment for all our contributors. Please adhere to our Code Of Conduct.

If you have more to contribute to this issue, please comment down below! We will try to get back to you as soon as we can.

[asdsh29]

[UPDATE]
Hi everyone,

I've just updated my instances of TallyArbiter to the latest version 3.0.10. I'm still having problems with the cloud.
The local and the cloud instance seem to be properly connected, the log of the cloudinstance is showing me the correct tally data in real time, but but the "Devices" in the cloud is not changing the tally state.

Is anyone else using the cloud service and having the same problem?

I will try to setup a local cloud instance and test if I can get it running.

[asdsh29]

[UPDATE]
I've just tested the cloud function running the server on a fresh install on a machine in my local network. Got the same problem. Tally state is updating in the log on the cloud connected device, but not in the 'Sources&Devices' section. Also Listeners are not changing tally state :(

[saschafoerster]

I have the same issue I guess, here my console output, when I switch from the startpage to the producer page:

TypeError: undefined is not an object (evaluating 'Oe(2).deviceBusColors[i.id].includes')
dX — main.b2e20b51ce8d45a1.js:1:460595
cI — main.b2e20b51ce8d45a1.js:1:63643
eF — main.b2e20b51ce8d45a1.js:1:70923
Z0 — main.b2e20b51ce8d45a1.js:1:72685
wI — main.b2e20b51ce8d45a1.js:1:72515
_I — main.b2e20b51ce8d45a1.js:1:72446
eF — main.b2e20b51ce8d45a1.js:1:71228
Z0 — main.b2e20b51ce8d45a1.js:1:72685
wI — main.b2e20b51ce8d45a1.js:1:72515
_I — main.b2e20b51ce8d45a1.js:1:72446
eF — main.b2e20b51ce8d45a1.js:1:71228
Z0 — main.b2e20b51ce8d45a1.js:1:72685
wI — main.b2e20b51ce8d45a1.js:1:72515
_I — main.b2e20b51ce8d45a1.js:1:72446
eF — main.b2e20b51ce8d45a1.js:1:71228
Z0 — main.b2e20b51ce8d45a1.js:1:72685
wI — main.b2e20b51ce8d45a1.js:1:72515
iF — main.b2e20b51ce8d45a1.js:1:72477
II — main.b2e20b51ce8d45a1.js:1:72822
eF — main.b2e20b51ce8d45a1.js:1:71598
Z0 — main.b2e20b51ce8d45a1.js:1:72685
wI — main.b2e20b51ce8d45a1.js:1:72515
_I — main.b2e20b51ce8d45a1.js:1:72446
eF — main.b2e20b51ce8d45a1.js:1:71228
Z0 — main.b2e20b51ce8d45a1.js:1:72685
wI — main.b2e20b51ce8d45a1.js:1:72515
iF — main.b2e20b51ce8d45a1.js:1:72477
II — main.b2e20b51ce8d45a1.js:1:72822
eF — main.b2e20b51ce8d45a1.js:1:71598
Z0 — main.b2e20b51ce8d45a1.js:1:72685
qP — main.b2e20b51ce8d45a1.js:1:73849
U0 — main.b2e20b51ce8d45a1.js:1:73921
detectChanges — main.b2e20b51ce8d45a1.js:1:74011
tick — main.b2e20b51ce8d45a1.js:1:126382
(anonyme Funktion) — main.b2e20b51ce8d45a1.js:1:127681
onInvoke — main.b2e20b51ce8d45a1.js:1:77504
run — polyfills.597b2302d01105b7.js:1:1992
next — main.b2e20b51ce8d45a1.js:1:127651
next — main.b2e20b51ce8d45a1.js:1:4742
_next — main.b2e20b51ce8d45a1.js:1:4422
next — main.b2e20b51ce8d45a1.js:1:4113
(anonyme Funktion) — main.b2e20b51ce8d45a1.js:1:7283
Ue — main.b2e20b51ce8d45a1.js:1:3862
next — main.b2e20b51ce8d45a1.js:1:7118
emit — main.b2e20b51ce8d45a1.js:1:75189
K0 — main.b2e20b51ce8d45a1.js:1:78497
xI — main.b2e20b51ce8d45a1.js:1:78915
onInvoke — main.b2e20b51ce8d45a1.js:1:77566
runGuarded — polyfills.597b2302d01105b7.js:1:2115

[peterfdej]

I have the same problem. For testing I defined on the local server a device. The device is visible on both the servers (on the cloud server with a cloud symbol). When I start the test mode on the local server, I see in the log of the cloud server the state of the device changing. When I look at the device on the cloud server, nothing happens. On the local server I see the device state changing.
A listener is connected to the cloud server, using the device from the local server. I see in the log of my device (TTGO_T listener) state messages appearing at each change, but in the message is no data of preview, program or aux.
I use version 3.0.10

[Jamesdtl8]

Same! Just set this up and it doesn't work :(

[peterfdej]

I did some testing again. Listener-client connected tot Cloud server. Added device on local server and connected the cloud listener on the cloud server to that local device.

Started test mode on the local server. On the local you will see the result at the device, on the cloud server not.

The logs in my listener-client show data:

but not the correct states.
Running the test mode on the cloud server, I got this in de the log of my listener-device:

Here are the id's of the device on the local server:

and on the cloud server:

[peterfdej]

Also chat function is not working between local server and cloud server, both ways.