Reachy 2 – “Connection failed” Error in Teleoperation (Meta Quest 3)

Users VR Tele-operation
1

Hello everyone,

We are experiencing issues with the teleoperation software of our Reachy 2, which we purchased last year, and we would appreciate some guidance.

Setup

  • Robot: Reachy 2

  • VR headset: Meta Quest 3

  • Teleoperation application launches correctly

  • The robot is reachable over the network

Issue Description

We can:

  • Launch the teleoperation application on the Meta Quest 3

  • See the VR environment correctly

  • Enter the robot’s IP address

  • Successfully ping the robot from the network

  • Access the robot dashboard without any issues

However, when attempting to connect through the teleoperation app, we consistently receive the following error:

“Connection failed”

Additional Information

  • The robot responds properly to ping requests

  • The dashboard is accessible

  • The issue started in the past few weeks (it was working previously)

Is there any specific configuration step, network requirement, or software update we might be missing?

Any help or guidance would be greatly appreciated.

Thank you in advance.

Best regards,
Raúl Gómez
CARTIF Technology Centre

2

Hi @raugom,
Thanks for all the details you provided.
Could you please give us some additional informations :

  1. a screenshot of where you are blocked in the app
  2. Are you using the executable app or are you launching it from Unity ? If you are using the app, which version are you using (written below the “Connect” button in the first screen when you launch the app) ?
  3. Could you verify the robot and the computer with the teleoperation app on the same network ? (If you can ping it, then yes, but I don’t know if you’re using the same computer for the remote operation application and the ping)
  4. Did you do any updates of the app, on your computer or on the Meta app between when the teleoperation was working and now?
  5. Are you using the alias reachy2-pvt03.local in the app ? If so, could you try to put the actual IP address (you can find it in the dashboard, section Network) ?

Claire

3

We had the same description, but we managed to get Reachy2 working. I followed the Github repo ( GitHub - pollen-robotics/Reachy2Teleoperation: Unity app for teleoperating Reachy2 · GitHub ) instructions step by step and made corrections when needed.

Our culprit was the GStreamer installation. The Reachy2Teleoperation repo has links to GStreamer Windows Runtime and Development Files installers, but the latter link is broken. The Reachy2Teleoperation is supposed to use both GStreamer installers. If the link to one is broken in the repo, then it is possible the link is broken in the installer as well.

We went and chose from here our Windows installation because it had both of the installers: https://gstreamer.freedesktop.org/data/pkg/windows/1.27.90/msvc/

Then I just made sure the GStreamer was in the PATH environment variable, and the Teleoperation started working.

1 Like