Core Safety Features to Look For
1. Force-Limiting Joints
Humanoid robots use actuators (motors + gears) to move. Force-limiting joints detect unexpected resistance and immediately reduce torque to avoid injury.
What to ask: What's the maximum force per joint? Is it compliant with ISO/TS 15066 collaborative robot standards? (~150N contact force typical)
2. Emergency Stop (E-Stop)
Physical button on the robot body and/or app-based remote stop. Pressing it should immediately halt all motion and drop power to motors.
What to ask: Where is the physical E-stop located? Can multiple people trigger it via app? What's the response time (typically <100ms)?
3. Geofencing / Virtual Boundaries
Software limits that prevent the robot from entering certain rooms or zones (e.g., baby's room, staircase, outdoor areas).
What to ask: Can you set multiple no-go zones? How are they enforced—GPS, room mapping, or QR markers?
4. Collision Detection & Avoidance
Sensors (LiDAR, depth cameras, tactile) detect obstacles and stop or redirect before contact. Critical for homes with pets and children.
What to ask: Can it detect fast-moving objects (pets, kids)? What's the reaction distance? Does it pause or reroute?
5. Tip-Over Prevention
Humanoid robots are top-heavy. Look for wide foot base, low center of gravity, or active balancing (gyroscopes, accelerometers).
What to ask: Can it recover from a push or uneven surface? What's the max incline it can handle safely?
Child & Pet Safety Scenarios
Scenario 1: Child Walks in Front While Robot Is Moving
Expected behavior: Robot should detect child via depth sensor, stop immediately (within 1 meter), and either wait or reroute.
What to verify: Test with dummies or supervised trials. Does it work in low light? With fast-moving toddlers?
Scenario 2: Pet Jumps on Robot or Grabs an Arm
Expected behavior: Force-limiting joints reduce torque; robot pauses and requests help (teleop or user intervention).
What to verify: Does the robot distinguish between intentional interaction (e.g., handing it something) and unsafe contact?
Scenario 3: Robot Operating Near Stairs
Expected behavior: Geofencing should block staircase access entirely. If robot approaches, it should stop 1+ meters away.
What to verify: Can you set permanent stair exclusion zones? What happens if mapping fails?
Pre-Purchase Safety Checklist
- Physical E-stop accessible and clearly labeled
- Force limits published in spec sheet (look for <150N per joint)
- Geofencing software with easy room/zone blocking
- Collision detection tested with pets/children (ask for demo videos)
- Battery certifications (UL 2054, IEC 62133 for lithium-ion safety)
- Tip-over recovery or prevention (watch demo on uneven surfaces)
- Fall detection + automatic shutdown if robot tips
Battery Safety
Humanoid robots use large lithium-ion battery packs (similar to e-bikes or power tools). Key concerns:
- Thermal runaway: Batteries can overheat and catch fire if damaged or defective. Look for UL 2054 certification.
- Charging safety: Does the robot auto-stop charging when full? Is there overcharge protection?
- Physical damage: If robot tips or collides, battery should be in a protected enclosure
- Swappability: Can you replace the battery yourself, or does it require service? What's the disposal process?
What Certifications Mean
UL (Underwriters Laboratories): U.S.-based safety testing. UL 2054 for batteries; UL 1950 for robotics.
CE (Conformité Européenne): European safety mark. Required for sale in EU; indicates compliance with safety directives.
FCC (Federal Communications Commission): Regulates wireless emissions (Wi-Fi, Bluetooth, cellular). Doesn't cover physical safety.
ISO/TS 15066: Collaborative robot safety standards. Humanoids targeting homes should aim for similar thresholds.
Fail-Safe Behaviors
What should the robot do when something goes wrong?
- Network loss: Should pause or return to charging station; not wander randomly
- Sensor failure: Should stop immediately and request service
- Low battery: Should navigate back to charger autonomously or alert user
- Stuck/trapped: Should attempt recovery (reverse, reroute) then call for teleop if that fails