400 bad request - error sending csv to handy / getting script from SLR server

slrdigital

Seeing this error frequently in DeoVR with Quest 3. Happens randomly in the middle of a script and causing the handy to loose connection. Once it gets into this error state it continues to fail on every video / script after showing "Handy Connected" it eventually times out and shows the same 400 "bad request" error. Video playback continues to work fine when this happens, but the handy connection remains broken.

1.) Is anyone looking into this issue?

2.) Anyone aware of a fix for this beyond completely rebooting quest + handy and re-syncing?

rerun119

slrdigital I also have the same thing happen over and over. I get a bunch of different messages, sometimes it still works. Sometimes you can hit the disconnect button on the handy and them reconnect without having to go to the setting in DEO. The worst one is the one that you point out because you have to disconnect and reconnect and go to setting to re-sync.

All of these take time with the scene paused and immersion is completely lost. It happens to me about every 5 minutes. I think it has to be caused on SLR end because the handy stays connected, plus it doesn't happen on other players nearly as much.

JonWlck

I have this issue as well. Solving this issue was to unplug and plug the handy and restarting the connection in the deo settings

RealcumberScripts

JonWlck - unfortunately I've encountered it as well, and usually unplugging and restarting deovr once solves the issue - of course ideally we would want there to be no need to ever need to restart anything

Will hopefully be able to resolve this for you guys for less time fussing and more time enjoying - thanks for bearing with us!

raser1

Hey guys, we've been working on updating the Handy connectivity.

The goal is to reduce the number of issues and handle errors without having to reboot the Handy and/or Quest.

I've been testing it and so far it's looking really promising.

rerun119

raser1 I don't know if this has been updated yet but I haven't had as many problems the last couple of days. Knock on wood.

raser1

Hey, we're still working on it, but hopefully we can push it out soon.

So far in testing it has been working really smoothly for me. Sometimes there are still errors coming from the Handy itself, but in case that happens, then the connection should be re-established automatically.

We also had reports from sync issues, those should be fixed by the upcoming update as well.

kashitsusan

raser1
Is there any new information about the handy connection problem?

raser1

Yes, the update for Handy is finished, but it didn't make it in time for the recent update unfortunately. It will be included in the next release.

rerun119

raser1 I had this happen 15 times the other night. It hasn't been as bad lately but when it is bad is horrible.
The worst part about it is that it don't try to reconnect. You have to go to the setting and reconnect every single time.

raser1

rerun119 We think this is related to the old version of the Handy API. We've updated it to V2 so hopefully that will solve these issues.

Error handling has also been greatly improved, so manual intervention should no longer be necessary. If an error occurs, it should be able to automatically resolve and reconnect.

rerun119

raser1 When did you update to V2? This happened 4 days ago.

Kieshi

rerun119 It is not released yet, should be released early next week.

raser1

rerun119 Yes @Kieshi is right, the update hasn't been released yet. Sorry for forgetting to mention that. 🙂