When I review a blind motor control requirement at JIECANG, I start with one practical question: after the system sends a command, what evidence comes back? A shade may move when someone presses a button, yet the control platform may still have no current information about where it stopped. That distinction matters when a project depends on remote supervision, automated scenes, or coordinated operation across multiple rooms.
The key difference between unidirectional and bidirectional blind motor communication is whether information can return from the device. To confirm a blind's position or operating state, that return path must carry the required information to the final control interface, through a gateway where the system uses one. A command sent, an acknowledgment received, and a target position reached are separate events.
My approach is to define the required evidence first, then check the selected motor and complete control system against it. This guide focuses on that decision: what the system knows after a command, how that knowledge is obtained, and how buyers can verify it before approving a configuration. For the broader selection process, see our Smart Shading Motors Guide.
In this article, unidirectional and bidirectional describe the direction of communication. A motor with unidirectional communication can still raise and lower a compatible blind.
A unidirectional control path sends instructions such as open, close, or stop to the motor or receiver. The blind can execute those instructions and may support stored limits or a favorite position. However, that path does not return motor status to the sender.
A connected controller may keep a record of the last command or calculate a position from travel time. Those functions can be useful, but they are different from receiving a position report from the device. If another remote changes the blind position, the controller's stored assumption may no longer match the installation.
A bidirectional control path allows supported information to travel back. Depending on the configuration, this may include command acknowledgment, position, movement state, or other device data. The exact fields and reporting behavior must be confirmed for the selected model and interface.
For a bidirectional motor, verify which feedback fields the system provides. I would ask what comes back, which device produces it, when it updates, and where the information can be read.
| Project question | Unidirectional communication path | Bidirectional communication path |
|---|---|---|
| Can it send movement commands? | Yes, with compatible equipment | Yes, with compatible equipment |
| Can the motor use limits or presets? | May be supported | May be supported |
| Does this path return motor information? | No | Supported fields may be returned |
| Is a displayed position necessarily device-reported? | Check whether the value comes from an estimate or a separate sensor | Confirm the source and integration |
| Can the system confirm arrival at a target? | Requires another source of evidence | Depends on available reports and validation |
JIECANG provides separate tutorials for adding unidirectional and bidirectional devices. They offer useful setup context when checking the selected device and gateway combination. Pair the device, then verify the feedback fields available in the selected configuration.
Follow the VelaSmart tutorial for adding a bidirectional device. Verify supported feedback separately for the selected configuration.
Watch on JIECANGFollow the VelaSmart tutorial for adding a unidirectional device. Device enrollment does not establish a return path for position reports.
Watch on JIECANGI separate the evidence into four questions. This prevents a user interface message from being treated as stronger proof than the underlying information supports.
An app may confirm that it submitted a request. A gateway may confirm that it accepted that request. A device acknowledgment may confirm reception at another point in the chain. Each acknowledgment has a defined source and meaning. None should automatically be read as confirmation that the blind completed its movement.
A supported device may report a current position or a state such as moving or stopped. Ask whether the value is returned after a query, sent after an event, or refreshed on another schedule. Check position and movement state as separate fields.
A value can remain on screen after communication is lost. For a supervised installation, I would define how the platform handles old information: show a last-update time, mark the device unavailable, or otherwise distinguish the last known state from a current report. The required behavior belongs in the project specification.
A position report describes the device's position reference. Ask how that reference is obtained and calibrated. It may depend on internal sensing, movement counting, or another model-specific method. It should not be described as an independent measurement of the fabric or bottom bar unless that is actually how the system works.
For acceptance, compare reported positions with physical observations using an agreed method. A motor position report alone does not establish a universal positioning tolerance, identical hembar alignment, or detection of every mechanical problem.
A percentage control sets or displays a value. Its presence alone does not establish where that value comes from. Before relying on it, identify whether the interface shows the requested target, an estimated position, or the latest position returned by the device.
For example, selecting a percentage may send a target command. A displayed value could then change immediately, change as the blind moves, or update after a device report. The appearance of the interface is not enough to identify which behavior is implemented. Check the interface definition and test the complete system.
Also agree what the endpoints mean. One interface may describe percentage open while another describes percentage closed. Record the meaning of each endpoint, the movement direction, and how intermediate values are mapped. For Venetian blinds, clarify whether a value controls lift position or slat tilt.
The following JIECANG tutorial shows percentage operation in the app. Use it to understand the control interface, then confirm whether the displayed value is a target or a device-reported position for the selected motor and gateway.
Percentage-based operation in the app. Confirm the source and update behavior of the displayed position for your configuration.
Watch on JIECANGThe remote-control tutorial demonstrates a different way to request a position. It is useful alongside the app example because a command input and a feedback display serve different functions. A remote percentage command does not by itself demonstrate app synchronization.
Percentage operation using a handheld remote. Check separately whether the connected platform receives an updated position afterward.
Watch on JIECANGFor a broader discussion of the two control interfaces, read App Control vs Remote Control Roller Shades Motor.
Feedback becomes especially valuable when a decision depends on the resulting blind state. In a room where someone operates a blind and sees the result, a suitable unidirectional motor may meet the requirement. When staff supervise shades from elsewhere, they need a defined way to distinguish completed movement, an unavailable device, and an unconfirmed result.
Consider an illustrative room with app and handheld-remote control. The app requests one position, and a person later moves the shade with the remote. The important test is whether the app receives the new state without another app command. If it retains the old value, an automation may act on an outdated assumption.
Sending one command to a group does not establish that every shade reached its target. Where individual confirmation matters, request device-level results and define how missing or delayed responses are handled. Bidirectional communication alone does not guarantee simultaneous movement or identical physical alignment across different shade assemblies.
A shade may still respond locally when internet access is unavailable, while an app or remote-management platform cannot refresh its state. Test movement and status reporting separately. Our Local vs Cloud Control in Smart Blind Motors guide provides related planning context.
A supported motor report is useful only if the required information reaches the system that makes the decision. I would trace the complete path: motor or receiver, gateway where used, integration driver or API, and final app or building-control interface. Some architectures combine these functions, but the information still needs a clear source and destination.
At each boundary, confirm the data fields, device identity, update behavior, and failure handling. A gateway connection can be healthy while a particular motor is unavailable. Likewise, a platform can expose movement commands without exposing every feedback field supported elsewhere in the system.
Record the motor variant, gateway model, firmware, app, and integration version used for approval. Recheck relevant functions after a configuration change. The broader questions are covered in our smart blind motor compatibility guide.
Use the intended shade assembly and control equipment. Set the limits and verify direction before testing intermediate positions. Record both the requested target and returned state, together with physical observation and timestamps. Choose target points and repeat counts to suit the project, while respecting the motor's permitted operating and rest conditions.
I recommend the following acceptance scenarios. Agree on expected behavior and acceptance criteria before testing the functions required for your configuration.
| Test scenario | What to check | Evidence to record |
|---|---|---|
| App target command | Distinguish target value from returned position | Target, report, timestamps, physical observation |
| Remote operation | Whether the final interface updates afterward | Device ID, remote action, new report and update time |
| Stop during travel | Whether position and movement state update as specified | Stop action, reported values and observed position |
| Group operation | Whether required individual results are available | Per-device response and missing-response handling |
| Motor or gateway unavailable | Whether old values are identified appropriately | Last known value, availability indication and timeout |
| Internet disconnected | Which local controls and reports remain available | Separate movement and status results |
| Restart and reconnect | How state is restored or synchronized | Recovery sequence, fresh report and any calibration need |
Disconnect equipment only through an approved procedure. Do not create a mechanical obstruction merely to demonstrate a missing response. Communication loss can be tested without deliberately jamming a shade.
If a report is missing, record the result as unconfirmed and verify the shade state separately. Define whether the next step is a status query, a bounded retry, an alert, or an on-site check. Repeated movement commands without state awareness can make diagnosis harder.
For the wider sample-approval process, use our guide to blind motor compatibility testing before bulk orders.
A useful RFQ states the operational decision the feedback must support. "Bidirectional motor required" leaves too much open. Instead, identify which state the system needs to know and under which conditions it must know it.
Include these details in the request.
Use our Blind Motor RFQ Checklist to combine these feedback requirements with the mechanical, electrical, and commercial information needed for quotation.
Yes, depending on the model. A stored favorite position is a motor control feature. It does not require that the motor return its current position through the same control path. Confirm preset support and reporting capability separately.
A hub can provide a user interface or automation functions, but it does not automatically create a return channel from a unidirectional motor. Identify whether the displayed state comes from a motor report, a separate sensor, or an estimate.
Not necessarily. Supported fields and update behavior depend on the device and integration. Confirm whether reports are event-based, queried, periodic, or available only under defined conditions. Specify update requirements that match the application.
It can support that judgment when the reference, calibration, installation, and physical verification are suitable. A reported endpoint alone should not be described as proof of complete fabric coverage or every mechanical condition. Define what "closed" means for the project.
That must be verified on the selected configuration. Operate the shade using the remote, then check whether the final interface receives a fresh position or state without requiring another app command.
Review these motor models and confirm the communication mode and available position reports for the exact variant and control setup.
My recommendation is to approve the complete evidence path: the command, the returned information, its freshness, and its relationship to the physical shade. Select unidirectional control when it meets the actual operational requirement. Specify and test feedback from a bidirectional motor when a system needs to know the result after a command.
For a JIECANG project review, send the blind type, intended motor configuration, control platform, gateway where applicable, and the states your system must confirm. Include the required response behavior and sample acceptance scenarios. Those details give our team a practical basis for reviewing the proposed configuration and identifying the functions that need verification.
Ready to verify your blind motor feedback requirements?
Head Office Address:No.2 Laisheng Road, Provincial High-tech industrial park, Xinchang county, Zhejiang province, China
E-mail:jc35@jiecang.com
Telephone:+86 4006666358 +616-952-0630(US)