Practical guide
PetSafe Smart Feed Extra Meals: Button Lock and Household Records
Check the three possible request routes. ButtonLock blocks physical FeedNow while app FeedNow remains available, so household requests and observed output need separate records.
Write what appeared without guessing its cause
If food appears outside a Smart Feed schedule, first record the time, what was already in the bowl and any actual observed delivery. Food present is not enough to identify which control caused it. It may also be old food, an unrecorded caretaker action or output you did not watch.
PetSafe’s current extra-meal support page identifies the physical FeedNow button as a common possible cause when a pet or child presses it. That is a useful branch to check, not proof of the cause in every household. Keep the animal’s appropriate feeding care separate from the investigation; do not automatically add or subtract an unverified amount.
This page concerns the Smart Feed model/control family documented by current MyPetSafe support. It does not describe Simply Feed’s advance-next-meal FeedNow or a rotating Five Meal tray. Confirm the model and current app route before changing a setting.
Separate scheduled, physical and app requests
Smart Feed request pathways
| Pathway | How to check the record | ButtonLock boundary |
|---|---|---|
| Previously saved schedule | Compare the intended time and amount with actual device/app information | A physical-button lock is not a schedule-off switch. |
| Physical FeedNow | Check whether the button was accessible and the lock setting was on | Current support says ButtonLock disables physical FeedNow. |
| App FeedNow | Check caretaker requests and the current app record where available | App FeedNow remains available with ButtonLock enabled. |
| Cause unknown | Keep time, bowl contents and observation limits together | Do not choose a cause just because one pathway is possible. |
Smart Feed FeedNow can provide an extra snack or meal, according to its guide. The older 2019 guide 400-2362 also describes using it for priming. A manual request therefore needs its own record; do not silently treat every such action as a replacement for the next scheduled meal.
The same printed guide describes an Activity Log, but its older interface and retention wording are not a verified current app feature here. Use the actual information your current app displays. If you cannot confirm a request or delivery, keep that uncertainty rather than inventing a device-log entry.
Use the current ButtonLock route and its limited effect
PetSafe’s current support says to open the MyPetSafe app, select the feeder and use its settings to enable ButtonLock. The control turns blue when active in the documented route. This disables the physical FeedNow button so a pet or child cannot use that button to dispense an extra meal.
The same support page explicitly says app FeedNow is still available. Enabling ButtonLock does not prevent an authorized caretaker from requesting food in the app. It does not establish an account-permission change, a locked food hopper or protection from a pet eating another animal’s food.
Check the setting on the actual model and current interface, and retain the intended schedule. If the app or control labels differ, use current maker support instead of borrowing a menu from another feeder. This page has not logged into an account, activated a real lock or tested the physical button.
If food continues to appear, record which pathways remain possible. A lock can close one input while leaving another open. Persistent unexplained output, an error signal or mechanical symptoms require the relevant manufacturer support; repeated factory resets are not a substitute for a clear event record.
Coordinate manual meals without sharing passwords
Agree who is responsible for the next manual action before anyone presses FeedNow. Record the intended amount, the reason for the request and whether it was actually confirmed. Then separately record observed delivery. A message saying “I fed the cat” can mean a request, food put in a bowl or witnessed intake; use the specific fact that is known.
For authorized household access, PetSafe’s current support provides a member-invitation route: feeder settings, Family Settings, Add Member, then the person’s nickname and email, followed by Add. Use that current account feature rather than sharing a password. Only invite someone you intend to authorize and keep private account information in your own household.
An invitation changes who can interact through the app; it is not a feeding event and does not prove a schedule was checked. Keep the meal agreement alongside the access arrangement. No invitation has been sent and no member/account has been added by this page.
When two people cover different shifts, include the actual event time and pathway in the handover. If food is already present and the previous event cannot be established, do not invent a missing amount to make a daily total look complete. Use the observed facts and your existing individualized feeding advice.
Two complete household control records
The physical lock is on but an app request remains possible
Hypothetical record: A hypothetical record shows ButtonLock active. Food appears at 15:00 outside the saved schedule. A caretaker confirms that they used app FeedNow at 15:00; nobody observed the full delivery or intake.
Decision: Keep the app request as the confirmed event. The active physical lock is compatible with that request; delivery amount and intake remain unconfirmed.
The lock closes physical FeedNow, not the app route. This record resolves a control-path misunderstanding without calling the lock broken. It does not prove how much food was dispensed or eaten because those observations were not made.
Two requests need two records, not an invented meal total
Hypothetical record: In a hypothetical handover, one caretaker reports requesting a 10 g-equivalent portion at 14:00 and another reports the same request at 14:05. They have not weighed output or checked the current device record.
Decision: Record two requests and the times. Do not label 20 g as observed delivery or automatically count either request as replacing a scheduled meal.
10+10=20 g is the total of the fictional requested amounts only. A volume-based setting may not actually be 10 g, either request may need confirmation, and delivery is a separate event. The useful correction is coordination and verified records rather than a fabricated daily intake number.
These are hypothetical examples for interpreting evidence. They are not device logs, pet observations or tests of a lock. Their conclusion is limited to the facts supplied in each record.
Keep the model difference and next action visible
Simply Feed FeedNow advances the next scheduled meal; Smart Feed FeedNow can request an extra snack or meal. Keep that distinction when a household uses both devices. A rule learned on one model cannot tell you how the other model’s next scheduled meal will behave.
For a Smart Feed connection problem, use the separate offline/reboot guide. For a splitter, record each bowl and each pet’s access separately. For unexplained mechanical dispensing, give the maker the actual model, current schedule, control settings and what was observed, rather than accusing a particular person or treating a possible cause as certain.
Download the editable record (TXT). Save your observations in your own copy; this page does not collect pet or household details.
Actual feeder model, app name and date: Intended scheduled times and amounts: Physical ButtonLock setting checked: Caretaker responsible for the next meal: Event time and pathway: scheduled / physical / app / unknown Requested amount and whether request actually confirmed: Food delivered: observed / not observed / amount unknown Food already present, leftovers and spills: Individual intake: known / unknown and evidence: Other caretaker action checked: Correction proposed and next observation:
A useful finished record distinguishes intended schedule, requests, observed output and known intake. When a stage is unknown, leave it unknown and choose the next observation or support action that can answer it.
Sources and further reading
- PetSafe: My PetSafe® Smart Feed Automatic Pet Feeder is Dispensing Meals Outside of the Scheduled TimePhysical FeedNow as a possible extra-meal cause; ButtonLock blocks that button while app FeedNow remains available.
- PetSafe: How To Add Another Household Member to the My PetSafe® AppCurrent Family Settings invitation route for authorized household members; an access invitation is not a feeding event.
- PetSafe: Smart Feed Automatic Dog and Cat Feeder, 2nd GenerationCurrent second-generation model list, 2.4GHz Wi-Fi, AC/backup power and Smart Feed feature scope.
- PetSafe: Smart Feed quick-start guide 400-2362, ©20192019 guide: safety and AC/backup scope, LED patterns and reboot/reset consequences, pages 2–3 and 5–7. Its older app name and minimum OS values do not establish current app compatibility.
- FeedPetWise: Healthy Pet Simply Feed Portion Check: Settings, Priming and GramsSimply Feed portion calibration, priming and its different advance-next-meal FeedNow behavior.