Soo i just discovered few multi axis scripts in my collection nice
MiraBot Lite – Wi-Fi Firmware v1.1 Official
The official Wi-Fi firmware is now available for MiraBot Lite.
If you’ve been running the BLE version and wanted more flexibility with software support, this release enables stable UDP-based wireless control over your local Wi-Fi network.
Supported Software
- MiraPlay AiO (v1.7+)
- Multifunplayer
- ToySerialController (VaM plugin)
- Other compatible softwares
Switching from BLE to Wi-Fi
If your Lite is currently on BLE firmware, you can flash the Wi-Fi version using the web-based firmware tool.
Flashing guide:
How to Restore & Update Your MiraBot Firmware
For New Orders
When placing an order, you can now choose your preferred wireless type:
- Bluetooth LE (simpler setup, no router needed)
- Wi-Fi (broader UDP software compatibility)
The selected firmware will be pre-installed and tested before shipment.
Feedback is always welcome — especially from those testing Lite with different software setups. 
With the new firmware with wifi, can it connect directly to Quest 3 through Heresphere? Thanks
As far as I can tell, not directly in the usual HereSphere setup.
The most detailed thread I found on EroScripts is this user tutorial by Husky:
In that post, the “Quest with any device over Wi-Fi” method still requires a Windows PC, with HereSphere sending timestamp data and ScriptPlayer / MultiFunPlayer on the PC driving the OSR. So based on that tutorial, Wi-Fi firmware does not mean a direct HereSphere → OSR connection by itself.
The workflow shown there is still:
Quest / HereSphere → PC → OSR
Sorry if this has been asked before, I don’t have time to go through the whole thread.
Does the MiraBot connect via bluetooth with Quest 3 for running scripts either via HereSphere or DEOVR?
I see setups like Quest 3 → PC → MiraBot (OSR device?) but I do not have a PC to use. So, can it be Quest 3 → MiraBot and use local video/scripts on the quest and/or online such as SLR?
This will be a big part of my purchasing decision.
Thanks.
Thanks for your question, this actually comes up quite a lot 
To be fully transparent, as far as I know, there isn’t currently any Quest 3 app that can handle VR playback + script sync + direct wireless control of OSR devices (including MiraBot) all at once without a PC in the loop.
That’s why most setups you’ve seen are still:
Quest → PC → device
That said, we’re actively working on our own Quest-side solution to enable a more direct Quest → MiraBot workflow with synced video and scripts over Wi-Fi/BLE. I can’t give an exact date yet, but it’s something we’re aiming to release in the near future.
In the meantime, there is another workable setup that doesn’t require a PC:
We’re about to release an update to MiraPlay AiO (around mid-April) with an improved Online Play / standalone script player. In this setup, MiraPlay handles the funscript playback and controls the device, while your Quest is used just for video playback (local or streaming like SLR). It’s not fully integrated yet, but it works quite well in practice.
If you do decide to go with MiraBot, we’re continuously improving the software side (especially MiraPlay) based on user feedback, and setups like this are exactly what we’re trying to make easier and more seamless.
I looked through your guide on how to connect VAM to Mirabot and the only way is through USB Serial, I tried connecting Mirabot to VAM through UDP and Intiface Central through wifi with no luck. UDP did work with MFP though. Can you provide a guide (or make it possible) to connect Mirabot wirelessly to VAM? Thanks.
Sorry！ we haven’t updated that guide in time.
The current guide still shows the older USB Serial setup, but MiraBot can also connect to VaM wirelessly through UDP when using the Wi-Fi firmware.
For VaM, you do not need Intiface Central for this. Please use ToySerialController’s UDP output directly.
Please refer to the screenshot below for the correct settings:
In ToySerialController:
- Set Select Output Target to Udp
- Address: mirabot.local
- Port: 8888
- Then click Start Udp
If mirabot.local does not resolve on your network, you can also try using your MiraBot’s local IP address instead.
Since UDP is already working for you in MFP, your device firmware should be fine. In that case, VaM should also work as long as ToySerialController is set to UDP correctly.
We’ve updated the guide. You can find it here
@Gesmax just ordered a MiraBot Lite order#16047. would have loved to buy a SR6. but low 
. got extremely lucky buying a ssd 4tb at $400 and 5070ti $700 on december. 
lol
Thanks for your order! The Lite is a really solid choice too. It has its own strengths, just like the S6. Hope you have a great time with it and enjoy the experience 
Hi, for the UK, recent orders usually arrive around 16 days after dispatch, and we normally ship within 2 business days after the order is placed.
For the Wi-Fi version: it supports UDP connection, so it can work wirelessly with OSR-compatible software such as MFP.
It does not currently connect directly to Quest / HereSphere / DeoVR in the same way as The Handy. At the moment, OSR-type devices usually use a setup like Quest → PC/MFP → device for DeoVR / HereSphere.
That said, we’re working on MiraPlay Web, which is intended to support a more direct Quest browser → MiraBot workflow for VR video + funscript playback. This is one of our upcoming software priorities.
My MiraBot S6 arrived this week. I tried everything, but it doesn’t work with EDI or FunscriptPlayer. It only responds (or sometimes doesn’t respond at all) when using a single axis, and completely ignores multi-axis scripts. Does anyone have any idea how to
[MountBatten] Avy & Oniichan’s Honey Moon v1.2 | Multi-Axis Update! - Software / Games - EroScripts
I’d suggest first testing the S6 multi-axis motion with MiraPlay AiO or MFP to confirm that the device and scripts are working correctly.
If everything works there, then it may be worth checking the EDI / FunscriptPlayer settings to see whether any option is limiting or overriding the extra axes.
I’ll also try to verify it on my side with the game you mentioned. If you’re willing, feel free to DM me with more details or screenshots and I’ll do my best to help narrow it down.
It works normally with MiraPlay AiO, ScriptPlayerPlus, and CubiLink – Live2D Motion Mapper for SR6. I checked the files and also tried the version available on the website, which improved the connection. However, it still doesn’t respond to scripts that use multiple axes. When I use EDI/FunscriptPlayer, it only responds if the script has a single axis, whether it’s twist or roll.
In short: it doesn’t work if there are files with the same name but different functions, such as:
video.pitch.funscript
video.funscript
However, it works if I delete all files with the same name and leave only one, regardless of the action.
It seems like it can’t merge multi-axis scripts and ends up not running any of them.
Thanks a lot for the detailed report, this is very helpful
We’re currently trying to reproduce this behavior on our side and identify the possible cause. Based on your description, it does seem related to how multi-axis scripts are being handled/loaded.
Once we have any findings or a fix, we’ll share updates here, as well as on our website and Discord.
Really appreciate you taking the time to test and explain it clearly.
Anything new?
Or is it a problem with my Mirabox?
Hi,
thanks for your patience while we checked this.
After testing this on our side, here is what we found:
1. EDI
For EDI, this appears to be mostly related to the setup/configuration for multi-axis scripts. EDI can support multi-axis playback, but the configuration is a bit specific, and it is easy to miss some required settings.
Since there isn’t a very detailed step-by-step guide for this workflow yet, we prepared a basic setup guide that you can follow first:
Please try the settings in that guide and see if multi-axis playback works correctly after that.
2. FunscriptPlayer
For FunscriptPlayer, after repeated testing, we found that the issue is related to compatibility between FunscriptPlayer and the current MiraBot firmware log output.
In short, the current firmware outputs more serial log information than FunscriptPlayer handles well during playback, which can interfere with multi-axis control.
Since we can’t be sure whether FunscriptPlayer will change this behavior on its side, we’re going to make a compatibility adjustment in the next MiraBot firmware update (v1.2). This update should reduce the issue and improve compatibility with FunscriptPlayer.
The new firmware is planned to be released soon.
Thanks again for reporting this clearly. It helped us narrow down the issue, and we’ll keep improving compatibility with different OSR tools where possible.
Quick update:
The rebuilt MiraPlay Web Beta is now available. I’ve posted the details in a separate ES thread here:
Also, MiraBot firmware v1.2 is now available.
This update improves support for MiraPlay Web wireless connection, adds WebSocket connection support, and includes compatibility improvements plus system log output adjustments for easier troubleshooting.
For the FunscriptPlayer multi-axis playback issue discussed above, updating to firmware v1.2 should resolve the problem.
If you want to use MiraPlay Web wireless connection with MiraBot, please update to firmware v1.2 or later first.
Firmware Flash Tool
Firmware update guide
If anything still doesn’t work as expected after the update, please share your setup details and we’ll continue checking it.
Has anyone figured out a good wearable solution to this? I tried using the hands3 wearable mount but since the mirabot lite is only compatible with 75mm vesa (the hands3 mount in 100mm vesa), I’ve had to get creative and begin messing around with vesa adapters. I don’t have a 3d printer nor CAD knowledge. Just a boner and a dream.
I add S6 to card , i got solace pro , hope it’s better.