Oh, this is just a private thing and I am not sending the data outside the local network. I got a Lovense Solace Pro recently but I noticed that toolchain I was using to connect it to VaM (ToySerialController+VaMSync) didn't actually set the position. Instead what was supposed to be the position was being translated as strength of thrust. Obviously this was very out of sync with the animation and not really the kind of immersion I was hoping for. And since I'm a C# developer, I figured I might be able to create a solution to that problem (really only for personal use).
I found out that basically, you can skip the entire toolchain you would normally use and could just use a VaM PlugIn to connect to the Lovense App, since it has it's own built-in REST-service. That way you can directly send Json commands to your toys. And instead of writing a whole PlugIn, I was planning on writing an add-on script for the ToySerialController. But that's where I hit the road block that lead to my original post here.
By now, I have abandoned modifying the PlugIn and instead I have written a bridge in C#. Small console program that runs a Udp-Server for ToySerialController to connect to, parses the data relevant for the Solace Pro and pushes it out as Rest requests to the Lovense App. That way I can directly update the position of the toy according to what's happening in VaM.
I'm still in early testing phases, messing around with settings and values, cleaning up the data I receive so I don't overwhelm the network or cause the toy to behave weirdly, but it looks like I am starting to get decent results.