MiraBot now supports both Wi-Fi and Bluetooth LE in the same firmware.
You no longer need to reflash different firmware builds just to switch between Wi-Fi and Bluetooth workflows. The wireless mode can be changed later via MiraPlay Web over USB.
Wi-Fi supports UDP & WebSocket; Bluetooth LE supports direct app control and SLR-compatible workflows.
Firmware 1.3.0 also adds SLR-Compatible Bluetooth Mode.
When enabled, MiraBot can connect to SLR playback workflows via Bluetooth LE without any additional bridge software — a more direct connection experience similar to Handy.
Many OSR/Tcode setups are powerful, but connection workflows can still be fragmented.
This update aims to make MiraBot easier to use across different workflows without reflashing firmware frequently.
For example:
Use Wi-Fi for VaM
Use Bluetooth LE for MiraPlay AiO in no-Wi-Fi environments
Use SLR-compatible Bluetooth mode for supported SLR / DeoVR workflows
Switch modes later without reflashing firmware
Actual behavior may still depend on the player or platform, but the device connection workflow is now much simpler.
Shipping and Support
All newly purchased MiraBot S6 / Lite units now ship with Firmware 1.3.0 installed by default (Wi-Fi mode enabled by default).
Existing MiraBot S6 / Lite users can update through MiraPlay Web.
Since MiraBot and MiraPlay are updating quickly, some tutorial blog posts may lag behind the latest features. If anything is unclear, feel free to DM me here or use the Contact Us page on the official MiraBotX website.
Hey, thanks for the update. I flashed the new firmware, enabled the support for SLR and the device also connected successfully.
However, when starting a video on DeoVR with a script, the device does not move, even though it’s enabled. The manual stroking and return to base option in SLR do nothing.
Also: Is Bluetooth COM port planned? Because when enabling Bluetooth connection, one loses the possibility to connect wirelessly to MultiFunPlayer (which I need for example for HereSphere VR). As my device is not connected to a computer most of the time, it would be quite cumbersome having to disconnect it from power, move it to the room where my computer is, then connect everything including the USB cable, switch connection mode and then move everything back again.
SLR support via WiFi would be equally welcomed.
Hi,
Thanks for the feedback, and great to hear that the firmware update and SLR-compatible Bluetooth connection were set up successfully.
For the DeoVR / SLR playback test, please first make sure that your SLR plan includes script support. A regular video-only plan may not send motion data to interactive devices, even if the device itself is connected successfully.
You can also try testing the device with another supported control method, such as MiraPlay AiO or a basic manual control test, to confirm that the device responds normally outside DeoVR / SLR. If it still does not respond, reflashing the firmware once and setting the wireless mode again may help.
If the problem continues, please contact us through the Contact Us page and our support team will help check your setup in more detail.
Regarding Bluetooth COM port / WiFi connection options: with the current ESP32-based controller setup, MiraBot uses either WiFi mode or BLE mode at one time. The new SLR-compatible mode was added mainly to make direct SLR / DeoVR connection possible without extra software in supported environments.
We are still looking into ways to make the connection experience more flexible in future updates. For SLR control over WiFi, that would also require support from the SLR / DeoVR side, and we would definitely welcome that possibility as well.
Hi, thank you again for the detailed information and screenshots.
We tested the same SLR video with a similar setup on our side, and the device worked normally with both manual stroking and scripted playback.
At this point, it may be related to a difference in the local Quest / DeoVR environment or Bluetooth pairing or cache state.
To narrow this down, could you please try the following comparison tests?
SLR website direct Bluetooth test on PC
Please connect the device via Bluetooth from the SLR website and try the same scripted video, just to compare it with the Quest 3 / DeoVR test.
SLR Haptics Connect app test, only if the first test does not work
Please install the SLR Haptics Connect app from Google Play. Once the device is connected in the app, please try the “Control” function and check whether the device moves.
Before testing, please temporarily turn off any other nearby SLR-compatible toy devices.
Thank you for the update and for testing this further.
It is helpful to know that the device works with the Haptics Connect app. This means the device, firmware, and TCode / Bluetooth communication should be working correctly.
Based on the current information, we think the issue is more likely related to certain Haptics settings in Quest 3 / DeoVR, a cached device connection state, or a local permission state.
We are continuing to look into this based on your feedback, and we are also trying to reproduce the same situation on our side so we can better confirm the cause.
Please give us a little more time to continue checking this. Thank you for your patience.
Learn more about MiraBot
