DEEBOT OZMO 950 Error Codes and Indicator Lights Explained

The DEEBOT OZMO 950 talks to you through beeps, error codes, and indicator lights. When something goes wrong, the robot almost always gives a visual and audio clue before it stops. Understanding those signals turns “Why did it stop?” into a quick checklist instead of a mystery, especially when paired with notifications from the Android companion app.

This guide focuses on what the lights and codes usually mean, how to read them step by step, and how to respond safely without guessing.

1. How the Robot Communicates Problems

The OZMO 950 typically uses three layers of feedback:

Indicator lights on the robot itself
Voice prompts or beeping sounds
Error messages displayed in the Android app

Even if you do not remember the exact code, the combination of light color, blinking pattern, and voice prompt is usually enough to identify the problem category: power, connectivity, mechanical blockage, sensors, or system fault.

The fastest strategy is:

Look at the robot’s top lights.
Listen for any voice or beep pattern.
Open the Android app to see the error description.

Treat these three channels as one integrated error “language.”

2. Status and Error Indicator Lights: Color and Pattern

The main status light and related indicators can show:

Different colors (commonly white/blue, red, or off)
Different patterns (solid, slowly flashing, quickly flashing)

Each combination corresponds to a typical state. Exact color names and icons differ slightly across batches and app designs, but the logic is similar.

2.1 Normal Operating States

These states indicate that the robot is not in trouble:

Solid light in the normal color (often white or blue):
Robot is idle but ready, docked and charging, or fully charged on the dock.
Slowly pulsing or breathing light in normal color:
Robot is charging or in standby mode, no active error.
Light off with the robot off:
Robot is powered down, or the battery is fully drained.

If the robot behaves normally and the app reports no errors, these states are nothing to worry about.

2.2 Wi-Fi and Network States

Network status is usually indicated by a small Wi-Fi symbol or by blinking patterns when you enter pairing mode.

Typical examples:

Rapid flashing Wi-Fi indicator or main light during setup:
Robot is in pairing mode, searching for a network or waiting for the Android app to connect.
Solid Wi-Fi indicator:
Robot is connected to the home network and can communicate with the app and cloud.
No Wi-Fi icon / app shows “offline”:
Robot is not currently connected; it might be out of range, the router might be off, or the password may have changed.

These states are not errors in the mechanical sense, but network issues can cause remote control, scheduling, or firmware update failures.

2.3 Error and Warning States

Most problem conditions are shown as:

Red light solid
Red light flashing (slow or fast)
Normal color + red combination in some models

Common patterns:

Solid red with voice prompt or beep:
A blocking mechanical or sensor error; the robot has paused to prevent damage.
Flashing red with repeated beeps:
Urgent attention needed, such as the robot being stuck, a wheel lifted, or a critical sensor problem.
Normal color but with repeated voice warnings:
Less urgent issues, such as dustbin not properly installed or mild obstruction.

If you see red, combine it with what the robot is doing (or not doing), and then check the Android app to read the actual error category.

3. Error Codes: Categories Instead of Memorizing Numbers

Different firmware versions and regional manuals may use slightly different labels for error codes (numbers like “E10,” “E11,” etc.). Instead of memorizing specific code lists, it is more practical to understand the major categories common to the OZMO 950:

Power and battery errors
Drive system and wheel errors
Main brush and side brush errors
Dustbin, filter, and fan errors
Cliff and navigation sensor errors
Stuck or lifted robot errors
Water tank and mopping system errors
Internal system or unknown errors

When you see or hear an error, the Android app usually shows a short description such as “Check main brush,” “Check wheels,” or “Check cliff sensor,” which maps directly to one of these groups.

Below are the typical categories and how to respond to each.

4. Power and Battery-Related Errors

4.1 Cannot Charge Properly

Signs:

Robot docked but the charging light does not behave as usual.
App may show a low battery that never increases.
Voice warning informing that charging has failed.

Common causes:

Dirty charging contacts on the robot or dock
Dock not plugged in or power source unstable
Robot not sitting correctly on the dock

Actions:

Unplug the dock from the wall, then plug it back in to ensure stable power.
Wipe the charging contacts on both the robot and dock with a dry cloth.
Make sure the dock is on a hard, flat surface with enough clearance for the robot to align.
Gently push the robot back onto the dock until you hear the confirmation sound and see the normal charging pattern.

If the robot still does not charge, it may be a deeper battery or internal power error, and support may be needed.

