Motors & Controls / Integration Center
Motor & Control Integration for Project Shading
Motorized shading is not compatible by slogan. The control path depends on the product, selected motor, power, controller, gateway or bridge, required commands and the project team responsible for programming and commissioning. This center shows what is documented, what is configuration-specific and what must be reviewed before quotation.
What We Review
Product family, motor model, power and control version.
RF, app, RS485, dry contact or other documented motor-side path.
Exact hardware, supported-motor list, app, account and region.
Wiring, third-party programming, testing and commissioning ownership.
Control Architecture Overview
NATIVE means the documented selected device provides the capability. VIA_MOTOR, VIA_CONTROLLER, VIA_GATEWAY, VIA_BRIDGE, VIA_DRY_CONTACT and VIA_RS485 identify the actual technical boundary. PROJECT_SPECIFIC means the final architecture must be reviewed against the selected equipment. NOT_VERIFIED means no public availability claim is made.
Public Compatibility Matrix
Every cell below is configuration-limited. It is a procurement map, not a universal compatibility table.
| Product/System | Power | RF | App / Tuya | Zigbee | RS485 | Dry Contact | KNX | Matter | Project Integration |
|---|---|---|---|---|---|---|---|---|---|
| Motorized curtain tracks | Wired or rechargeable by selected motor | Available on selected configurations | Available on selected configurations | Configuration review; gateway required where offered | Selected models; protocol verification required | Selected models; I/O verification required | Project-specific; exact interface required | Not currently verified for this family | BMS/Lutron review by architecture |
| Roller, Roman, Zebra and Shangri-La shades | Wired or rechargeable by selected motor | Available on selected configurations | Available on selected configurations | Configuration review; gateway required | Selected configurations; protocol review | Selected configurations; command review | No native public mapping verified | Selected AM25LE/A-M motor only after product/load review | Project-specific |
| Honeycomb, Venetian, wood and fabric blinds | Varies by motor family | Available on selected configurations | Available on selected configurations | Configuration review; gateway required | Selected configurations; protocol review | Selected configurations by motor family | No native public mapping verified | Not currently verified | Project-specific |
| AM25LE/A-M selected motor | Rechargeable; 5V Type-C charging | Native 433MHz remote path | Not the documented path | Not the documented path | Not verified | Not verified | Not verified | Native on this selected motor; QR pairing | Apple Home, Amazon Alexa or Google Home setup per manual |
| AC801 / AC802 / AC803 bridge | 5V 1A Type-C | Radio+ variants by bridge model | 2.4GHz Wi-Fi bridge/app path | Not documented | RJ11 interface documented | Not documented | Not documented | Not documented | Gateway path; exact supported motor required |
| Lutron-controlled project review | Defined by selected Lutron system/project | System-specific | Not implied | Not implied | Only if separately documented | Only if separately documented | Not implied | Not implied | Selected native Lutron systems or documented interface; project-specific |
RF & Local Control
RF control is documented for selected motor configurations. Frequency, remote type, channel count, grouping and motor pairing must be confirmed for the exact motor. One documented selected motor, AM25LE/A-M, uses a 433 MHz remote path; that frequency is not generalized to other motor families.
App, Tuya & Zigbee Paths
Tuya control is configuration-specific: the label alone does not identify whether the path is Wi-Fi, Zigbee, motor-native or controller-based. For the selected Tuya Zigbee configurations, a gateway is required. The exact motor, gateway, region, app/account and platform must still be matched before quotation. Saiwenna does not claim that every product works with every Zigbee hub.
Verified AC801-Series Bridge Facts
The AC801, AC802 and AC803 guide documents 2.4 GHz Wi-Fi, RS485 through RJ11, Radio+, 5V 1A Type-C power, firmware update, and stated limits of up to 30 motors, 50 scenes, 30 timers and 20 rooms. The bridge variants are listed as AC801 433 MHz, AC802 447 MHz and AC803 429 MHz. The guide does not provide a complete supported-motor list, so the exact bridge and motor pairing remains a required review item.
RS485
Seeing an RS485 connector is not the same as proving protocol compatibility. Request the protocol, addressing, topology, command list and feedback behavior for the exact selected model.
Dry Contact
Dry contact is documented on selected configurations. The available commands, electrical requirements and whether any feedback exists must be confirmed by model. Dry contact does not imply position reporting or bidirectional data.
KNX & BMS Requests
BMS is a project context, not a protocol. A BMS request must identify the selected control system, motor/controller, required commands, feedback expectations, interface hardware and commissioning responsibility. KNX requests require project review because an exact native KNX motor/controller, datapoint set and approved project mapping are not currently verified for a public compatibility claim. KNX therefore remains project-specific and requires a documented interface path.
Matter-Capable Selected Configuration
The AM25LE/A-M quick-start guide documents Matter QR pairing for that selected rechargeable motor, together with 433 MHz remote control and 5V Type-C charging. The guide shows setup through Apple Home, Amazon Alexa and Google Home. This is an exact selected-motor claim; it does not mean all Saiwenna blinds or motors support Matter.
Lutron-Controlled Projects
A real U.S. residential project provides evidence for selected Lutron-native shading paths and a project-specific interface discussion. Saiwenna can review the shading system, motor/interface requirements, framing, pre-wire and quotation inputs. Final Lutron models, wiring, programming and commissioning responsibilities remain with the documented project scope and integrator.
Review the Lutron project-integration pathway · See the anonymized U.S. quotation/configuration case
Completed Large-Scale Control Reference
For a historical completed-project perspective, review the Inner Mongolia power dispatch command-center motorized roller-blind reference. The completed supplier-network evidence records a large motorized deployment and project-specific control workflow; it does not imply that the same control architecture is standard for every Saiwenna project.
Project Responsibility Matrix
| Scope | Typical Owner | Confirmation Required |
|---|---|---|
| Shading product and supplied motor/controller selection | Saiwenna within the quoted supply scope | Product, size, power, interface and selected model |
| Third-party control design and programming | Customer-appointed integrator | Platform, gateway/interface, commands, feedback and software scope |
| Site wiring, power and installation provisions | Contractor / electrician / installer | Approved drawings, local code and access requirements |
| Gateway, interface, testing and commissioning | Project-specific | Named equipment, owner, test plan and handover criteria |
Controls and integration working resource
Motor & Control Compatibility Matrix
Organize the shading-system, power, control and responsibility inputs needed for a configuration review.
What this resource does and does not confirm
The workbook structures project inputs. It does not confirm a motor, controller, gateway, protocol path or third-party interface until the exact project configuration is reviewed.
Safe selection framework
- Define the project context. Identify the shading system, opening schedule, quantity, buyer role and project stage.
- Record the requested interfaces. Capture project power, control outcome, cable route and handoff information supplied by the responsible disciplines.
- Keep selection reviewable. Leave final equipment fields open until drive-selection inputs and project responsibilities are reviewed together.
Required project inputs
- Buyer role. State the role coordinating the request so review questions reach the correct project discipline.
- Project stage. Identify the current project stage so the submission can be reviewed in the right sequence.
- Product or system type. Describe the requested shading system in buyer terms and flag uncertain classification for review.
- Location identifiers. Use the project’s floor, room and opening labels consistently across drawings and schedules.
- Opening geometry. Record project dimensions and the measurement basis for each identified opening.
- Quantity. Provide quantity by opening or item group and keep unlike configurations separate.
- Drive-selection inputs. Record the requested drive position and selection inputs; leave final equipment fields for project review.
- Power-supply inputs. Record the project power information supplied by the electrical team without inferring equipment suitability.
- Control requirement and protocol. Describe the requested control outcome and any protocol identified by the project controls team.
- Cable route and power point. Mark proposed cable routes, handoff points and power-point locations on the coordinated drawing.
- Installation responsibility. Record the proposed responsibility for preparation, installation, connection, testing and approval.
- Drawing revision reference. Identify the drawing issue and revision used for the submission.
- Project destination. State the destination needed for document, delivery and coordination review.
Use the working download
Download the blank working resource, complete only known project inputs, and keep uncertain selections open for review.
Continue the project workflow
- Technical & Project Resources
- Smart-home integrator pathway
- Wiring and Integration Guide
- BOQ and Window Schedule
- Use the preserved final control-review route below when the project inputs are ready.
Public Control Document
Download the Motor & Control Compatibility Matrix (XLSX) for a concise configuration-scoped matrix, or browse the Technical & Project Resources center.
What We Need Before Quotation
- Product/window type, dimensions and quantity
- Power available at each opening
- Control platform and exact controller/gateway if already selected
- Required commands, grouping and feedback
- Wiring or automation drawing
- Third-party integrator contact or responsibility matrix where applicable
- Country, project type and commissioning expectations
Organize quotation inputs with the RFQ workbook before configuration-specific motor, gateway or interface review.
Custom Lighting and Remote-Control Engineering
RGB lighting is not a standard motor function, and custom remote controls require separate review of power, protocols, hardware and sample validation. Use the RGB lighting and custom remote-control guide before requesting a project-specific development review.
Related Guides & Real Cases
Tuya vs Zigbee vs RF · KNX vs RS485 vs dry contact · BMS integration guide · Dubai dry-contact review
Plan the Power Context Before Freezing the Control Path
Use the voltage and power guide to prepare destination supply, motor-selection and responsibility inputs before an interface is confirmed.
Request a Control Compatibility Review
Send the product, dimensions, power, control platform, required commands, feedback needs and any wiring or integration drawing. We will identify the motor, controller, gateway or interface evidence required before quotation.