Companion robot safety

Companion Robot Emergency Stop Checklist: 21 Safe-Shutdown Tests

A stop button is only useful when people can find it, reach it and understand what happens next. This owner-focused procedure turns vague assurances into a repeatable test.

By BizarreSexuality.com Editorial Desk · Published October 18, 2026 · 12-minute read

Companion robots combine software, batteries, powered joints, microphones, cameras and network services in a product that may share close space with people. That combination makes the words stop, pause, sleep and power off deceptively easy to confuse. A voice command might suspend conversation while leaving motors energized. An app button may depend on Wi-Fi. A standby control may darken a screen without isolating a battery. The correct behavior is model-specific, so the manufacturer's current manual remains the controlling source for the exact device.

This checklist is a conservative way to verify those instructions. It is not a certification, repair procedure or substitute for a recall remedy. The U.S. Occupational Safety and Health Administration's robotics guidance concerns industrial systems, not a blanket rule for consumer companions, but it illustrates a useful principle: safeguards, emergency controls and human access must be considered together rather than as labels on separate components. NIST's robot test-method program similarly emphasizes repeatable conditions and observable results. Owners can borrow that disciplined approach without pretending a home check proves laboratory compliance.

Start by separating four different actions

Write down the manufacturer's name for each control and the stated result. Do not merge the categories simply because one button performs several functions.

• Normal pause: a routine interruption from which the robot can resume its task.
• Emergency stop: a rapid intervention intended for an abnormal or hazardous situation. The exact implementation varies, and some consumer robots may not have a formal emergency-stop device.
• Normal shutdown: an orderly software and hardware sequence that may save state before turning systems off.
• Energy isolation: preventing powered motion or other hazardous energy from returning. This may require a manufacturer-specified switch, connector or service step; unplugging the charging dock alone may not isolate an internal battery.

If the documentation never states which control stops powered movement, treat that absence as a pre-use question for the seller or manufacturer. Do not infer safety performance from a red color, a familiar symbol or marketing language.

Before the test: prepare a low-risk area

Move the robot to a level, dry space with enough clearance for its longest possible reach, rolling distance or tipping envelope. Remove pets, children, fragile items and loose cables. Keep the charging dock outside the movement zone unless the test specifically concerns docking. Use the robot's lowest supported speed and smallest movement. If the manual requires two people, protective equipment or a service technician, follow that instruction and stop the home test.

Charge only to the level needed for the procedure. Inspect for swelling, unusual heat, damaged insulation, liquid intrusion, cracked housings or an unfamiliar smell. Those are reasons to stop and follow the maker's isolation and support instructions, not reasons to press buttons experimentally. Our separate companion robot charging safety checklist covers docks, cables and battery warning signs in more detail.

The 21-test emergency stop and shutdown checklist

1. Match the product to the right instructions

Record the model, hardware revision, serial number, app version and installed firmware. A manual for a visually similar robot may describe different controls. Save a local copy of the current instructions and note the retrieval date.

2. Check recalls and official safety notices

Search the manufacturer support site and the appropriate national product-safety database. In the United States, the Consumer Product Safety Commission maintains a public recall search. A recall instruction outranks a generic checklist; do not continue testing a unit that should be disconnected or returned.

3. Locate every physical stop control

Find each button, guarded switch, key, pull cord or disconnect named in the manual. Verify that its label is legible from the position a household member would actually occupy. A control hidden by clothing, accessories or furniture is not reliably accessible.

4. Identify remote stop methods separately

List app, remote-control and voice commands, but mark their dependencies: Bluetooth, local Wi-Fi, cloud access, account login, microphone availability and phone battery. A network-dependent command should not be the only plan for an immediate stop.

5. Define the expected stopped state

Copy the manual's claims precisely. Does the control halt wheels, arms, head motion and speech? Are joints actively braked or merely unpowered? Does the robot remain upright? Knowing the expected state makes the observation meaningful.

6. Test from idle

With no task running, activate the approved stop. Observe displays, indicator lights, fans and sounds. The result establishes a baseline and reveals whether the device uses a latched control that must be reset deliberately.

7. Test during the smallest permitted movement

Command one low-speed, low-force motion described as safe for user testing, then activate the stop from outside the movement envelope. Record stopping distance and any continued settling. Never block a limb with your hand to measure force.

8. Test the most accessible alternate control

If the robot has two approved physical stop points, test both independently. A household plan should not assume that a control on the rear remains reachable when the robot faces a wall.

9. Test the app without internet access

Only if the manual allows it, disconnect the home's internet while preserving the local connection and see whether the app stop remains available. Label the result as local, cloud-dependent or unclear. Do not change router security settings solely for the test.

