I bought the PowerBlow last year when they were running promotions on it, and I cannot believe we haven’t made any progress on actually getting this thing connected to any (non-proprietary) player.
At this point, if anyone could give me the slightest push in the right direction I’d almost be willing to do it myself. I’m a python programmer (data scientist) for my job, but have enough C experience to at least make some progress on this. Is anyone else already working on this, or does anyone have some advice where I can get started?
Only XToys.app seems to support Kiiroo PowerBlow. Wondering why no Buttplug.io support still. I would gladly implement it if I was able to sniff the protocol from XToys.app. But I have not been able to do so. XToys.app javascript code seems to be a bit obfuscated.
Unfortunately, it can only be connected to the FeelConnect and Haptics Connect app.
If anyone has information on how to connect it to a local scenario/script in the MultiFunPlayer app or to Intiface Central, please provide links or instructions.
App FeelConnect has an option for activation via clap/sound. Perhaps there’s a way to write a script that converts commands or signals into sound cues, which can then be transmitted exclusively to the microphone. It’s not the most elegant solution, but it’s the only idea that comes to mind for now. Might be worth exploring until a proper integration is available.
Sex like real kinda let us connect and use it as intended idk how they did it so poorly it is kinda just max on or off and the timing when it triggers don’t do it any favors and it never seems to vent properly = not getting the breathing feeling of it contracting then releasing
I found it too correctly work with feelxvideos subscription through feelconnect 3.0 app and I think also adulttime. feelxvideos has a free month somewhere if you look hard enough. there was 2 great videos there. leigh raven blowjob and an older lady one.
Currently, there is no direct connection between xToys and MultiFunPlayer (MFP), but there is a workaround that allows you to synchronize them manually.
Method to Sync xToys with MFP
This method works by launching scripts in both programs simultaneously.
Automating script playback through event triggers (e.g., monitoring log events).
If an automated solution is needed, further testing or an external API bridge might be required.
Maybe someone in the community will find a better way to integrate them.
This has always been the issue with the PowerBlow. It connects to virtually nothing! And the things it does connect to, never sync well with the Keon. I’ve always found it fairly useless and not worth the trouble.
But it works with that xToys app! Simple and straight forward. I used it today for the first time in about six months and it worked great.
I’m attempting to connect MFP (MultiFunPlayer) to xtoys.app WebSocket server, but I’m running into the following errors:
SSL Connection Issues: I get an error stating that the SSL connection couldn’t be established, with the inner exception pointing to “RemoteCertificateNameMismatch” and “RemoteCertificateChainErrors.”
Connection Terminated Unexpectedly: After a failed connection attempt, the WebSocket throws an exception stating: “The remote party closed the WebSocket connection without completing the close handshake.”
I tried connecting through port 12345 and 9000, but the issue persists. It seems like there could be a certificate mismatch or invalid certificate, but I’m unsure how to resolve it.
Has anyone encountered this issue before while connecting MFP to xtoys.app or similar WebSocket servers? Any advice or suggestions would be greatly appreciated!
Not sure if relevant but I encountered an issue trying to connect intiface and a videoplayer at the same time to mfp. The issue was I had them both connecting on the same port so whenever intiface tried to connect it would self terminate the connection since it was being used.
Probably irrelevant to your issue but its something similar with self terminating connections.
They closed the PR without merging it, so they probably aren’t going to add it to Initface. Initface is just the client, not a device manager. That said, the code looks good to go – it just needs to be integrated somewhere that makes sense
I’ll keep looking into it though. Thank you!
