Bekannte Probleme & Lösungen für humanoide Roboter

What this section is

Every page in this section is a list of problems that owners and developers have actually reported for one specific robot, with the fix or workaround where one exists. It is not a manual and not a review: an entry earns its place because more than one person hit the same thing and wrote it down in public.

How the data is gathered

A scheduled job runs once a week, every Monday, and reads the public issue trackers for each robot — both the manufacturer’s own repositories and the community drivers, SDK ports and simulators people actually run. Published research abstracts are checked too. A report has to clear a corroboration floor before it can be published automatically: it is measured by how many comments and reactions the original thread drew, and anything below the floor is held back for a human to review rather than posted.

Nothing here is written from memory. Every entry is derived from a document this pipeline fetched, and it carries the link to that document, so you can read the original thread and judge it yourself. Where a problem comes from a community driver rather than the robot itself, the entry says so, because a bug in a third-party port is not a defect of the hardware. Each entry is tagged with a category, how badly it affects use, and whether the vendor has fixed it, a workaround exists, or it is still open.

Robots currently covered

• Unitree G1 — 38 documented issues, updated August 23, 2026
• Unitree Go2 — 31 documented issues, updated August 29, 2026