Since this is my own use case here's an example of how this can be used from Node-RED for doing a scene change in OBS. I like to have everything as a separate item because with this modular approach it's easy to create new combinations from this: invoke a difference OBS instance, a different method, with different parameters, everything can be just put together with a few clicks. The scene change call looks like this:
From left to right: "My Scene Name" is the input parameter, this is the scene we want to switch to. "SetCurrentScene" is the method we want to invoke. "OBS Main" is the name of the OBS instance we want to address. And "OBS Control" is a "http request" node that does the actual HTTP call. To have it this modular way it has "obs.method" and "obs.instance" configured as dynamic request parameters, the settings look like this:
The item "OBS Main" sets the parameter "obs.instance" like this:
The item "SetCurrentScene" sets the parameter "obs.instance" like this:
This part will be the same for all calls to the tool, just change the name of the method and the instance you want to call according to your needs. Then, many methods need addtional parameters. You have seen that we configured the "http request" node to get query parameters from the payload, so for SetCurrentScene we need to put the "scene-name" parameter into the payload like this:
Note that this string is enclosed in quotation marks. This is important, since the corresponding JSON parameter for obs-websocket is a string and therefore needs the quotes (unlike numbers or boolean values).
This is just for the sake of this example, of course you can also dynamically feed in the scene name from other logics you might have. In this case make sure that you don't have any remaining payload items from previous nodes, as they would also be sent to OBS, causing the call to be rejected.
And again, remember the quotation marks. If you get the scene name from a field that doesn't have them, you can easily add them using a mustache syntax template node like this:
And that's it. If you understood how this works you should easily be able to do all other possible obs-websocket calls from Node-RED now just by copying and modifying these nodes.
Of course if you prefer you can do all the parameter settings in one single change node. I personally prefer this modular approach, since this way I can easily put new combinations of these together, also it automatically is a good visual documentation of what is done. But that's up to you...