4.2 Low Battery Shutdown / Cannot Start Cleaning

Signs:

Robot refuses to start a job and asks to return to the dock.
App shows a very low battery percentage.
Robot reports battery is too low to start.

Actions:

Place the robot on the dock and allow it to charge uninterrupted.
Avoid constantly interrupting cleaning cycles; let the robot return to the dock automatically.

If the battery drains unusually fast even after full charge, it may be a sign of battery wear over time, not a short-term error.

5. Drive System and Wheel Errors

5.1 Wheel Stuck or Blocked

Signs:

Voice prompt such as “Wheel is stuck” or similar wording.
Robot stops in place with red indicator.
Wheels do not rotate freely when you try to move them by hand.

Common causes:

Hair or thread wrapped around wheel axles
Small objects wedged under the wheels
Robot forced onto an uneven or soft surface (like thick carpet edges)

Actions:

Turn the robot over on a soft surface.
Inspect both large drive wheels and gently spin them.
Remove wrapped hair with tweezers or the cleaning tool.
Check for small debris stuck in the wheel well.

If the wheel feels mechanically stiff even when clean, it may require professional repair.

5.2 Robot Cannot Move or Keeps Pivoting

Signs:

Robot rotates but does not move forward.
App or voice prompt indicates an obstruction or wheel error.

Common causes:

One wheel blocked while the other moves
Front caster wheel jammed
Robot stuck on thresholds or trapped between floor levels

Actions:

Clean the front caster wheel; remove it (if designed to be removable), clear hair inside, and reinstall.
Avoid high thresholds or add ramps if needed.
Expand no-go zones over problem areas to reduce repeated wheel stress.

6. Main Brush and Side Brush Errors

6.1 Main Brush Blocked

Signs:

Robot stops and announces that the main brush is stuck.
Red or warning light with “Check main brush” in the app.

Common causes:

Hair, thread, or pet fur wrapped tightly around the brush
Large debris caught between brush and floor
Foreign object wedged under the brush guard

Actions:

Open the main brush cover and remove the brush.
Cut away hair along the brush and at both ends (near the bearings).
Remove any large object lodged in the brush area.
Reinstall the brush firmly, ensuring it clicks into place.

If the robot repeatedly reports main brush errors even after thorough cleaning, check if the brush is worn, deformed, or cracked; replacement might be necessary.

6.2 Side Brush Errors

Signs:

Robot reports side brush issue or makes strange clicking noise near corners.
Side brush appears loose or does not spin.

Common causes:

Hair wrapped around the side brush spindle
Side brush arms bent or worn
Side brush not properly attached or screw is loose

Actions:

Remove the side brush by gently pulling or unscrewing, depending on design.
Clear hair around the spindle.
Straighten slightly bent bristles or replace the brush if badly deformed.
Reattach it properly and ensure it spins freely.

7. Dustbin, Filter, and Fan Errors

7.1 Dustbin Not Installed or Not Detected

Signs:

App or robot says the dustbin is not in place.
Robot refuses to start cleaning.

Common causes:

Dustbin removed and not reinserted fully
Dustbin misaligned after cleaning
Sensor or switch near the bin slightly blocked by dust

Actions:

Remove the dustbin completely.
Check for dust buildup around the bin contacts or switches; gently clean.
Insert the bin firmly until you hear or feel it click.

If the error persists, observe the small detection components around the bin area and gently clean them with a dry cloth.

7.2 Filter or Fan Error (Reduced Suction)

Signs:

Robot reports reduced suction or fan error.
Loud or unusual suction noise.
Cleaning performance suddenly drops.

Common causes:

Filter extremely clogged with fine dust
Dustbin packed tightly, restricting airflow
Foreign object lodged near the fan intake

Actions:

Empty the dustbin and remove loose dust.
Take out the filter and tap it gently to remove debris (or follow washable instructions if applicable).
Make sure air pathways in the bin and near the filter are not blocked.

Persistent fan errors after cleaning may indicate a faulty motor or internal blockage that requires service.

8. Cliff Sensors, Navigation, and “Robot Will Fall” Errors

8.1 Cliff Sensor Dirty or Blocked

Signs:

Robot refuses to move forward near stairs or even on flat floors.
Voice prompts about cliff sensors or “robot will fall.”
App shows a cliff sensor error.

Common causes:

Dust or dirt covering underside cliff sensors
Dark or reflective flooring confusing the sensors
Robot running in extremely bright sunlight or unusual conditions

