KNX blind actuator review preview
The preview shows repeated KNX blind channels and Control4 candidates being reviewed before export, including naming, room alignment, Move, Step/Stop, Position, Angle, DPT 5.001 feedback and safety context.
The actuator channel is the real source
Many ETS projects name blinds by room, but the actual control path lives on the actuator channel. A single motor can have Move, Step/Stop, Position, Angle, Info Position, Angle Position and status objects that need to be treated as one functional group.
If those objects are split or named inconsistently, Control4 may show a shade device that moves but cannot report the correct height, slat angle or upper/lower end-position state.
Signals to review from ETS
The review should separate user-facing blind control from actuator diagnostics, safety lockouts and manufacturer-specific parameters. This keeps the .codu package clean and avoids creating confusing devices in Composer.
- Move up/down, Step/Stop and limited up/down commands.
- Position height command and DPT 5.001 position feedback from Info Position objects.
- Angle command and Angle Position feedback for venetian blinds or jalousies.
- Travel time, direction inversion, reference movement, calibration assumptions and 0/100 percent convention.
- Wind, rain, frost, intrusion, fire, block or forced-operation objects that may prevent actuator movement.
Slat angle and position are separate decisions
Roller shutters may only need Move, Step/Stop and Position. Venetian blinds or exterior jalousies often need Angle as a separate value. In Control4 and ETS review, height and slat are not the same decision.
Control4 documentation describes height as 0 percent top and 100 percent bottom, while slat position can use 0 percent open and 100 percent closed. The installer should confirm whether Control4 should expose slat control, hide it, or keep it as manual Composer scope.
Weather protection should stay visible
Wind, rain and frost alarms can be safety-critical. KNX actuator models can also include intrusion and fire behavior, plus priority rules that block normal operation while an alarm is active.
If the actuator is already protected by KNX logic, the Control4 handoff should respect that boundary and avoid replacing proven field logic with incomplete Composer assumptions.
How actuator channels affect device count
A blind or shutter actuator channel that becomes a Control4 blind counts as a blind device in the tier. Diagnostic, lockout, weather or keypad objects around it do not become extra blind devices by themselves.
This distinction keeps pricing tied to the actual lights, blinds, thermostats and KNX/IP gateways that are generated, while still keeping the actuator context available for review.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Is each KNX shutter actuator channel a Control4 blind?
Only if the channel has enough reviewed command and feedback context to become a user-facing blind or shade. Diagnostics, alarms, lockouts and manufacturer parameters are review context.
Why does 0 and 100 percent need review?
Height and slat conventions can differ. Control4 actuator documentation uses height 0 percent as top and 100 percent as bottom, while slat position can use 0 percent open and 100 percent closed.
Should slat angle be created automatically?
Not without review. Slat angle is separate from height position and may need a specific Control4 UI or manual Composer scope.
Which Control4 KNX actuator files are relevant?
Common official references are C4-KNX-4BRS with KNXPROD JRA/S 4.230.1.41 and C4-KNX-8BRS with JRA/S 8.230.1.41, programmed in ETS 5.6.6 or greater.
Do wind or rain lockouts count as blind devices?
No. Weather and safety objects are context unless a project-specific add-on is confirmed.
Review blind actuators before Composer
Import ETS, group C4-KNX-4BRS/8BRS or other actuator channels, confirm position and slat feedback, then export a clean .codu package.