Getting help

Where to reach us

• Discord — fastest. Community support and updates.
• GitHub — bugs and feature requests.
• X — updates.

What to send us

A report we can act on beats a fast one. Include:

What you were doing — teleoperating from the app, running your own SDK client, in VR, mid-recording.

What you expected, and what happened instead. "It didn't work" costs us a round-trip.

The safety state. telemetry.safety at the moment it went wrong — ok, safe_hold, or latched. This single field routes the whole diagnosis, and a robot in latched is not a bug. See safety states.

The connection state. Where onConnState stalled — particularly whether it ever reached connected.

Your network. Corporate/university Wi-Fi, hotel, VPN, mobile hotspot? If a session won't connect, this is usually the answer. Relay credentials are now minted automatically at connect, so also tell us whether the session log showed TURN: using minted credentials or TURN: mint failed. See connection troubleshooting.

Whether it correlates with load. A peripheral that drops under load and is fine when idle is a power problem, not a software one.

Logs, if you can get them.

Things we already know

Don't spend your afternoon on these — they're expected:

• Low-res, ~15 fps video. It's the robot's power budget, not a bug. Why.
• perceive() returns null on real hardware. The on-Pi detector doesn't exist yet. Perception.
• A stall stops one joint, not the robot. By design. Safety states.
• Silence after joinCall() until someone at the robot accepts the prompt. By design. Audio.
• Sessions that hang at connecting on strict networks. You need the TURN relay path; the app fetches credentials for you at connect. Connection.
• A robot that latched itself with nobody touching it. Over-temp and over-current motor protection do that on purpose. Safety states.
• batteryPercent reading null. Means unknown, not empty — many robots have no monitor fitted. Telemetry.

If these docs are wrong

Tell us. A page that contradicts what your robot actually does is a bug, and we'd rather hear about it than have you work around it. Every page has an Edit this page link if you want to fix it yourself.