Symptoms
App position reaches 100% before physical curtain finishes.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: App position reaches 100% before physical curtain finishes.
- Comparison to run: Compare rail endpoints and controller position calibration with no obstructions.
- Pass condition: Position display matches fabric travel at both ends.
Why It Happens
A raw event is not the same thing as an automation action. Timing, state mapping, hub subscriptions and the physical device must be checked separately.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Motor travel limit miscalibrated — investigate this first only if the local state or controlled comparison supports it.
- Rail friction causes missed movement — a second layer that may survive a simple restart and requires a targeted check.
- Curtain direction was reversed — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Keep hands clear of moving curtains; never force a jammed motor. A smart-home event can be detected correctly by a sensor but then delayed or misread by the hub, bridge, cloud integration or automation rule. Separate raw sensor state from the action triggered by that state. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare rail endpoints and controller position calibration with no obstructions. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare rail endpoints and controller position calibration with no obstructions. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Remove visible obstructions and inspect rail safely. | This can expose or rule out motor travel limit miscalibrated without changing several settings together. |
| Inspect the deeper layer | Review motor stall detection and position feedback where provided. | Use the evidence to separate rail friction causes missed movement from curtain direction was reversed; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether rail friction causes missed movement is consistent with the evidence. If not, investigate curtain direction was reversed rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. App position reaches 100% before physical curtain finishes. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare rail endpoints and controller position calibration with no obstructions. Do not erase logs or reset the device yet. Remove visible obstructions and inspect rail safely. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Run the manufacturer's supported end-stop recalibration. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. Position display matches fabric travel at both ends. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider motor travel limit miscalibrated, rail friction causes missed movement and curtain direction was reversed separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare rail endpoints and controller position calibration with no obstructions. Review motor stall detection and position feedback where provided. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Have installer inspect curtain track and motor torque if repeated. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. Position display matches fabric travel at both ends. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating motor travel limit miscalibrated as certain before running the comparison: Compare rail endpoints and controller position calibration with no obstructions.
- Trying several changes at once, such as modifying rail friction causes missed movement and curtain direction was reversed simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Keep hands clear of moving curtains; never force a jammed motor.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Position display matches fabric travel at both ends.
- Repeat the original failing action under equivalent conditions: App position reaches 100% before physical curtain finishes.
- Run the control again: Compare rail endpoints and controller position calibration with no obstructions.
- Check the positive pass condition: Position display matches fabric travel at both ends.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Review motor stall detection and position feedback where provided. Have installer inspect curtain track and motor torque if repeated.
Give vendor support sanitized event times, hub model, raw-state transitions and firmware details; treat safety and access-control devices as safety equipment, not debugging toys.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare rail endpoints and controller position calibration with no obstructions.
- Preserve the corrected behavior: Position display matches fabric travel at both ends.
- Preserve hub backups and automation screenshots; test critical automations after hub, battery or time-zone changes.
- Review configuration or hardware changes that could reintroduce motor travel limit miscalibrated.
Frequently Asked Questions
Does this symptom prove motor travel limit miscalibrated?
No. Start with the controlled comparison: Compare rail endpoints and controller position calibration with no obstructions. Only treat motor travel limit miscalibrated as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Review motor stall detection and position feedback where provided. That helps determine whether rail friction causes missed movement or curtain direction was reversed fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Position display matches fabric travel at both ends. Keep a record of the working state for future troubleshooting.