Key takeaways
- Group any blink pattern into one of four families before hunting for a brand specific chart: motor stall, no water detected, communication fault, or battery trouble.
- A universal reset, unplug sixty seconds, reconnect, restart, clears most ghost errors regardless of brand.
- A light that returns every cycle on a machine with clean filters and clear tracks is describing a real fault, not a nuisance.
- Treat any error light next to a tripping GFCI outlet as an electrical question first and a robot question second.
- Film the blink pattern before calling support; it settles arguments faster than counting flashes over the phone.
The light under the handle used to glow a steady, boring blue. Tonight it stutters: two quick blinks, a pause, two more, over and over, while the robot sits motionless on the shallow end steps.
You have no manual within reach, the box went in the recycling back in June, and the sticker on the power supply is too sun bleached to read. This is the exact moment most owners give up and start pricing new robots.
Do not. After nine seasons of reading these lights for a living, I can tell you blink patterns are far more generous than they look. Stop trying to memorize an exact count for your exact brand, and start grouping codes by what they protect against instead, and the light stops being a mystery.
Why the lights speak in families, not sentences
Dolphin, Polaris, and Aiper each publish their own blink charts, and the precise number of flashes varies by model and sometimes by firmware version within the same model line. Chasing an exact match to a random forum post is often a dead end.
What holds steady across nearly every brand is the short list of conditions worth protecting against in the first place. A motor working too hard, water that never reached the pump, a power supply that lost touch with the robot’s board, a battery pack refusing to cooperate: that handful of situations covers the large majority of error lights you will ever see, whatever logo sits on the lid.
Treat the exact blink count as a detail for your specific manual, and treat the family below as the map that gets you there faster.
A reference table for reading any brand’s lights
Use this as your starting point before digging through a manual you may not even be able to find, then confirm the exact specifics for your model afterward.
| Light behavior | Likely family | First checks | Typical reset |
|---|---|---|---|
| Fast, repeating pattern only while the robot tries to move | Motor stall or overload | Clear tracks and wheels of debris, check brush axles | Unplug 60 seconds, clear the jam, restart |
| Steady or slow blink from the moment power connects | No water detected or priming fault | Confirm the robot is fully submerged, check the intake for blockage | Reseat in water, start a fresh cycle |
| Blink pattern only on the power supply, robot itself dark | Communication or supply fault | Check connector pins for corrosion, inspect the cord for damage | Reseat the cable, power cycle the supply |
| Alternating two color pattern near the charge port | Battery or charging fault | Confirm the charger is fully seated, check contacts for corrosion | Full charge cycle before judging the pack |
| Light stays solid and steady, no blinking at all | Not an error, just underperformance | Check filter media and confirm the cycle mode | None needed |
Notice that the bottom row is not an error at all, just normal underperformance next to a perfectly healthy light. That distinction alone saves plenty of owners an unnecessary support call.
Motor stall and overload lights
This family fires when the drive motor or the pump motor draws more current than the board expects, and it is protecting a motor, not accusing one.
Tracks and wheels jammed with a pebble or a wad of hair make the drive motor strain, and a wrapped impeller does the same thing to the pump motor. Both trip the same category of light on most brands, even though the actual blockage sits in two completely different places.
Unplug the power supply, flip the robot over, and roll the tracks by hand before assuming a dead motor. Tracks that spin freely while the light keeps firing point further in, toward the impeller bay or a genuinely tired motor, and that climbs the repair or replace ladder fast on an older machine.
No water detected errors
Robots prime themselves the moment they submerge, and a sensor or pressure switch confirms water is actually moving through the body before the pump commits to full power.
The classic trigger is simple: someone sets the robot in too shallow, or drops it in before the pool has enough water level to fully cover the intake. Reseat it fully underwater and give it a fresh start before assuming anything is broken.
A less obvious trigger is trapped air in a machine straight out of the box or fresh off a winter storage shelf. If the light clears the moment you tilt and resubmerge the unit a few times, air was the entire story, and no part number is involved.
Communication faults between the supply and the robot
App connected robots add a second conversation on top of the electrical one, and this family covers both sides: the power supply losing touch with the robot’s board, and the robot losing touch with the app over Wi-Fi.
A customer once drove forty minutes to our counter convinced his robot had died, because his app showed a red triangle and nothing else. The robot itself had no light lit at all, a classic communication fault rather than a dead machine. A five minute cable reseat sent him home with a working robot and a much better story than the one he arrived with.
Start at the physical link. Inspect the connector for green corrosion or trapped moisture, and confirm the cable is fully seated rather than resting on its pins.
If the connection looks clean and the light persists, check the app for a waiting firmware update. A surprising number of app pairing errors on connected models clear the moment the firmware catches up, since the two sides were quite literally running different versions of the same conversation.
Safety first
If a light in this family shows up alongside a GFCI outlet that keeps tripping, stop treating it as a robot problem. Dry everything, reset the GFCI once, and if it trips again, call an electrician before you touch the robot again. The ESFI’s pool electrical safety guidance is blunt about why that device never gets bypassed.
Battery lights on cordless models
Cordless robots translate the same worries into a different vocabulary. A slow, single blink is usually a routine low battery pack warning, nothing more urgent than a recharge.
A rapid or alternating pattern right after you connect the charger more often points at contact corrosion on the charging pins, or a pack sitting in deep discharge lockout after a winter of neglect. Give it a full hour on the charger before deciding the pack itself has failed; chargers on models like an Aiper Seagull Pro will not show a normal charging light until voltage climbs back into a safe range.
The reset sequence that clears most ghost errors
Before you order a single part, run the universal reset: unplug the power supply, wait a full sixty seconds so the board fully discharges, reconnect, and start a fresh cycle. Cordless models get the same idea through their own power button, held until the unit fully powers down.
- Unplug the power supply and wait sixty seconds
- Clear tracks, wheels, and the impeller bay of debris
- Confirm the robot is fully submerged before restarting
- Check the app for a waiting firmware update
- Inspect the connector for corrosion or trapped moisture
When to stop resetting and call it a real fault
A light that clears after one reset and stays clear was a ghost, and you can move on with your day. A light that returns within the same cycle, every time, on a machine with clean filters and clear tracks, is describing a real fault rather than a hiccup.
Photograph or film the blink pattern before you call support or a local shop. A fifteen second video saves a frustrating game of counting flashes over the phone, and it hands a technician something concrete to match against the chart for your exact model, whether that is a Dolphin Nautilus CC Plus or a Polaris VRX iQ+.
Where to go from here
Group your light into its family before you ever open the manual: stall, water, communication, or battery. Run the free checks for that family, then the universal reset, before spending anything at all.
Most blinking lights I chased down over nine seasons ended in a rinsed filter, a cleared jam, or a firmware update, not a shop bill. Keep the pattern and its timing in mind, and the next time that light stutters at you, it will read like a note instead of a threat.
Frequently asked questions
Do all pool robot brands use the same blink codes?
No. Dolphin, Polaris, Aiper, and other brands each publish their own exact patterns, and the same two blink pattern can mean different things across brands. What stays consistent is the small set of situations worth protecting against: motor stall, no water detected, communication faults, and battery trouble. Use those families to narrow the problem fast, then confirm the exact pattern in your specific manual before ordering parts.
Can I keep running the robot if an error light appears but it still seems to clean fine?
You can run one more cycle to gather information, but do not make it a habit. A light that flashes while the robot still completes its job is usually an early warning, like a filter starting to choke flow or a connector starting to corrode. Clear the likely cause soon, since ignoring an early warning tends to turn a free fix into a paid one.
Does a solid, non blinking light ever signal a problem?
Rarely. Solid lights almost always mean normal operation or a simple low battery notice on cordless models. Real faults nearly always announce themselves through a blinking or alternating pattern, because manufacturers design steady light to mean everything is fine. If a robot underperforms with a solid, healthy light showing, look at filters and cycle mode rather than the light itself.
How many times should I try resetting before calling support?
Two attempts is a fair limit. Run the universal reset once, and if the same light returns within the same cycle, clear the obvious physical causes, debris, moisture, a loose connector, and reset a second time. A third identical failure in a row means you are looking at a real fault, and further resets just delay the call you already need to make.
Will a firmware update change what the blink patterns mean?
Occasionally, yes. Manufacturers sometimes adjust which condition triggers which pattern between firmware versions, which is part of why matching an old forum post to a current robot can mislead you. Check the app's changelog after any update, and keep in mind that a firmware update can also simply fix the bug that was causing a nuisance error in the first place.
Krisha Gupta
Krisha Gupta is a home-technology writer who spends most of her weekends knee-deep in pools, testing the latest robotic cleaners so readers don't have to. Her reviews are hands-on and jargon-free, focused on what a robot actually does when you leave it running unsupervised for eight hours. When she's not comparing brush patterns or waterline scrubbing, she's writing plain-English maintenance guides for pool owners who'd rather swim than tinker.
