Split unit HVAC cross-check preview
The cross-check view keeps KNX source objects and proposed Control4 structure visible together so split unit HVAC, remote model, mode, fan speed and state candidates can be reviewed before export.
Why split units are not normal thermostats
A room thermostat may expose temperature, setpoint and operating mode. A split unit gateway can also depend on infrared command support, vendor remote model compatibility, fan speed tables, horizontal and vertical swing, silent mode and gateway-specific KNX parameters.
That makes the project more sensitive to assumptions. A light can often be reviewed as command plus feedback; a split unit needs the installer to confirm how each HVAC command is represented, which remote model is selected and whether the physical unit can actually accept the requested control path.
Official gateway setup stays separate
Control4 documentation identifies the device as Split Unit Gateway, FM, SKU C4-KNX-SUAC, with KNXPROD SUG/U1.41 available through ctrl4.co/knx-suac and the Control4 KNX Tool through ctrl4.co/knx-tool. ETS 5.6.6 or later and the SUG/U 1.41 app are commissioning requirements.
CoduWorks should not pretend to commission the IR database or replace the official supported remote model list. Its role is to read the ETS project, surface HVAC object families and help the installer decide what belongs in a reviewed Composer handoff.
- Gateway device, ETS application and Control4 KNX Tool checks happen outside the core build.
- Remote model compatibility is a commissioning requirement, not a naming cleanup task.
- The gateway may appear in ETS under Manufacturers / Control4 / Heating Ventilation Air conditioning.
- The .codu export should include only reviewed Control4 structure and clear scope.
KNX signals to review before Composer
Before any Control4 climate device is planned, the installer should see on/off, operating mode, setpoint command, setpoint limits, measured temperature, fan speed, swing or vane signals, silent mode, boost, error/status and available state objects together.
If those signals are spread across inconsistent names or different DPT families, the AI Assistant can group candidates for review, but the final HVAC behavior still needs installer confirmation.
- On/off, operating mode and heating/cooling state.
- Setpoint command, setpoint feedback and measured room temperature.
- Fan speed command, fan speed feedback and optional swing or vane signals.
- Door/window contacts that may block or condition HVAC behavior.
Unidirectional IR state needs explicit review
The Split Unit Gateway sends infrared commands to the split unit. If the physical air conditioner is also used with its original remote, or if it is not ready to receive an IR command, the gateway state can drift away from the real unit state.
That is why CoduWorks treats mini split HVAC as a review item. The .codu package should not hide uncertain mode, fan speed or feedback assumptions inside an automatic build.
- Do not treat remote control compatibility as solved by the .knxproj alone.
- Confirm which status objects are real KNX feedback and which are gateway-side assumptions.
- Keep unclear split unit mappings out of the create-only Composer plan until reviewed.
Scope and pricing boundary
Split unit HVAC is outside the standard CoduWorks license count unless scoped specifically. The main count remains lights, blinds, thermostats and KNX/IP gateways. HVAC needs separate scoping because each gateway, room controller and manufacturer can model controls differently.
This keeps the base project accessible while still allowing HVAC to be reviewed as a professional add-on when the ETS project contains enough context.
Composer handoff for mini split projects
Composer should receive HVAC scope only after the gateway path, mode semantics, DPTs, state assumptions and supported unit model are clear. If the split unit mapping is uncertain, it should remain a review item instead of being hidden inside the core create-only package.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Does CoduWorks automatically create KNX split unit HVAC devices?
Not by default. Split unit HVAC is treated as add-on review scope. The main automatic count focuses on lights, blinds, thermostats and KNX/IP gateways.
Does CoduWorks replace the Control4 KNX Tool or SUG/U 1.41 ETS app?
No. The official KNXPROD SUG/U1.41, SUG/U 1.41 ETS app, supported remote model selection and Control4 KNX Tool checks remain part of gateway commissioning. CoduWorks reviews the exported ETS project and prepares a clean Composer handoff.
Why is a split unit gateway different from a thermostat?
A split unit gateway may depend on IR remote compatibility, fan speed tables, mode values and manufacturer-specific KNX parameters in addition to setpoint and temperature objects.
Is split unit feedback guaranteed?
No. The IR path can be unidirectional, so the gateway may not know the real physical state if the air conditioner is operated by its original remote or misses a command. State objects and feedback assumptions must be reviewed.
What should be checked before Composer?
Check gateway setup, C4-KNX-SUAC / SUG/U1.41 application, supported remote model, operating modes, DPTs, setpoints, fan speed, swing, status assumptions and any window contact conditions that affect HVAC behavior.
Scope KNX split unit HVAC before Composer
Import ETS, review split unit gateway objects, remote model assumptions and available state objects, then keep HVAC decisions separate from the core light, blind and gateway build.