Buyer decision guide
Do Motorized Shades Work Without Internet? Plan and Verify Local Control
Learn how internet, Wi-Fi, gateway, controller and motor power failures affect different shade functions—and what must be documented and tested.
Quick Answer
Internet failure is only one possible fault. A shade may depend on local power, a motor receiver, wall control, router, gateway, cloud service or automation controller in different combinations. Record the selected path, required fallback and responsible test. Do not assume that remote-app loss means local operation is lost—or that local operation survives—without documentation and a representative test.
Dependency and Survival Matrix
| Layer / condition | What changed | Potential impact | Possible fallback to verify | Evidence / test | Owner |
|---|---|---|---|---|---|
| Internet / WAN unavailable | Off-site connection or cloud path cannot be reached | Remote access, cloud routines or account services may be affected | Documented onsite control, if the selected path supports it | Current architecture and WAN-loss test | Integrator / IT |
| Wi-Fi or router unavailable | Local IP network is unavailable | App, gateway or controller communication may be affected | Documented non-IP local input, if included | Network topology and router-loss test | IT / integrator |
| Gateway unavailable | Bridge between control methods is offline | Gateway-dependent commands may stop | Native or wired local input, only if documented | Gateway role and disconnect test | Integrator |
| Automation controller unavailable | Central logic/controller cannot issue commands | Scenes, schedules or central UI may stop | Documented local wall/remote path | Controller-loss test and recovery owner | Integrator / operator |
| Local wall control unavailable | User input or local device is unavailable | Local command may be lost even while central control works | Another documented local/central path | Input mapping and failure observation | Integrator / electrician |
| Motor power unavailable | Motor-side supply is absent | Motor cannot move regardless of network state | No assumed fallback; diagnose the selected power path safely | Power architecture and qualified electrical review | Electrician / service owner |
Internet Failure Is Not Controller or Power Failure
Remote app availability
Depends on the selected account, app, cloud, network and gateway path.
Local operation
May use a wall input, receiver or controller, but only the named configuration can prove it.
Motor movement
Requires the documented motor-side supply and working equipment; network access cannot replace power.
Plan the Test Without Inventing Behavior
- List the functions that must be available during normal operation.
- Disconnect one agreed dependency at a time without altering unsafe wiring.
- Record expected behavior before the test and observed behavior afterward.
- Use PASS, FAIL, NOT_TESTED or NOT_APPLICABLE. Blank or untested is not PASS.
- Assign recovery, account, network and electrical responsibilities before handover.
Use the existing Control Bench-Test Acceptance Record for the exact selected build; this page does not recreate that record.
What the Buyer Provides and Receives
| Buyer provides | Saiwenna reviews | Review output |
|---|---|---|
| Motor/controller/gateway and versions | Documented dependency path | Layer map and missing evidence |
| Required local/remote functions | Native/interface/gateway behavior | Function-to-path questions |
| Network/control diagram | Ownership and commissioning boundary | Responsible test and open items |
| Required fallback conditions | Selected documentation and test scope | Conditional acceptance route, not a guarantee |
Synthetic Failure-Layer Example
A residence requires wall operation even when internet access is unavailable. The proposed app path also uses a gateway. The team must not infer that the wall input bypasses the gateway. It records the exact wiring and controller path, tests WAN loss separately from gateway loss, and keeps each result tied to the tested version. Synthetic planning example—not a completed Saiwenna project.
Send a Reviewable Brief
Send the motor/controller/gateway models, diagram, required local fallback and functions that must remain available.