KNX underfloor heating cross-check preview
The cross-check view keeps KNX source objects and Control4 candidates visible together so heating zones, setpoints, valve actuators and feedback can be reviewed before export.
Floor heating is not always one thermostat
A radiant floor system may expose one room controller per zone, one heating actuator per manifold, separate valve outputs, pump demand, heating enable and temperature feedback. Control4 should not receive a neat thermostat device until the installer knows which objects belong together.
That is the value of the preflight step: the KNX source stays visible while the Control4 candidate structure is reviewed.
Signals to review from ETS
The ETS project should show how each heating zone is controlled and measured. A flat group address list can hide the relationship between room name, manifold loop, valve channel and thermostat UI.
CoduWorks should group candidates for review, not silently decide that every heating object is a final Control4 climate device.
- Measured room temperature, target setpoint and setpoint feedback.
- Floor temperature sensor, slab protection or max floor limit where present.
- Heating demand, valve open/close or valve percentage feedback.
- Heating enable, eco/protection modes, schedules and window contact lockout.
- Manifold channel, actuator output and real room name alignment.
Room names and loop mapping matter
Underfloor heating is sensitive to naming mistakes because the physical loop may not match the visible room label in ETS. A wrong link can make the Control4 interface show the right room while controlling the wrong valve channel.
Before export, the installer should confirm the relation between ETS room, heating zone, manifold output and any thermostat or sensor shown to the user.
Separate add-on scope and pricing
Underfloor heating does not belong in the standard device tier by default. The counted scope stays focused on lights, blinds, thermostats and KNX/IP gateways, while HVAC zones are scoped separately because the object model changes by project.
That keeps the base build predictable and keeps heating work reviewable instead of hiding it inside a generic device count.
Composer handoff after review
Composer should only receive floor heating scope after the zone model, setpoint semantics, feedback and actuator mapping are clear. Uncertain zones should remain review items, not automatic create-only devices.
The .codu package can carry the reviewed structure and notes so the driver build starts from explicit decisions instead of loose ETS assumptions.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Is KNX underfloor heating included in the core device count?
Not by default. Underfloor heating is HVAC add-on scope. The main count remains lights, blinds, thermostats and KNX/IP gateways.
Can CoduWorks auto-create floor heating devices in Control4?
Not as a blind core build. It can prepare reviewable HVAC candidates, but the installer should confirm zones, DPTs, valve outputs, setpoints and feedback before creation.
Why are valve actuators important?
A valve actuator may represent physical manifold outputs, not user-facing rooms. Mapping those outputs incorrectly can control the wrong heating zone.
What should be checked before export?
Check room temperature, setpoint command and feedback, valve state, demand, floor sensor limits, window lockout, actuator channel and room-zone naming.
Scope floor heating before Composer
Import ETS, review heating zones, room controllers and valve actuators, then export .codu only after HVAC scope is clear.