Brand-scoped code index

Narwal robot vacuum error codes and alerts

Use this page as a routing table, not a universal code chart. The same number can change meaning across brands and generations, so every row keeps the exact model attached to the fault.

Before fixing anything: confirm Narwal + exact model + exact code/alert. If your model is not listed, use the Error Finder or symptom hubs instead of borrowing another model’s meaning.

Use Error Finder Open Narwal desk Browse symptoms

Narwal Flow

1 code / alert paths

Abnormal noiseNarwal FlowNarwal’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.Open →

Narwal Freo Z Ultra

6 code / alert paths

Error 1011Narwal Freo Z UltraNarwal 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.Open →Error 1012Narwal Freo Z UltraError 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.Open →Error 1013Narwal Freo Z UltraError 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.Open →Error 2003Narwal Freo Z UltraNarwal’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.Open →Errors 1009 / 1010Narwal Freo Z UltraNarwal 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.Open →Errors 1022 / 1023Narwal Freo Z UltraErrors 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.Open →

Why this index is model-locked

Broad “complete code” tables can collapse multiple generations into one meaning. This index only links to existing source-backed diagnostics and keeps model scope visible so a code number is never treated as universal.