Symptoms
Keypad unlocks with a valid guest PIN while the app marks that code invalid. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: Keypad unlocks with a valid guest PIN while the app marks that code invalid.
- Control test: Compare guest code status on lock versus cloud account, without exposing the digits.
- A confirmed correction must meet this outcome: App and keypad agree on guest code state and time window.
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 video stream, a cloud acknowledgment and a physical door release represent different subsystems. Access credentials, egress safety and residents' permissions take precedence over convenience changes.
The important distinction is whether offline keypad code not synced or guest code schedule mismatch explains the observed difference. Different lock selected remains another plausible explanation until the comparison rules it out.
Three competing explanations
- Offline keypad code not synced.
- Guest code schedule mismatch.
- Different lock selected.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports offline keypad code not synced does not automatically exclude guest code schedule mismatch; the comparison needs to separate them.
Before Making Changes
Protect legitimate emergency entry and fire egress. Change permissions only through the authorized owner or building administrator. Never revoke the only safe emergency entry method.
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 guest code status on lock versus cloud account, without exposing the digits. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Offline keypad code not synced | If the failing state changes under the comparison, offline keypad code not synced is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Guest code schedule mismatch | If the first change has no effect but a supported configuration differs, guest code schedule mismatch moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Different lock selected | If both earlier paths are contradicted, investigate whether different lock selected 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 the selected lock and code validity time while preserving active access. 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
Keypad unlocks with a valid guest PIN while the app marks that code invalid. 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 guest code status on lock versus cloud account, without exposing the digits. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Apply a targeted reversible correction
Confirm the selected lock and code validity time while preserving active access. 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
App and keypad agree on guest code state and time window. 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 offline keypad code not synced, guest code schedule mismatch and different lock selected separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Inspect supported diagnostic records
Compare lock audit history and cloud sync status; regenerate a code only after providing safe alternate entry. 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 guest code status on lock versus cloud account, without exposing the digits. If the first suspected cause is not supported, compare the behavior predicted by guest code schedule mismatch with the behavior predicted by different lock selected. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: App and keypad agree on guest code state and time window. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the device owner, building manager or access-control service provider. Safety boundary: Never revoke the only safe emergency entry method.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming offline keypad code not synced is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare guest code status on lock versus cloud account, without exposing the digits.
- Skipping this safety boundary: Never revoke the only safe emergency entry method.
- 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: App and keypad agree on guest code state and time window. 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 guest code status on lock versus cloud account, without exposing the digits.
- Check the stated pass result: App and keypad agree on guest code state and time window.
- 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: Compare lock audit history and cloud sync status; regenerate a code only after providing safe alternate entry. 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 device owner, building manager or access-control service provider, 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 offline keypad code not synced, guest code schedule mismatch and different lock selected 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: App and keypad agree on guest code state and time window. 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: Keypad unlocks with a valid guest PIN while the app marks that code invalid. 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 offline keypad code not synced is responsible?
Run the controlled comparison: Compare guest code status on lock versus cloud account, without exposing the digits. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is guest code schedule mismatch rather than offline keypad code not synced?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Compare lock audit history and cloud sync status; regenerate a code only after providing safe alternate entry. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: App and keypad agree on guest code state and time window. If it fails after the normal workflow is repeated, document whether different lock selected still explains the remaining behavior and escalate with non-sensitive observations.