Warranty & Safety Notice:
Warranty starts on receipt. Owner ships the unit to Unitree at own cost for diagnosis. Warranty is VOIDED by opening the shell, disassembly, or unauthorized modification. No consumer spare-parts channel; resellers provide first-level support only. G1 base ~8 mo; G1 EDU ~18 mo (EU 24 mo).
Sources:
https://www.unitree.com/mobile/terms/policyhttps://blog.robozaps.com/b/unitree-g1-review
Workarounds listed below are community-sourced and provided without guarantee.
motor/actuatorBlocks UseWorkaround Exists
Leg/hip/ankle motors overheat and force a shutdown
Symptom
Ankle-roll motors reach ~90°C within 5-10 min even near-idle; the left hip joint overheats after ~30 min of teleoperation and triggers an automatic system shutdown.
Affected
Reported under third-party whole-body controllers (NVIDIA GEAR-SONIC / Isaac-GR00T N1.7 on Jetson Orin NX). Unitree's stock controller keeps ankles at 30-45°C.
Fix / Workaround
Overheating is tied to aggressive controller gains, not always a hardware fault. Reduce Kp/Kd gains, adjust standing posture to lower static load, and prefer Unitree's stock controller for extended runs. If temps spike on the stock controller too, stop use and inspect — a genuinely failing actuator needs service.
No vendor fix documented. Community direction: the arm needs gravity/payload compensation for the added hand mass and lower torque limits; owners are still seeking Unitree's recommended PD gains for this pairing. Treat as a tuning problem before assuming hardware failure.
Robot ignores SDK commands (stuck in damp / develop mode)
Symptom
G1 boots into 'damp mode' and ignores SDK commands; entering 'develop mode' also disables SDK responsiveness, so users conclude the SDK is broken.
Affected
General G1 firmware behavior.
Fix / Workaround
Activate the robot with the remote before sending SDK commands: press L1+A, then L1+UP to leave damp mode. Do not sit in develop mode if you need SDK control. If you entered develop mode, renew the ai-sport client via the app.
Code and official examples break after firmware 1.4.0 ('ClientStub send request error')
Symptom
Previously working Python code and official SDK examples stop working after updating to firmware 1.4.0; repeated '[ClientStub] send request error'. Related: GetVolume returns error 3102, high-level/audio examples fail.
Affected
Firmware 1.4.0.
Fix / Workaround
No vendor fix documented. Confirm the robot is activated (out of damp mode), verify the SDK version matches the firmware, and if you upgraded specifically for a feature, be aware some users rolled back. Watch Unitree release notes for a follow-up patch.
Inspire hand won't open serial port / is unreachable at its IP
Symptom
'Open Serial port /dev/ttyUSB0 failed' — the Inspire hand can't be controlled; or the FTP hand is unreachable at 192.168.123.211.
Affected
G1 with Inspire hand (DFX serial vs FTP modbus-TCP variants).
Fix / Workaround
The control method depends on the hand variant. FTP Inspire hands use Modbus TCP, not a serial port — using serial code on an FTP hand fails by design. Confirm which variant you have and use the matching control method; verify the hand's IP is reachable on the 192.168.123.x network.
Dex3-1 hand thumb barely moves during teleoperation
Symptom
In teleop the thumb only makes 3-4° micro-movements versus full range in simulation; thumb-to-index pinch bottoms out at ~5cm, too coarse for fine manipulation.
Affected
G1 software V1.4.7 + Dex3-1 hand.
Fix / Workaround
No fix documented. Power-up self-check shows joints normal and simulation works, which points to a command-mapping mismatch between teleop and the hand driver rather than hardware. Report the driver version to Unitree.
Teleoperation latency grows to ~2.5s after 1-2 hours
Symptom
Arm and camera latency climbs to ~2.5s after prolonged teleop; arm prep pose takes ~4s instead of ~2s, eventually appearing immediately on startup.
Affected
xr_teleoperate v1.3 and v1.5.
Fix / Workaround
No fix documented. Upgrading to a gigabit router and WiFi 6 did not help, and simulation mode is unaffected — suggesting an onboard buffering/accumulation issue rather than the network. Restart the teleop stack between long sessions as a stopgap.
Policy deployment over WiFi hangs on 'Waiting for connection rt/lowstate'
Symptom
Deploying over WiFi hangs on 'Waiting for connection rt/lowstate' even though SSH to the robot works; wired ethernet works fine.
Affected
G1, DDS-based control.
Fix / Workaround
Use a wired connection and specify the interface, e.g. ./g1_ctrl --network enx701988512412. DDS multicast for lowstate does not traverse the wireless interface reliably.
DDS assertion failure / CycloneDDS writer error when initializing the G1 simulation; it won't start.
Affected
Ubuntu 22.04, ROS2 Humble; system CycloneDDS 0.10.5 vs Python CycloneDDS 0.10.2.
Fix / Workaround
Don't source the ROS setup script (its DDS libs differ from unitree_sdk2's). Verify which .so is linked at compile time. Alternatives: build CycloneDDS 0.10.2 from source, patch unitree-sdk2py for 0.10.5, or develop on Ubuntu 20.04.
'Unmatched robot type' on Ethernet connect (23 vs 29 DOF)
Symptom
The controller connects over Ethernet then immediately fails with 'Unmatched robot type' during sim-to-real deployment.
Affected
G1 23-DOF and 29-DOF variants (incl. locked-waist/dummy-hands configs).
Fix / Workaround
The robot's DOF/config must match the controller's expected type. Set the correct DOF in your config, and check for conflicting SDK installs in /usr/local vs your project path — rebuilding unitree_sdk2 cleanly (deploy build with -DBUILD_EXAMPLES=OFF, sim build with a separate CMAKE_INSTALL_PREFIX) resolves the related unresponsive-velocity-mode case.
Moving arms via SDK while walking destabilizes balance
Symptom
Controlling the arms via SDK while walking (gamepad) makes the robot bend forward or lose balance; raising arms while walking produces an unstable, heavy gait.
Affected
G1 with 3-DOF waist.
Fix / Workaround
No fix documented. Zeroing waist axes, holding initial values, and leaving them untouched were all tried without success — the arm SDK controller and the locomotion balance controller conflict. Avoid large arm motions during locomotion until a firmware update addresses it.
Simulated G1 collapses with no default stabilization
Symptom
In MuJoCo simulation the G1 has no default stabilization and falls over when run without controls.
Affected
unitree_mujoco.
Fix / Workaround
Enable the elastic band: set enable_elastic_band: 1 in unitree_mujoco/simulate/config.yaml (or ENABLE_ELASTIC_BAND=True). Note the factory motion controller isn't available in sim, and the band can be awkward to disable when switching to joystick control.
The 9,000 mAh battery gives only about 2 hours per charge, and drains faster under dynamic movement.
Affected
Base model, 9,000 mAh pack.
Fix / Workaround
This is a capacity limitation, not a fault. Keep charged spare batteries for hot-swapping between sessions; budget runtime around ~2 hours of active use.
Buyers of the ~$13,500 base G1 discover it's a demo/showcase unit with no SDK and cannot be programmed.
Affected
G1 base (23 DOF) vs G1 EDU (up to 43 DOF).
Fix / Workaround
This is a product-tier limitation. SDK access, higher torque, and more DOF require the G1 EDU / developer platform (~$44k-$74k). Confirm the tier before purchase if you intend to develop.
Solid red LED / physical fault checklist (falls, cables, battery)
Symptom
Solid red LED indicating a software/hardware error; plus field faults — cracks/dents from falls, sensor degradation from dust or misalignment, unresponsive components from loose/frayed cables, battery swelling or deformation.
Affected
General.
Fix / Workaround
Visually inspect for impact damage; clean sensors and confirm mounting; reseat cables and connectors; verify battery seating and replace if swollen or leaking. On a solid red LED, run the mobile-app diagnostics and record a video of any intermittent fault before contacting support. Note: opening the shell voids the warranty.
Critical security: BLE command injection with hardcoded keys (UniPwn)
Symptom
A command-injection flaw in the BLE Wi-Fi provisioning, using hardcoded AES keys shared across all units, allows root access and is potentially wormable. Separate research found telemetry transmitted to external servers every ~5 minutes.
No confirmed vendor patch documented at time of writing. Mitigate at the network level: isolate the robot on a segmented/firewalled network, restrict access to its internal interface (192.168.123.0/24), and block unexpected outbound traffic. Watch for a Unitree firmware advisory.
Viral demo skills are choreographed, not autonomous
Symptom
Kung-fu and backflip clips are trained showcases; the robot has no household autonomy out of the box and fails simple tasks like opening a door.
Affected
General.
Fix / Workaround
Expectation-setting, not a fault. Autonomous task performance requires significant development on the EDU platform; the base experience is remote/pre-programmed motions.