Narwal troubleshooting
Freo error codes, localization and base-station diagnostics. Start with the exact model, then match the error code, light pattern, voice alert or symptom.
Narwal Freo Z Ultra
Exact-model mapping, network, perception, mop, dust-collection and base-station diagnostics grounded in Narwal support.
12 live diagnostics →FlowNarwal Flow
Flow-specific Wi-Fi, docking, dock-version, detergent and noise diagnostics.
7 live diagnostics →All Narwal diagnostics
19 guidesError 1011
Narwal defines Error 1011 as a localization error. Check whether the base station was moved; if it was, remapping may be required. Also check whether the robot is operating on a temporary map that no longer matches its physical location.
Error 1012
Error 1012 means the robot is trapped. Move the Freo Z Ultra into an open area and remove surrounding obstacles, then check the bumper, whether it can return to base, and whether the LiDAR rotates normally without a red warning.
Error 1013
Error 1013 means the robot believes it entered a No-Go Zone. Move it out of the restricted area and restart. If the error repeats, save a screenshot of the map and restricted zones, the robot location, and the exact error message before changing boundaries.
Error 2003
Narwal’s published Error 2003 article is manufacturer-wide and uses other Freo models as examples rather than being a Freo Z Ultra-specific bulletin, so keep the scope explicit. Error 2003 is the base-station water-overflow path. Treat it as a seal/drainage diagnosis, not a robot navigation error. First remove the cleaning tray and base slope pad, dry residual water in the station and clean the tray. Then pull the dirty-water tank and prove the lid locking tabs fully engage—the manufacturer says a distinct click should be heard and felt. Inspect sealing strips on both clean- and dirty-water tanks and press any loose strip back into its groove. Lift both tanks and check the silicone seals beneath them. Finally, confirm that no other-brand fragrance or cleaning detergent was added to the clean-water tank. If the station still overflows after those visible owner-level checks, stop repeated wash cycles and escalate rather than opening the powered base.
Wi-Fi / app connection failure
Narwal Flow is an exception to the older Narwal “2.4 GHz only” rule: Narwal’s Flow-specific FAQ says this model supports both 2.4 GHz and 5 GHz Wi-Fi. Start with the Flow pairing path in the Freo App, confirm the robot and base are powered, enable Bluetooth and the phone permissions Narwal requires, and keep the robot near a strong signal. If setup fails, compare the two supported bands or a simple phone hotspot without changing several variables at once. Narwal’s general network guide is still useful for permissions, hotspot and router isolation, but its 2.4-GHz-only sentence is not the correct compatibility rule for Flow. If the failure persists, send Narwal the robot SN, App ID and a screen recording or clear record of the failed setup stage.
Won't return to base
Do not start by deleting the map. First give Narwal Flow a compliant base area: hard and level, away from direct sunlight, with about 45 cm / 1.5 ft of clear approach space. Narwal’s current return-to-base troubleshooting then calls for cleaning the robot/base charging contacts and reflector stickers, checking the drive and caster wheels for oil or debris, confirming the cleaning tray and roller-brush cover are seated correctly, and remapping only if the base station was moved. A short return from near the dock can then separate final-entry trouble from whole-home localization. If Flow still cannot return, record the final approach for support instead of repeatedly remapping.
Base button not working / missing
First identify which Narwal Flow dock you own. Narwal documents two versions: the Basic Dock has one multifunction button, while the compact Auto Refill & Drainage dock intentionally has no base-station button. On the Basic Dock, a short press starts/pauses/resumes, a double press starts or cancels mop-pad cleaning, a two-second hold ends a task, and a five-second hold enters or exits pairing mode. If you have the compact dock, use the Freo App or robot controls instead of diagnosing a missing switch. If a powered Basic Dock ignores every documented gesture, capture the response on video for Narwal.
Abnormal noise
Narwal’s Flow-specific noise article starts with the side brush: clean away hair or foreign objects and check for deformation. Then compare whether the sound still occurs in mopping-only mode. Narwal’s broader robot-noise guide adds owner-safe checks for the roller brush and wheels when the source is unclear, and notes that the mopping module can make a normal motor feedback sound when fully lifted. If a clean robot still makes unfamiliar grinding, clicking or impact noise, stop speculative disassembly and record a close video showing the operating mode and moving part when the sound begins.
Detergent not auto-dispensing
The first test is not the detergent bottle; it is the dock version. Narwal says Flow’s Basic Dock does not auto-dispense detergent at all. With that dock, detergent is mixed manually into a full clean-water tank using Narwal’s specified capful guidance. The compact/Auto Refill & Drainage version has a built-in main detergent reservoir and can auto-dispense after the cartridge is filled and reinstalled horizontally. Narwal also documents an app switch under Device Homepage → Settings → Base Station → Automatically add detergent for Flow with Auto Refill & Drainage. If you diagnose the wrong dock as if it had the other dock’s dosing system, a normal design difference looks like a failure.
Residual water after mopping
Narwal says Flow normally leaves no water in most cases, but a few droplets can be normal after significant movement—especially when the robot exits the base station or climbs a threshold. Treat quantity and pattern as the key discriminator. Dry the floor, repeat the same short route and note whether moisture is limited to those movement events or forms a continuous trail/puddle during ordinary travel. Do not open the internal water path for a few isolated drops. If the residue is clearly noticeable or persistent, Narwal asks for the robot serial number and a video of the robot operating.
One side brush is longer
Yes—on Narwal Flow the right-hand side brush is intentionally longer. Narwal says the extra reach comes from the brush itself, not from an extend/retract actuator, so a healthy asymmetric pair should not be “fixed” or trimmed to match. Confirm the long brush is on the right, inspect for real damage or tangles, make sure any removed brush is seated correctly, and judge health by whether it rotates and sweeps edge debris normally. If the longer right brush stops rotating, repeatedly detaches or is physically damaged, that is a separate maintenance fault worth documenting for Narwal.
Wi-Fi / app connection failure
The Freo Z Ultra is a 2.4 GHz-only Narwal model, so a failed setup should first be separated into band, phone-permission, app-pairing and home-router problems. Narwal’s network guide says to power the robot and base normally, keep the base where Wi-Fi is strong, enable Bluetooth and location permissions, then add the device inside the Narwal Freo App rather than pairing it through the phone’s Bluetooth menu. If setup still fails, a temporary 2.4 GHz phone hotspot is a useful discriminator: a successful hotspot connection points back toward the home router or its signal, while failure on both networks makes the robot/app path more suspicious. Do not factory-reset the robot merely because the app says offline; preserve the failure stage, screenshots and current map first.
Mapping failed / wrong map
For a Freo Z Ultra that maps the home incorrectly, misses rooms, places itself in the wrong area or throws a localization-style problem, preserve the current map first and determine whether the failure happened during first mapping or after a previously good map changed. Narwal’s mapping guidance says doors to wanted rooms should be open, floor and base-station obstacles should be cleared, people should stay about two meters away and out of doorways, and the base should not be moved after mapping. For Freo Z Ultra specifically, Narwal also calls out removing the protective camera stickers before mapping. If the base was moved or the active temporary map conflicts with reality, remapping is appropriate; if only a small new area was omitted, the robot may add it during later cleaning, so immediate map deletion is not always necessary.
Obstacle avoidance / collisions
Freo Z Ultra obstacle avoidance is not a single sensor with a single cleaning step. Narwal’s exact-model guidance says the AI avoidance strategy can be set to Intelligent or Safe, and it also explains that dim light, direct strong light and blind spots around low objects can reduce visual avoidance performance. Narwal’s broader recognition troubleshooting says to clean the forward and side sensor surfaces and notes that very small obstacles can remain challenging even on AI-camera models. Start by documenting the object, lighting and approach direction, then clean only the user-accessible sensor surfaces and repeat the same controlled route. If Safe mode improves clearance, the hardware may be functioning but the selected avoidance behavior was too permissive for that scene. A persistent miss on a clear, well-lit test object after cleaning is a better support case than random resets.
Errors 1009 / 1010
Narwal explicitly lists Freo Z Ultra as an applicable model for Errors 1009 and 1010 in its robot-vacuum error index. On Z Ultra, the official owner path is intentionally narrow: clean the mopping module and restart the robot; if the error persists, contact support. Do not import the sealing-plate inspection written for Freo Z10/Z10 Ultra into a Z Ultra repair just because the code numbers match—Narwal separates those model groups in the same error entry. Before cleaning, preserve the exact code and the task state in the app, then inspect only the removable user-serviceable mop components for hair, grit or poor seating. After reinstallation, restart and run a short safe mopping test. A recurring 1009/1010 after correct cleaning/reseating is a service case, not an invitation to pry into the lift drive or modify the mop mount.
Errors 1022 / 1023
Errors 1022 and 1023 are Narwal’s Base Station Not Found path. The official branch changes depending on where the robot is when the error occurs. Near or on the base, Narwal says to verify base power, check installation/condition of the roller-brush assembly, rear drive wheels and caster, cleaning pad/tray or ramp components, and remap if the base was moved. When the error occurs away from the station, Narwal specifically points to cleaning the base-station reflector stickers. That location split is the key discriminator: do not immediately delete the map when the robot is physically at the dock with a power or seating problem, and do not replace a charging part when the robot simply cannot find the mapped station from a room. If the controlled checks fail, support wants the serial number, occurrence time and video.
Dust collection timing / failure
Freo Z Ultra can look like it “forgot to auto-empty” when it is actually following Narwal’s moisture-control sequence. Narwal’s exact-model product help says that after a cleaning task, the robot dust bin is dried to avoid pulling sticky wet waste into the collection path, and dust collection starts before the next task rather than immediately after the previous one. So the first diagnostic question is timing: did collection fail when it was genuinely scheduled to run, or are you expecting an after-task empty cycle that this model intentionally postpones? If a real collection cycle starts but debris remains, Narwal’s base-station guide says to check whether the dust bag/bin is full and inspect all three dust inlets for hair clogs, then manually run intensive dust collection from the app. If no collection starts when requested, preserve the app/station state and avoid repeatedly cycling a blocked system.
Mop drying not working / interrupted
Freo Z Ultra normally dries its mop pads with 40°C air after mop washing, and Narwal documents Strong, Silent and Smart drying behavior. Strong Drying is designed around roughly four hours, while Silent Drying can take under five hours; Smart Drying can choose behavior around Do Not Disturb. Before diagnosing a failed heater or fan, confirm drying actually started after a completed mop-wash cycle or from the Washing & Drying control, then leave the robot/mops in the base for the full selected mode. Removing the robot or mopping module early can end the drying process. If the app reports Error 1039 or 1040, Narwal labels those as mopping-pad drying interrupted and directs owners to contact support with video. That exact error path should not be diluted into endless DIY cleaning when the normal start conditions are already met.
Hot-water mop wash not heating
Freo Z Ultra supports hot-water mop washing, but Narwal does not expose a manual temperature slider for the user to force a fixed water temperature. The exact-model product help says to enable Smart Temperature-Controlled Mopping System under Settings > Base Station, after which the robot/base automatically adjusts wash-water temperature according to dirt type and wash cycle. That means “the water is not always very hot” is not enough to diagnose a fault. First verify the feature is enabled and that you are observing an actual mop-wash event. If the base consistently produces no heated wash water when the function should be active, Narwal’s base-station troubleshooting explicitly includes Freo Z Ultra and says to unplug the base power cord to restart it; persistent failure goes to support. Do not open a powered wet base or try to bypass the temperature-control system.