Symptoms
Scheduled meals occur an hour early or late after local clock transition. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: Scheduled meals occur an hour early or late after local clock transition.
- Control test: Compare feed time in app, device time zone and event log.
- A confirmed correction must meet this outcome: One meal arrives at the correct local time across a time-zone transition simulation where supported.
One successful test is a useful clue, but a reliable resolution should survive reopening the application or repeating the original workflow without extra workarounds.
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.
An apparent failure of the whole system can originate in one stage. In this case, investigate time zone wrong before treating local schedule stores UTC offset or duplicate rule created around transition as facts.
Three competing explanations
- Time zone wrong.
- Local schedule stores utc offset.
- Duplicate rule created around transition.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports time zone wrong does not automatically exclude local schedule stores UTC offset; 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. Maintain a manual feeding plan until proven stable.
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 feed time in app, device time zone and event log. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Time zone wrong | If the failing state changes under the comparison, time zone wrong is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Local schedule stores utc offset | If the first change has no effect but a supported configuration differs, local schedule stores UTC offset moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Duplicate rule created around transition | If both earlier paths are contradicted, investigate whether duplicate rule created around transition 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: Confirm region time-zone setting and set a short one-time test schedule. 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.
Capture the current behavior
Scheduled meals occur an hour early or late after local clock transition. 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 feed time in app, device time zone and event log. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Correct the supported setting
Confirm region time-zone setting and set a short one-time test schedule. 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
One meal arrives at the correct local time across a time-zone transition simulation where supported. 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 time zone wrong, local schedule stores UTC offset and duplicate rule created around transition separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Review event-level evidence
Inspect firmware schedule semantics and remove only a known duplicate event. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Isolate a second independent variable
Revisit the comparison: Compare feed time in app, device time zone and event log. If the first suspected cause is not supported, compare the behavior predicted by local schedule stores UTC offset with the behavior predicted by duplicate rule created around transition. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: One meal arrives at the correct local time across a time-zone transition simulation where supported. 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: Maintain a manual feeding plan until proven stable.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming time zone wrong is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare feed time in app, device time zone and event log.
- Skipping this safety boundary: Maintain a manual feeding plan until proven stable.
- 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: One meal arrives at the correct local time across a time-zone transition simulation where supported. 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 feed time in app, device time zone and event log.
- Check the stated pass result: One meal arrives at the correct local time across a time-zone transition simulation where supported.
- 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: Inspect firmware schedule semantics and remove only a known duplicate event. 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 time zone wrong, local schedule stores UTC offset and duplicate rule created around transition 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: One meal arrives at the correct local time across a time-zone transition simulation where supported. 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: Scheduled meals occur an hour early or late after local clock transition. 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 time zone wrong is responsible?
Run the controlled comparison: Compare feed time in app, device time zone and event log. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is local schedule stores UTC offset rather than time zone wrong?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Inspect firmware schedule semantics and remove only a known duplicate event. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: One meal arrives at the correct local time across a time-zone transition simulation where supported. If it fails after the normal workflow is repeated, document whether duplicate rule created around transition still explains the remaining behavior and escalate with non-sensitive observations.