Symptoms
The phone graph jumps after probe maintenance but test strips show no similar change. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: The phone graph jumps after probe maintenance but test strips show no similar change.
- Control test: Compare a fresh calibration standard and independent water sample before dosing.
- A confirmed correction must meet this outcome: pH reading agrees with a reliable reference across two samples.
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 probe not recalibrated or sensor not fully rinsed explains the observed difference. Temperature compensation mismatch remains another plausible explanation until the comparison rules it out.
Three competing explanations
- Probe not recalibrated.
- Sensor not fully rinsed.
- Temperature compensation mismatch.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports probe not recalibrated does not automatically exclude sensor not fully rinsed; 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. Never adjust tank chemistry based on one unverified sensor.
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 a fresh calibration standard and independent water sample before dosing. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Probe not recalibrated | If the failing state changes under the comparison, probe not recalibrated is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Sensor not fully rinsed | If the first change has no effect but a supported configuration differs, sensor not fully rinsed moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Temperature compensation mismatch | If both earlier paths are contradicted, investigate whether temperature compensation mismatch 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: Stop automatic dosing based on the suspect reading and verify a separate reference. 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.
Verify the affected workflow
The phone graph jumps after probe maintenance but test strips show no similar change. 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 a fresh calibration standard and independent water sample before dosing. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Try the smallest safe intervention
Stop automatic dosing based on the suspect reading and verify a separate reference. 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
pH reading agrees with a reliable reference across two samples. 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 probe not recalibrated, sensor not fully rinsed and temperature compensation mismatch separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Check the responsible subsystem
Follow sensor calibration protocol and inspect probe age and temperature compensation. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Validate the unaffected path
Revisit the comparison: Compare a fresh calibration standard and independent water sample before dosing. If the first suspected cause is not supported, compare the behavior predicted by sensor not fully rinsed with the behavior predicted by temperature compensation mismatch. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: pH reading agrees with a reliable reference across two samples. 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: Never adjust tank chemistry based on one unverified sensor.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming probe not recalibrated is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare a fresh calibration standard and independent water sample before dosing.
- Skipping this safety boundary: Never adjust tank chemistry based on one unverified sensor.
- 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: pH reading agrees with a reliable reference across two samples. 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 a fresh calibration standard and independent water sample before dosing.
- Check the stated pass result: pH reading agrees with a reliable reference across two samples.
- 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: Follow sensor calibration protocol and inspect probe age and temperature compensation. 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 probe not recalibrated, sensor not fully rinsed and temperature compensation mismatch 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: pH reading agrees with a reliable reference across two samples. 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 phone graph jumps after probe maintenance but test strips show no similar change. 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 probe not recalibrated is responsible?
Run the controlled comparison: Compare a fresh calibration standard and independent water sample before dosing. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is sensor not fully rinsed rather than probe not recalibrated?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Follow sensor calibration protocol and inspect probe age and temperature compensation. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: pH reading agrees with a reliable reference across two samples. If it fails after the normal workflow is repeated, document whether temperature compensation mismatch still explains the remaining behavior and escalate with non-sensitive observations.