'OBS Remote' Plugin Stopped Working After OBS Update?

O

OldMcCoy

New Member
Is anyone familiar with this OBS Remote plugin? It works with the "obs-websocket" connection in OBS.

I use it with Streamlabs Chatbot for viewers in the Twitch chat to be able to play a Media Source (video clip) in OBS. Example: !clip will trigger a specific video clip to play in OBS. (I have a list of video clips added as media sources in OBS so there are a lot of different ones the chat can trigger... !lol !wtf !gtfo, etc)

It works through Streamlabs Chatbot under Connections, then you enter the IP, Port, and Password and connect it with OBS.

The "obs-websocket" settings is still in OBS, although it looks like the Server Port and IP changed. I tried to enter the new Port and IP in the Streamlabs settings but it doesn't seem to be connecting. :(

It could be that it still works and I'm missing something that changed, or maybe it doesn't work anymore?
 
E

ECraigS

New Member
Having issues as well. From the log file:

19:04:34.038: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.xx.xxx]:59925

19:04:34.038: [obs-websocket] [WebSocketServer::onMessage] Client [::ffff:192.168.xx.xxx]:59925 appears to be running a pre-5.0.0 protocol.

19:04:34.039: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.xx.xxx]:59925` has disconnected with code `4010` and reason: You appear to be attempting to connect with the pre-5.0.0 plugin protocol. Check to make sure your client is updated.
 
J

jsnknght

New Member
I had the same problem with the chatbot not connecting to obs after I updated to ver 28. I think the chatbot doesn't like the 5.0 websocket that's included in obs 28, but can't be sure. I resorted to downgrading to the older version of obs and using the websocket 4.91 compatibility which can be found at the bottom of this github link. After doing so, the chatbot worked as normal. If you are set on using obs 28 you might have to migrate your commands to a different program. Hopefully streamlabs updates the chatbot to fix this. If they drag their feet I will probably start using another program for my commands as I will want to update my obs sooner or later. Sorry I can't offer further insight
 
O

OldMcCoy

New Member
jsnknght said:
I had the same problem with the chatbot not connecting to obs after I updated to ver 28. I think the chatbot doesn't like the 5.0 websocket that's included in obs 28, but can't be sure. I resorted to downgrading to the older version of obs and using the websocket 4.91 compatibility which can be found at the bottom of this github link. After doing so, the chatbot worked as normal. If you are set on using obs 28 you might have to migrate your commands to a different program. Hopefully streamlabs updates the chatbot to fix this. If they drag their feet I will probably start using another program for my commands as I will want to update my obs sooner or later. Sorry I can't offer further insight
Click to expand...
Thanks for the response, I submitted a support ticket to Streamlabs asking if they can do something with it.
 
You must log in or register to reply here.
Top