Symptoms
The feeder releases two scheduled portions when Wi-Fi returns after an outage. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: The feeder releases two scheduled portions when Wi-Fi returns after an outage.
- Control test: Compare local schedule with cloud app schedule and feed history.
- A confirmed correction must meet this outcome: Exactly one test portion dispenses per scheduled event.
Write down the exact sequence that reproduces the failure and the moment it stops. Intermittent failures are easiest to isolate when the same short test is repeated before and after one change.
Why It Happens
A pet device may use a local schedule, a cloud schedule and intermittently delivered sensor reports. Confirm which state is current before acting on feeding, containment or location alerts.
The important distinction is whether duplicate schedule stored in cloud and device or replayed queued command explains the observed difference. Clock shifted during outage remains another plausible explanation until the comparison rules it out.
Three competing explanations
- Duplicate schedule stored in cloud and device.
- Replayed queued command.
- Clock shifted during outage.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports duplicate schedule stored in cloud and device does not automatically exclude replayed queued command; the comparison needs to separate them.
Before Making Changes
Provide an independent safe way to feed, water, locate or admit the animal while the connected device is being tested. Keep animals supervised until portions are reliable.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare local schedule with cloud app schedule and feed history. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Duplicate schedule stored in cloud and device | If the failing state changes under the comparison, duplicate schedule stored in cloud and device is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Replayed queued command | If the first change has no effect but a supported configuration differs, replayed queued command moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Clock shifted during outage | If both earlier paths are contradicted, investigate whether clock shifted during outage accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Turn off remote extra-feed rules and observe an empty test with food safely removed. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Identify the exact failure
The feeder releases two scheduled portions when Wi-Fi returns after an outage. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare local schedule with cloud app schedule and feed history. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Apply a targeted reversible correction
Turn off remote extra-feed rules and observe an empty test with food safely removed. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
Exactly one test portion dispenses per scheduled event. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for duplicate schedule stored in cloud and device, replayed queued command and clock shifted during outage separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Inspect supported diagnostic records
Audit event timestamps and firmware behavior; report duplicated command IDs to vendor. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Test the alternative explanation
Revisit the comparison: Compare local schedule with cloud app schedule and feed history. If the first suspected cause is not supported, compare the behavior predicted by replayed queued command with the behavior predicted by clock shifted during outage. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: Exactly one test portion dispenses per scheduled event. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the pet-device manufacturer and a safe manual care plan. Safety boundary: Keep animals supervised until portions are reliable.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming duplicate schedule stored in cloud and device is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare local schedule with cloud app schedule and feed history.
- Skipping this safety boundary: Keep animals supervised until portions are reliable.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: Exactly one test portion dispenses per scheduled event. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare local schedule with cloud app schedule and feed history.
- Check the stated pass result: Exactly one test portion dispenses per scheduled event.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Audit event timestamps and firmware behavior; report duplicated command IDs to vendor. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the pet-device manufacturer and a safe manual care plan, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether duplicate schedule stored in cloud and device, replayed queued command and clock shifted during outage were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: Exactly one test portion dispenses per scheduled event. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: The feeder releases two scheduled portions when Wi-Fi returns after an outage. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether duplicate schedule stored in cloud and device is responsible?
Run the controlled comparison: Compare local schedule with cloud app schedule and feed history. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is replayed queued command rather than duplicate schedule stored in cloud and device?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Audit event timestamps and firmware behavior; report duplicated command IDs to vendor. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: Exactly one test portion dispenses per scheduled event. If it fails after the normal workflow is repeated, document whether clock shifted during outage still explains the remaining behavior and escalate with non-sensitive observations.