KNX fan coil cross-check preview
The cross-check view keeps KNX source objects and Control4 candidates visible together so fan coil mode, setpoint, fan speed, valves and feedback can be reviewed before export.
Fan coil is more than a thermostat
A basic room thermostat can often be reviewed around setpoint and measured temperature. A fan coil usually adds fan speed, valve outputs, operating mode, demand logic and sometimes window or occupancy conditions that decide whether the unit is allowed to run.
The AI Assistant should surface those KNX channels together so the installer can decide whether Control4 should receive one climate device, separate status context, or a manual review item.
Signals to review from ETS
A flat group address list can hide whether fan speed is a one-byte percentage, a step selector, a set of binary outputs, or a vendor-specific object. The same applies to valves and heating/cooling state.
Before Composer creation, every fan coil candidate should keep command objects and feedback objects visible next to the generated Control4 room and device context.
- Measured room temperature, target setpoint and setpoint feedback.
- Heating/cooling mode, auto mode, protection mode and demand state.
- Fan speed command, fan speed feedback, step labels or percentage scale.
- Valve command, valve feedback, enable state and error/status objects.
- Window contact or occupancy conditions that can block HVAC operation.
Two-pipe, four-pipe and mode assumptions
Two-pipe and four-pipe fan coil systems can expose different command paths. Some projects use a shared valve with seasonal heating/cooling changeover, while others separate heating valve, cooling valve and fan demand.
That difference matters before Control4 is created. The page should not promise automatic climate mapping when the ETS project does not make the mode semantics clear.
Feedback and gateway visibility
Fan coil status often depends on feedback that must cross the correct KNX line and gateway path. A fan speed command without reliable feedback can make the Control4 interface look responsive while the real HVAC state is unknown.
The review should flag missing feedback, unclear DPTs, missing read flags or gateway visibility issues before the .codu handoff.
Separate HVAC add-on scope
Fan coil units sit outside the standard license count unless scoped specifically. Main pricing is based on lights, blinds, thermostats and KNX/IP gateways, while HVAC add-ons are scoped separately because fan coil object models vary heavily by project and manufacturer.
This keeps the base KNX to Control4 workflow accessible while still giving installers a structured way to review advanced HVAC where the ETS project contains enough information.
Composer handoff after review
Composer should receive fan coil scope only after setpoint, temperature, mode, fan speed, valves, feedback and blocking conditions are confirmed. Unclear channels should remain review items instead of being hidden in the create-only build.
The .codu package can carry the reviewed structure and notes so the Composer driver starts from explicit HVAC decisions.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Are KNX fan coil units included in the core device count?
Not by default. Fan coil HVAC is add-on scope. The main count remains lights, blinds, thermostats and KNX/IP gateways.
Can CoduWorks map KNX fan coil objects with AI?
It can prepare reviewable candidates from ETS, but the installer must confirm setpoints, modes, fan speed, valves, DPTs and feedback before Composer creation.
Why is fan speed difficult in Control4 KNX projects?
Fan speed may be modeled as steps, percentages, multiple binary objects or vendor-specific values. Command and feedback must be reviewed together.
What should be checked before exporting .codu?
Check setpoint, measured temperature, heating/cooling mode, fan speed, valve state, demand, feedback, gateway route and window or occupancy lockout.
Scope KNX fan coil before Composer
Import ETS, review fan coil channels with KNX context and export .codu only after HVAC scope is clear.