An automatic pet feeder promises portions at times. The portioning mechanism gets all the attention in reviews, and the clock gets none, which is backwards: a feeder with a perfect auger and a clock that resets on every power blip will miss meals, and a missed meal is exactly the failure the device exists to prevent.
Where the schedule lives
The first question about any feeder is where the feeding schedule is stored. On the device, the schedule survives outages and keeps firing without a network. In the cloud, every feed depends on the device being online at the moment of dispensing, and a router reboot at 7 a.m. can mean a skipped breakfast even though nothing is wrong with the feeder.
Neither choice is wrong. A cloud-executed schedule can be edited from anywhere and adapts to app changes; a locally stored schedule is what you want for a house with unreliable internet or a pet on a strict medical timetable. Many feeders mix both, storing the schedule locally after it is set from the app, which is usually the best of the two designs. The datasheet rarely says which one a given model uses, so it has to be tested.
What a power outage does to the clock
A feeder without battery-backed timekeeping loses the wall-clock time when mains power fails. The relay state and the schedule may survive in flash, but "feed at 07:00" is meaningless to a device that thinks it is midnight, or 1980. Some models recover by pulling network time once Wi-Fi returns. Some keep running on the wrong time until a human opens the app.
The test costs nothing: unplug the feeder overnight, plug it back in, and check what time the device believes it is and whether the next scheduled feed fires on schedule. Do this before trusting the device with a weekend away. A feeder that passes this test has an RTC with backup or a disciplined NTP recovery path; one that fails it needs to be treated as a mains-dependent clock.
Time zones and daylight saving
Clock errors do not only come from outages. A feeder that stores local time will shift every feed by an hour when daylight saving starts or ends, unless the app rewrites the schedule. A feeder that stores UTC and displays a converted time handles the transition by itself. The distinction is invisible at purchase and shows up twice a year, usually on the first morning after the change when the cat is an hour early to an empty bowl.
Frequent travelers hit a related edge: some apps schedule in the phone's current time zone, so feeding a pet at home while the owner's phone is in another zone can quietly move every feed. It is worth confirming the schedule is anchored to the device's configured time zone, not to wherever the phone happens to be.
Drift is a medication problem, not a nuisance
Cheap realtime-clock crystals drift, typically minutes per week on the worst parts and seconds per week on decent ones. For twice-daily kibble, drift is trivia. For a pet on timed medication, a feeder that loses four minutes a week has lost almost half an hour by month five, and for some drugs the window matters.
Network-connected feeders re-discipline the clock periodically and drift becomes irrelevant. Offline feeders do not get this correction, so drift compounds for the life of the deployment. If the feeder will run medical schedules, the drift number or a periodic sync behavior belongs in the purchase conversation.
What to ask before you order
Four questions cover the whole clock story. Where is the schedule executed, device or cloud. What happens to the clock and the schedule after a 24-hour outage. Does the device handle daylight saving transitions on its own. Is there a time source the feeder trusts, and how often.
A pet feeder manufacturer can answer all four against the bill of materials, because the answers are design decisions, not marketing points. The models listed under pet feeders on XingLiao cover both local and cloud-executed schedules, and edge cases like RTC backup are worth a message here before a medical feeding project is quoted.
Top comments (0)