Okay that’s good to know.
What about this? 
In other words, Device #1 is set for the full range of 0 to 100, but the user of Device #2 is only hard enough at the moment for a range of 0 to 50. Will the user of Device #2 be able to adjust their personal range as necessary with the buttons, the app, or the website?
I also downgraded back to FW3 just to compare and for me it hits the bottom. It’s clearly nothing in the way as I don’t use a hands free cup and hold the handy in my hand.
I tested it and upgraded back and forth between FW4 and FW3 and it only happens on FW3, but did not before I upgraded to FW4. I also tried moving the stroker to the top and running the initial configuration on the app.
Here is a (very) short video of the issue:
This happened when using the remote on the app and setting the velocity to 100 and range to 0-20. Although I first noticed it with this script here: https://discuss.eroscripts.com/t/cock-hero-finisher-deluxe-fallenone-wine69-normal-hard-version-odyssey-scripts-hand-made-script/236215
Is there any way to fix this? I did not find a “calibrate” option in the app. Only the initial configuration.
Hello, is it possible for us to have a local server under Docker (in a github repository), in case your servers are crashed or not available? is this planned?
Will the API for firmware v4 be available like v3?
Hey is there somewhere we can get a full overview of the new controls? It took me awhile to figure out how to set it to a pure bluetooth that will work with scriptplayer by holding up on the dpad and the wifi/bluetooth/manual swap button at the same time. Now hitting right on the pad seems to change stroke length. This has been frustrating to figure out the new controls. Are they posted anywhere?
You could adjust the mechanical limits (possible in 4.0.12 or later through the onboarding app), but that is not a smooth method. We plan to implement HSP through device link (channel API). This will allow you to send a scripts on the fly and can be a simple up down script or more advanced. With HSP, you should be able to do as you describe.
Hmm, what FW version are you one now (excact version)?
I recommend you to update to FW4 and use the calibration feature in the onboarding app to fix this.
Can you reach out to support for further assistance?
API v3 will only support FW4. Here is the docs for the new API: Your connected workspace for wiki, docs & projects | Notion
Local server support is on the road map but not a priority. Our first mission is to create a smooth user experience (including uptime) and a simple and rich developer experience. Remember that we are a small player in this industry. We have to pick our battles carefully. Even the limited BT support we have today causes confusion and costs in customer support.
This forum seems to think we are a much bigger company than we are. We have 2 SW developers (including me). In comparison, Lovense has 500+ employees.
But I hear you, and we should do whatever we can to empower cool apps.
@personainterest :
Yes, here is a support page dedicated to FW4: What's new in Firmware 4? | Ohdoki Help Center
Handy FW 3.2.3+c1ddbc7e
I disliked that the FW4 ignores points it can’t reach, while FW3 goes as far as it can for the point, so I wanted to keep FW3 for now.
Okay, did the calibration and the upper limit was set to 109 and some instead of 110. After downgrading the issue seems gone. But I’m not sure about that yet. Before there were some situations when it needed some weight in it to show the issue. I currently only use official handy sleeves so it’s not that I put more weight on it than is supported.
Another topic: Why is the handyverse app no longer supported, but only the handy onboarding app for FW4?
When I try to start the handyverse app now it just shows that it’s no longer supported and gives a link to the new onboarding app and the alternative selection to use the old app in a browser. Just yesterday I still could use the old app.
As FW4 is still in beta I think it’s not a good choice to force people out of the FW3 app.
Have you tried version 4.0.13 of the firmware? Points are no longer skipped as they were in previous versions.
Regarding the Handyverse app: Unfortunately, Google has taken it down. The app was essentially a website wrapper, but the website is still available at old.handyfeeling.com. You can also download the APK if you’d like to use it as an app, or you can access it on iOS. For more information, click here: https://www.reddit.com/r/theHandy/comments/1i26ja5/regarding_handyverses_unavalability_in_android/
tried FW 4.0.13 with DeoVR on SLR and custom Scripts today and had no issues at all.
Just FYI, I upgraded to the latest version of FW4 since SLR is updating their system tools.
I experienced a few errors:
–When I dropped out of a PMV hosted on SLR (using the DEO app on a Quest 3), the handy kept moving to the beat (previous funscript was still running), and even when I tried starting other videos, it kept running the prior script.
I tried resetting it by using the power button, but I had to unplug the power cord to get it to recognize scripts again.
–In another video, when I skipped ahead, the script stopped working and I had to unplug the Handy and sync it again to get it to work.
I downgraded to FW3 and it seems to be working again.
What I liked:
I really liked the instant start for scripts. Took me by surprise a couple of times.
Other info:
My handy is about a year or so old.
I didn’t try the FW4 equipped Handy on any other app or computer, just the Quest 3
WOW!!! I’m here on this thread looking for help because that’s EXACTLY what happened to me. Mine starts kind of OK, but after intense sessions (or some scripts that never had issues), it hits the border pretty hard! I tried offsetting it little by little (%) but sometimes it still would hit the damn plastic border 
I’ll try this! Thanks for confirming it did work for you!
Sorry, but actually - just as I suspected in FW3 the issue still came up sometimes, despite the calibration.
I currently just use FW4, but it is kind of disappointing that one can’t downgrade to the “stable” version without issues. If I would read the thread now and not having updated yet this would prevent me from trying out the beta.
Maybe I’ll try to contact the support.
i use script player, latest beta fw 4 version. can confidently say i had all those issues as well, especially the script crashing the handy till replug, has happened to me like atleast 5 times, so its def the fw, didnt happen on priory fw4 versions nor fw3, my handy is about 1.5 years old, and i have reverted back to fw3 twice times in the past if thats at all helpful
Hi
Thank you for the feedback.
What version did you have when it failed? It will help us debug faster:-)
For me, it was the latest version available on 3/6/2025. It was the first time I updated from 3 to 4.
Hoho! In that case you guys are doing even more amazing job on hardware, software and support. You might lack behind with marketing, but there the sheer difference in amount resources is crucial I guess. Shit, I wonder what 300+ of those 500 do - invent new dildo shapes? 
Same here with Scriptplayer 1.2.2. But It happens rarely for me and is not really reproducable as far as I can see. It just happens sometimes.
Handy FW 4.0.13+09d7e70a