Whisker Feeder-Robot: scheduled meals running late or not happening
What you're seeing right now
Your Whisker Feeder-Robot is skipping scheduled feedings, running meals at incorrect times, or ignoring new schedule updates sent from the Whisker app. The small Connect light on the keypad may be blinking red, or the top Status Tower may display solid purple.
In this guide
💡 Quick Resolution Summary (BLUF)
- Offline Local Execution: The Feeder-Robot stores schedule configuration in local memory (EEPROM). It will continue to feed on its last saved schedule even if Wi-Fi goes completely offline. Missed or delayed meals are caused by local schedule desync or sensor blockages, not public time-sync socket issues.
- App Discrepancy: If you modify your schedule in the app while the feeder is offline (blinking red Connect light), the cloud saves the new schedule, but the feeder continues to run the old schedule stored locally. The app does not display a connection error warning.
- Chute Blockage Safeguard: If your pet does not eat their food and it backs up into the dispenser chute, the feeder's infrared sensors will detect the blockage (Status Tower turning solid purple after 12+ hours) and skip meals to prevent overflow.
- Re-Sync Protocol: To force a correct schedule synchronization, clear all scheduled meals in the app, power-cycle the unit for 15 seconds to reboot its internal Wi-Fi chip, wait for the Connect light to turn solid blue, and then re-save your schedule.
Whisker Feeder-Robot light and status codes
| Indicator Type | State / Color | Meaning & Action Required |
|---|---|---|
| Connect Light (Keypad) | Solid Blue | Online and connected. The feeder can download schedule updates successfully. |
| Connect Light (Keypad) | Blinking Red | Offline. The feeder cannot receive schedule changes. Verify 2.4 GHz network settings. |
| Connect Light (Keypad) | Blinking Blue | Attempting connection. Wait for it to turn solid blue. |
| Status Tower (Top) | Solid Blue | Automatic Feeding Mode active. Feeder is executing the locally saved schedule. |
| Status Tower (Top) | Solid Purple | Chute blockage detected. Feeding is paused to prevent overflow. Clear the bowl and wipe sensors. |
01 — Why schedules stop syncing
Two main issues cause the feeder to fall out of sync with the app. These usually occur together after local network drops or physical blockages.
Wi-Fi drop causing schedule mismatch
When the Feeder-Robot disconnects from your local network (indicated by the Connect light blinking red), it cannot download updates sent from the Whisker cloud. If you edit the schedule in the app during this offline window, the app saves the changes to the cloud database but cannot push them to the device. The feeder continues to run its old locally-saved schedule, creating a silent mismatch.
Food chute blockage and sensor stops
The Feeder-Robot has physical infrared sensors inside the Food Chute. If food builds up and blocks these sensors—either because the pet is not eating (Status Tower solid purple) or because kibble debris has coated the sensor lenses—the feeder pauses automatic dispensing to prevent overflow. This is a mechanical safety check rather than a network or cloud-sync error.
Follow these step-by-step instructions to restore synchronization.
02 — Step-by-step sync fix
Part A checks local diagnostic indicators. Part B forces a fresh cloud handshake. Work through them in order.
Whisker Feeder-Robot
If physical board failure or water damage has broken the Wi-Fi module, a replacement unit restores full connectivity and scheduling.
After completing the checklist, verify that the feeder dispenses a meal at the next scheduled time. If it still fails, see the advanced configuration section or replacement options.
03 — Sourcing and replacement options
If the feeder continues to drop its connection or ignores schedule updates after completing the checklist, the internal Wi-Fi antenna or main control board may have failed. Replacing the unit is the most reliable way to restore schedules.
Whisker Feeder-Robot 3
The latest Feeder-Robot 3 includes an updated power board and comes with a full warranty. The stainless steel hopper option is worth considering if your current hopper shows wear.
As an Amazon Associate, Pet Infrastructure earns from qualifying purchases. We may receive a commission when you buy through our links, at no extra cost to you.
04 — Advanced network configuration
For managed networks or mesh Wi-Fi systems. Most home users can skip this section.
| Specification | Requirement / Value | Status & Diagnostics |
|---|---|---|
| Wi-Fi Band | 2.4 GHz Only | 802.11 b/g/n. 5 GHz is not supported. Use a dedicated 2.4 GHz SSID if drops occur. |
| Security Protocol | WPA / WPA2-PSK (AES) | Does not support WPA3 or Enterprise portals. |
| IP Protocol | IPv4 via DHCP | Does not support IPv6. Ensure DHCP pool has available leases. |
| Connect Light (LED) | Solid Blue / Blinking Red | Solid Blue = Online. Blinking Red = Offline. Blinking Blue = Connecting. |
| Status Tower (LED) | Solid Blue / Solid Purple | Solid Blue = Schedule active. Solid Purple = Food chute block (feeding paused). |
Resolving Wi-Fi band steering issues →
Many modern routers combine 2.4 GHz and 5 GHz bands under one name, then dynamically shift simple 2.4 GHz devices to the 5 GHz band. Because the Feeder-Robot only supports 2.4 GHz, this steering causes immediate disconnections.
Fix: Access your router's administration portal. Temporarily disable the 5 GHz band during onboarding, or create a separate, dedicated 2.4 GHz guest network SSID (secured with WPA2-PSK AES) specifically for your smart pet devices. This prevents the router from attempting to steer the feeder.
Pinning the feeder's MAC address (Static AP / Client Steering) →
On mesh networks (Eero, Nest, Orbi, UniFi), the system controller may dynamically move connected clients between access points. If this occurs during an active app schedule push, the connection disruption corrupts the packet, causing a sync failure.
Fix: Open your mesh router's controller app. Locate the Feeder-Robot under connected clients, and enable static AP assignment (sometimes called 'sticky client', 'lock to AP', or 'client steering') to lock the feeder to the nearest access point. This ensures data packet integrity during schedule transfers.
Frequently Asked Questions
Why does my Whisker Feeder-Robot skip scheduled meals?
The most common cause is that the feeder has disconnected from Wi-Fi (indicated by a blinking red Connect light on the control panel) and cannot sync schedule updates made in the app. Another frequent cause is an obstructed food chute: if kibble builds up and blocks the infrared sensors (indicated by a solid purple Status Tower after 12+ hours), the unit pauses automatic feeding to prevent overflow.
The app shows my schedule is saved, but the feeder is ignoring it — why?
This occurs when the feeder is offline when you save schedule updates in the Whisker app. The app saves the new parameters to the cloud database, but because the unit is offline, it cannot download the update and continues to execute the old schedule stored in its local memory. Confirm the Connect light is solid blue, clear the schedule in the app, power-cycle the feeder for 15 seconds, and then save the schedule again.
What is the difference between the blue lights on the Feeder-Robot?
The Feeder-Robot has two distinct blue indicators. The main Status Indicator Tower on top of the hopper displays solid blue to confirm the feeder is in Automatic Feeding Mode and running a schedule. The Connect light on the Control Panel displays solid blue to confirm the unit is online and connected to the internet.
Based on official manufacturer documentation and practical engineering recommendations. Verified support resources can be found at the Whisker official support portal. Last revised: June 2026.
Need help with other smart pet gear? Check our diagnostic guides for Whisker Feeder-Robot motor stall faults or Whisker Feeder-Robot backup battery replacement.