10. Test loss of the controller

During a benign idle state, lock the phone, close the app or move the remote out of range as the manual permits. Confirm whether the robot pauses, continues or enters another defined state. This is not a reason to create a hazardous movement first.

11. Confirm voice-command limits

Try the documented voice stop in ordinary background noise and from the recommended distance. Note whether wake words, profiles or network access are required. Voice control is convenient, but microphones can be muted, obstructed or confused by noise.

12. Verify dock behavior

Check whether the stop control works while docking, charging and leaving the dock, but only in the modes the manufacturer explicitly permits users to test. Confirm that stopping the robot does not create a cable pinch or leave a connector under strain.

13. Observe communications after a stop

Determine whether cameras, microphones, wireless radios and cloud sessions remain active. A motion stop is not necessarily a privacy stop. If privacy matters, follow the separate, documented procedure for sensors and accounts.

14. Check residual movement

Wheels may coast, a heavy arm may lower, and a balancing platform may need space to settle. Record what happens after activation instead of describing the response only as “instant.” If behavior differs from the manual, stop using the unit and contact support.

15. Confirm that restart is deliberate

A stopped robot should not resume unexpected movement merely because Wi-Fi returns, an app reconnects or power is restored. Follow the maker's reset sequence and verify that a fresh command is required where the instructions promise one.

16. Test restart from a safe position

Before resetting, move people and objects out of range and verify the robot's posture. Some machines perform a calibration movement, home their joints or re-establish balance. Treat the reset as a new operating event, not the end of the emergency.

17. Distinguish shutdown from battery isolation

Run the documented normal shutdown, then observe which indicators remain active. If the product contains an internal battery, unplugging the wall adapter does not necessarily remove stored energy. Never open a sealed pack or connector housing without authorized instructions.

18. Document an inaccessible-control scenario

Without moving the robot, imagine the primary control is against a wall or beneath a fallen object. Identify the approved alternative. If there is none, change placement and household rules rather than inventing a risky reach-around maneuver.

19. Teach every authorized user

Each adult user should be able to point to the controls, describe their effects and explain when not to approach. Keep a one-page model-specific card near the operating area, but do not cover ventilation openings or controls.

20. Record failures without repeatedly reproducing them

Capture the firmware version, time, command, indicators and observable result. One unexpected response is enough to pause normal use and contact support. Repeatedly recreating an abnormal movement can increase risk and complicate evidence.

21. Re-test after meaningful changes

Repeat the low-risk checks after firmware updates, repairs, battery replacement, controller changes, relocation or long storage. A dated log is more useful than memory. Our software support lifespan guide explains why version history and end-of-support dates matter.

What to put on the household stop card

Use plain language and large type. Include the model name, the physical stop location, the first action, what not to touch, the safe restart sequence and the official support contact. Add the robot's weight only if the manufacturer provides it; do not encourage anyone to lift a machine beyond their capacity. If a breaker, plug or battery connector is part of the approved procedure, identify it precisely and make sure the instruction cannot be confused with another appliance.

When testing should end immediately

Stop the procedure if the control does not behave as documented, the robot restarts on its own, a joint continues powered motion, a battery or connector becomes unusually hot, the enclosure cracks, liquid is present, a protective cover is missing, or an error message directs the user to service. Keep people away, follow the manufacturer-approved isolation steps and contact official support. For smoke, fire or immediate danger, leave the area and use local emergency services; do not handle a damaged lithium-ion battery.

Evidence standards and important limits

A successful home check proves only that one unit produced an observed response under the recorded conditions. It does not prove compliance with an industrial robot standard, validate every fault condition or guarantee future behavior. Marketing terms such as “safe AI,” “collision avoidance” and “human-aware” do not replace a documented stop path. Conversely, the absence of an industrial-style red mushroom button does not by itself prove a consumer device is defective; the product's design, intended use, jurisdiction and official instructions all matter.

For buyers, make stop controls part of the return-window inspection. Ask the seller for the full manual before purchase, confirm whether safety-critical functions require an active subscription, and save warranty promises in writing. The companion robot warranty checklist covers repairs, transport, batteries and service exclusions, while the return-window test plan helps organize the broader acceptance check.

Primary references

• U.S. OSHA Technical Manual, Section IV, Chapter 4: Industrial Robots and Robot System Safety — industrial context and safeguarding concepts; not presented here as a consumer certification rule.
• NIST Robot Test Methods — background on repeatable robot performance testing.
• U.S. Consumer Product Safety Commission recall database — current recall and remedy notices for covered consumer products.