Actions:

Turn the robot over and locate each cliff sensor on the underside.
Wipe them with a soft, dry microfiber cloth.
Avoid covering them with tape or stickers; they need a clear line of sight to the floor.

If the error happens only on a specific floor pattern (very dark or highly reflective), consider adding a no-go zone there or adjusting the cleaning area.

8.2 Navigation or “Stuck in Place” Errors Without Visible Obstruction

Signs:

Robot spins or nudges furniture repeatedly, then reports an error.
Map in the Android app shows confusion or repeated attempts in one corner.

Possible causes:

Front sensors dirty or foggy.
Bumper stuck due to a small obstruction.
Robot operating in extremely cluttered areas.

Actions:

Clean the front sensor window with a soft cloth.
Press the bumper gently; ensure it moves freely and returns to its neutral position.
Remove small objects and cables from the floor.

If navigation errors continue in the same area, widen no-go or restricted areas to reduce tricky zones.

9. Stuck or Lifted Robot Errors

9.1 Robot Is Physically Trapped

Signs:

App shows the robot is stuck.
Robot beeps and stops, usually under furniture or on thresholds.

Common causes:

Robot wedged under low furniture.
Robot stuck on cable bundles, door tracks, or uneven thresholds.
Robot partially hanging off edges or ledges.

Actions:

Gently lift the robot and place it on a flat surface.
Remove the cause of obstruction (cables, clutter, or move furniture slightly).
Consider using no-go zones or physical barriers to prevent the robot entering the problem spot again.

9.2 Robot Lifted or Not on the Floor Properly

Signs:

Robot reports a lifting or tilt error.
It may refuse to move even though it looks fine.

Common causes:

Robot resting on a thick cable or object, causing one wheel to hang midair.
Robot placed on uneven or unstable surface.

Actions:

Relocate the robot to a flat, stable area, then restart cleaning.
Remove any object under the robot that changes its tilt.

10. Water Tank and Mopping System Errors

10.1 Water Tank Not Installed Properly

Signs:

Robot reports that the water tank is missing or not correctly installed.
Mopping mode will not start.

Common causes:

Tank not fully inserted into its slot.
Dust or debris around the tank connector.

Actions:

Remove the water tank completely.
Wipe the connector area gently.
Reinsert the tank firmly until it clicks or seats smoothly.

10.2 Water Flow Issues

While not always labeled as a strict “error,” water flow problems can be indicated by warnings or poor mopping performance:

Mop pad remains completely dry.
Area under robot becomes too wet.

Actions:

Ensure the water level is set correctly in the Android app (if adjustable).
Check that the mop pad is attached properly.
Clean the outlet area of the water tank (if accessible) to remove clogs.

11. Internal System or Unknown Errors

Sometimes the robot reports a general system error that does not clearly map to a visible part.

Typical signs:

Error code displayed but description is vague.
Robot reboots or stops without clear mechanical cause.

First steps:

Turn off the robot using its power switch (if available), wait a short while, then power it back on.
Place the robot on the dock and let it charge for a bit.
Open the Android app and check for firmware updates.

If the same error recurs frequently with no clear physical cause, it may indicate a deeper internal problem that needs professional diagnosis.

12. Using the Android App as an Error Companion

The Android app is your “translator” for error codes:

It usually shows a plain-language message (“Check wheels,” “Check main brush,” “Check cliff sensor”).
Some versions include illustrations or short guides.
The app may store recent error history, helping you spot recurring problems.

Useful habits:

When an error occurs, open the app immediately and note the description.
If the same type of error appears repeatedly, consider whether a component (brush, wheel, sensor) has reached the end of its life.
Use the app’s maintenance or usage stats to time replacements for brushes, filters, and other consumables.

13. Preventing Errors Before They Start

Most frequent errors can be minimized with simple routine care:

Clear floors of cables, socks, and small items before scheduled cleanings.
Regularly clean brushes, wheels, sensors, and dustbin.
Keep the charging area clear so the robot can dock reliably.
Avoid extremely thick rugs or block them off with no-go zones.
Protect steep drop-offs with both real and virtual boundaries.

By combining consistent maintenance with a basic understanding of what each light and error category means, the DEEBOT OZMO 950 becomes less “mysterious” and more like a predictable appliance. When it does complain, you will know whether it is asking for a quick brush cleaning, a sensor wipe, a better Wi-Fi connection, or—on rare occasions—professional support.