Disclosure: kittynex.com participates in affiliate programs. If you buy through a link on this page, we may earn a commission at no extra cost to you.
By Jason Feng, Founder & Researcher. See how this review was researched.
Quick answer
The light next to the Connect button is the diagnosis. On a Litter-Robot 4, a blinking blue light means the unit is trying to reconnect, one flashing yellow means it is waiting to be onboarded, and a solid white light means Wi-Fi is switched off entirely.
Every current Litter-Robot connects on 2.4 GHz only, so a 5 GHz-only network will never work. Your cat is fine in the meantime: the cycle logic runs on the machine, not in the cloud.
Table of contents
- What offline actually costs you
- The Wi-Fi light table
- Why 2.4 GHz is the whole story
- The reconnect order
- When the network is not the problem
- Mesh routers and the guest-network workaround
- Litter-Robot 5 and the LCD status line
- Network requirements by model
- What the machine still does without Wi-Fi
- Our verdict
- How we researched this
- Sources
What offline actually costs you
Before the fix, know what you are fixing. An offline Litter-Robot is not a broken Litter-Robot, and the two get conflated constantly in owner reports.
Whisker’s fault articles all open with the same three prep lines: confirm the unit is plugged in, confirm it is connected and online, and confirm the firmware is current. That ordering is a tell. Connection is a prerequisite for diagnosis, not for operation. When a unit drops off the network, what you lose is the fault text in the app, push notifications, the usage history, remote cycle commands, and firmware updates. What you keep is a machine that still senses a cat and still runs a cycle.
The settings prove it. Cycle delay can be set from the Litter-Robot 4 control panel without the app, in 3 to 30 minute increments. Sleep mode is a long press on the machine.
PETKIT says the same thing in plainer language. Its support center answers the question directly: if the network is disconnected, the litter box continues to work according to the previous app settings. Whisker does not publish a sentence that flat, which is why this comes up as a question at all. [DATA NOT VERIFIED: Whisker does not publish an explicit "works offline" statement for the Litter-Robot 4, though its troubleshooting requires on-unit button presses for every fault path.]
The Wi-Fi light table
This is the table to keep open while you are standing over the machine. All rows are Litter-Robot 4 unless noted, and all are from Whisker’s consolidated light codes guide.
| What you see | What it means | What to do |
|---|---|---|
| Blue bar, one flashing yellow at Connect | Onboarding mode, waiting for the app | Finish setup in the Whisker app |
| Blue bar, blinking blue at Connect | Connecting, or dropped and retrying without success | Wait a few minutes, then reconnect manually |
| Blue bar, solid white at Connect | Wi-Fi is switched off | Short press Connect |
| Blue bar, flashing red at Connect | Cannot reach the router | Power cycle the unit, check the band |
| Blue bar, flashing white at Connect | Wi-Fi chip fault | Base replacement |
| Solid white LED, Litter-Robot 5 | Connected | No action |
| LCD reads Disconnected, Litter-Robot 5 | Offline, auto-retry starting | Wait, then update network in app |
| LCD reads WiFi Chip Fault, Litter-Robot 5 | Radio fault | Hard power cycle, then check IoT firmware |
Two rows are easy to mix up and they mean opposite things. A solid white light at the Connect button on a Litter-Robot 4 means Wi-Fi is off, not that Wi-Fi is fine. Owners see white, read it as healthy, and spend an hour on the router.
The other trap is the chip fault. On a Litter-Robot 4, blue with a flashing white at Connect is a hardware fault that Whisker routes straight to a base replacement. No amount of router work fixes it. On the Litter-Robot 5, the same class of fault has its own recovery path, covered below.
Why 2.4 GHz is the whole story
Every Litter-Robot in the current line is a 2.4 GHz device. The product pages say it plainly: the Litter-Robot 4 requires a 2.4 GHz signal with IPv4 or IPv6 addressing and does not support the 5 GHz band, and the EVO page carries an identical sentence. Whisker’s onboarding guide for the Litter-Robot 4 repeats it.
That single constraint explains most "it worked for a year and then stopped" cases. Nothing changed in the machine. Something changed in the air.
Three things move under you. A router replacement ships with band steering on by default, which presents one network name and quietly assigns devices to whichever band the router prefers. A firmware update on the router can flip that behavior. And a mesh system that adds a node can change which band a distant corner of the house receives.
If your network shows one SSID for both bands, the machine may have connected to 2.4 GHz on day one and be offered 5 GHz on day four hundred. It will keep retrying and keep failing, because the credentials match but the band does not.
The practical fix is a dedicated 2.4 GHz network with its own name, either by splitting the bands into separate SSIDs or by creating a guest network pinned to 2.4 GHz. Whisker recommends exactly that workaround for mesh systems, which is a useful admission that the problem is common.
The reconnect order
Work down this list rather than jumping to the step that sounds most likely. The order is Whisker’s, sorted by cost in time and money.
- Look at the Connect light. If it is solid white, Wi-Fi is off. Short press Connect and stop reading.
- Confirm the network is alive. Check that other devices on the same network are online, and that the SSID and password have not changed.
- Give the automatic retry a chance. A Litter-Robot 4 that dropped will attempt to rejoin with the credentials it already has. This can take a few minutes.
- Power cycle properly. Unplug the power inlet from the back of the base, wait at least one minute, plug it back in, and let the unit finish its initial cycle until the bar goes solid blue.
- Update the network in the app. Open the Whisker app, select the unit, tap the settings gear, choose Update Network, and follow the prompts. This is the step that handles a new router or a changed password.
- Delete and re-onboard. If Update Network fails, delete the robot in the app and run onboarding from scratch. Whisker presents this as the next step, not a last resort.
- Move the unit or the router. Whisker’s note is that a robot in a spot where your phone shows weak signal will struggle to hold a connection.
Step 4 matters for a mechanical reason. A hard power cycle forces the radio to re-read its stored credentials and restart the association from scratch. A button press does not. Whisker asks for a full unplug, not a power toggle, in every reconnect article it publishes.
Step 5 is worth understanding rather than just following. Update Network keeps the unit’s identity and history and changes only the credentials. Deleting wipes the association and makes you rescan the QR code.
When the network is not the problem
Three failure modes look like network problems and are not.
The first is a firmware update in progress. On a Litter-Robot 4, a white light flashing in the middle of the bar means an over-the-air update is running, and no action is needed. Whisker’s newer models extend this: after onboarding a Litter-Robot 5, the company asks for 15 to 30 minutes before you touch anything.
The second is an unbalanced machine. Blue with two flashing yellow lights is not a network code at all. It means the scale has been triggered for more than 30 minutes, usually because the unit is on carpet, on a litter mat, on a power cord, in a grout line, or leaning against a wall. Owners who see yellow and assume connectivity spend the afternoon on the router. Our cat sensor fault guide covers that path properly.
The third is a genuine radio failure. On a Litter-Robot 4 that is the blue with flashing white at Connect, which is a base. On a Litter-Robot 5 it is the WiFi Chip Fault message, and the recovery is specific: unplug the power supply from the base rather than pressing power, wait 15 seconds, plug back in, wait 60 seconds for the camera to chime on a 5 Pro, then hold Cancel and Connect together for three seconds to display the firmware versions. If the IoT firmware reads 0.0.0 after a retry, Whisker wants a support contact rather than more attempts.
Mesh routers and the guest-network workaround
Mesh systems are the single most common cause of a Litter-Robot that onboards once and then refuses to stay connected.
The mechanism is band steering. A mesh system advertises one network name and decides per device which radio to use. When the robot first joins, the mesh may hand it 2.4 GHz because that is what the robot can hear. Later, after a node reboot or an optimization pass, the same mesh may stop presenting a compatible 2.4 GHz association. The robot keeps its credentials, sees a name it recognizes, and cannot complete the join.
Whisker’s recommendation for this case is to create a dedicated 2.4 GHz guest network and reconnect the robot to it. That removes the steering decision entirely: the guest SSID exists only on 2.4 GHz, so there is nothing to steer to.
Two router-side details show up in Whisker’s onboarding notes. Network names must be under 31 characters, and passwords must be between 8 and 31 characters with no slashes, periods, or spaces. Hidden networks are not visible to the unit, and the robot does not display a MAC address.
One documented conflict is worth flagging. Whisker’s onboarding guide lists IPv4 or IPv6 as acceptable, and the product pages repeat that. A separate Whisker article states the Litter-Robot is not compatible with IPv6 and that newer Xfinity routers running IPv6 produce an "invalid credentials" error until the router is switched to IPv4. Both statements are on Whisker’s own site. If you are on Xfinity with a correct password and a credentials error, try IPv4 first.
Litter-Robot 5 and the LCD status line
The newer generation replaced the color puzzle with text, which changes the procedure slightly.
A short press of the Connect button on a Litter-Robot 5 shows the current status on the LCD. Offline reads as Disconnected, and the screen then moves to "Reconnecting, check router, or update network in app" for roughly ten seconds while the robot retries. If it succeeds, the LED goes solid white and the LCD reads Connected.
Confirmation is a two-part check on that model, and the second part is the one people skip. Whisker asks you to open the app, confirm the unit shows Online, and then send a manual cycle from the app under Controls, Cycle. A unit that shows Online but does not respond to a remote command is not connected, it just has a stale status.
For a changed router or password, the path is Device Settings, then Update Network. Whisker notes that the Litter-Robot 5 Pro cannot join a different network through Update Network at all and requires a Factory Reset first, which is a real difference between the two models.
One more band note for that generation: the standard Litter-Robot 5 is 2.4 GHz only. Whisker’s offline article says so directly, in the same paragraph that recommends rebooting the router for 30 seconds.
Network requirements by model
The brand-to-brand comparison matters if you are choosing a box partly on connectivity, because the requirements are not uniform.
| Model | Wi-Fi bands | Onboarding method | Offline behavior |
|---|---|---|---|
| Litter-Robot 4 | 2.4 GHz only | QR code plus Bluetooth, Connect button for 3 seconds | Runs on stored settings, no app data |
| Litter-Robot 5 / 5 Pro | 2.4 GHz only | Connect button, LCD status, Bluetooth | Runs on stored settings, LCD reports state |
| Litter-Robot EVO | 2.4 GHz only | Whisker app onboarding | Runs on stored settings |
| PETKIT Pura Max 2 | Wi-Fi and Bluetooth, band not published | Menu button to Configure Network, then app | PETKIT states it keeps prior app settings |
| PETKIT Purobot Max Pro 2 | 2.4 and 5 GHz | PETKIT app | Same |
| PETKIT Purobot Ultra | 2.4 and 5 GHz | PETKIT app | Same |
The pattern is worth naming. Whisker is the conservative one on radio hardware, shipping 2.4 GHz only across three generations, while the newer PETKIT models support both bands. That makes a dual-band PETKIT easier to live with on a modern mesh network, and it makes a Litter-Robot more dependent on you configuring a 2.4 GHz SSID correctly.
If the choice between generations is what you are weighing, our Litter-Robot 5 vs 4 vs EVO comparison covers what changed beyond the radio.
What the machine still does without Wi-Fi
With no connection, the Litter-Robot still detects a cat, still waits out the cycle delay, still rotates, and still reports a full drawer on its light bar. The delay setting you configured persists on the device. Sleep mode persists. A manual cycle works from the panel.
What stops is everything in the app or the cloud: push notifications, the fault text that names a problem in words rather than colors, the weight history and per-cat visit log, remote cycling while you are away, and firmware updates.
Two consequences follow. A fault while offline is harder to diagnose because you lose the text, so fix the connection before reading the alert. And a unit offline for months may be several firmware versions behind, so a reconnect can trigger an update that changes behavior for half an hour.
Our verdict
Read the light at the Connect button before you touch the router. On a Litter-Robot 4 that light names the exact failure: onboarding, retrying, radio off, unreachable, or dead chip. Three of those five are fixed in under a minute.
Then check the band. Every Litter-Robot in the current line is 2.4 GHz only, and a mesh network with band steering is the most likely reason a unit that worked for months stopped working. A dedicated 2.4 GHz SSID is the durable fix, and Whisker recommends it itself.
Follow the reconnect order rather than improvising. Light, network, automatic retry, hard unplug for a minute, Update Network, then delete and re-onboard. The hard unplug is the step that actually resets the radio.
Do not treat offline as an emergency. The box keeps cleaning. If you are leaving for a week and the app shows offline, the cat is still covered, and the honest priority is the litter level.
If the light pattern you are chasing is not a Wi-Fi code, check the other patterns before ordering anything. Our Litter-Robot error codes guide covers the full vocabulary, and the pinch detect fault guide covers the one pattern that stops the globe entirely.
How we researched this
- Wi-Fi light behavior comes from Whisker’s consolidated Litter-Robot 4 light codes guide and its app onboarding article, both fetched on 2026-10-27 through a US egress with an en-US language header.
- Reconnect steps are Whisker’s published order from its reconnect article and its offline troubleshooting article, including the one-minute unplug and the Update Network path.
- Band requirements are quoted from Whisker’s product pages for the Litter-Robot 4, 5 and EVO, which each state 2.4 GHz with no 5 GHz support.
- The mesh and band-steering workaround, the SSID and password character limits, and the Litter-Robot 5 Pro factory-reset requirement are Whisker’s own statements, not inference from owner threads.
- This is a research-based review. Specifications come from manufacturer documentation, with owner-reported failure patterns aggregated across public reviews and community threads.
See our full methodology page and our affiliate disclosure.
Sources
Fetched on 2026-10-27 through a US egress with an en-US language header:
- https://www.litter-robot.com/support/article/litter-robot-4-light-codes-guide/
- https://www.litter-robot.com/support/article/whisker-app-onboarding-your-litter-robot-4/
- https://www.litter-robot.com/support/article/how-do-i-reconnect-if-i-got-a-new-router-wifi-network/
- https://www.litter-robot.com/support/article/my-unit-went-offline-but-my-internet-and-other-appliances-still-work/
- https://www.litter-robot.com/support/article/why-does-my-whisker-app-say-successful-onboard-but-the-litter-robot-appears-disconnected/
- https://www.litter-robot.com/support/article/litter-robot-5-offline/
- https://www.litter-robot.com/support/article/litter-robot-5-wifi-chip-fault/
- https://www.litter-robot.com/support/article/litter-robot-4-wait-time-settings
- https://www.litter-robot.com/litter-robot-4.html
- https://www.litter-robot.com/litter-robot-5.html
- https://www.litter-robot.com/litter-robot-evo.html
- https://gcs-petkit.udeskglobal.com/hc/articles/3426
- https://www.petkit.com/products/purobot-max-pro-2-automatic-cat-litter-box-with-ai-camera
- https://www.petkit.com/products/purobot-ultra
- https://www.petkit.com/pages/manual-downloads