Closed SloppyButDecent closed 2 weeks ago
It seems that is a problem on your side. I can connect without problems to the simulator (all versions). Do you use the correct IP and port number?
I’ve used 127.0.0.1:10606 and 192.168.2.140:10606, the latter of which is the one that is auto populated when the connection is added. On Sep 27, 2024 at 6:17 PM -0500, Dorian Meid @.***>, wrote:
Closed #24 as not planned. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
try 3000 instead of 10606
I’ve done that as well with no luck. Happens on both PC and Mac. On Sep 28, 2024 at 2:23 AM -0500, Phill Power @.***>, wrote:
try 3000 instead of 10606 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Can you successfully connect to WebRCS with a browser from the machine where Companion is running on? If yes, use the same URL that you use in the browser. Including the protocol, the ip or hostname and the port. That is also written in the help page.
Updating to the most recent companion fixed the issue. I was 1 version behind. On Sep 28, 2024 at 6:18 AM -0500, Dorian Meid @.***>, wrote:
Can you successfully connect to WebRCS with a browser from the machine where Companion is running on? If yes, use the same URL that you use in the browser. Including the protocol, the ip or hostname and the port. That is also written in the help page. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Unlike the other Companion module for LivePremier, I am unable to get this one to connect to the simulator session that I have open to test buttons and flows.