Control4 KNX pricing and device count preview
The preview shows a KNX project being processed into a Control4 structure so counted lights, blinds, thermostats and gateway devices can be reviewed before export.
What counts as a pricing device
The counted device list is focused on the objects CoduWorks prepares for the Composer build: KNX lights, KNX blinds, KNX thermostats and KNX IP gateways. These are the items that move the project into one license tier or another.
A light can be a simple switch or a dimmer. A blind can be open-close or percentage based. A thermostat counts when it is included in scope. A KNX IP gateway counts because it belongs to the build infrastructure and gateway context that must be carried into the reviewed package.
- Switch lights and dimmers that become Control4 lighting devices.
- Blinds and shades that become Control4 blind/shade devices.
- Thermostats included in the reviewed Control4 build scope.
- KNX IP gateways used by the reviewed Control4 build.
What does not move the license tier
Large KNX projects often contain hundreds of keypads, push buttons, binary inputs, contacts, sensors and service objects. Those records may be useful during review, but they do not raise the core license tier by themselves.
This keeps pricing more accessible for projects with many physical controls but a smaller number of generated Control4 lights, blinds, thermostats and gateway devices.
- Keypads and push buttons remain context or programming signals.
- Motion, presence, contact and binary input objects can remain visible for review.
- Room, line, topology and service objects are not counted as generated user devices.
License tiers
The tier is selected from the counted device total after the ETS project has been imported and reviewed. The goal is to avoid charging by every KNX object in the project when many of those objects are context rather than generated Control4 devices.
License 01 is for compact projects up to 75 counted devices. License 02 is for larger homes or professional projects between 75 and 300 counted devices. License 03 is for high-volume projects above 300 counted devices.
Thermostats count when included
KNX thermostats count as devices when they are part of the prepared Control4 build. They still need a dedicated review because setpoints, modes, fan speed, demand state, feedback and vendor-specific DPT choices vary by project.
When a project needs thermostats, the scope should make them explicit so the installer can confirm the control model before Composer receives the build package.
How to estimate the tier before a quote
The fastest estimate is to count the lights, blinds, thermostats and KNX IP gateways that should become part of the Control4 project. Then keep keypads, push buttons and sensors in separate review buckets.
The AI Assistant can help make that count clearer after importing ETS because it shows the generated Control4 structure beside the KNX source context.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Do keypads count for Control4 KNX pricing?
No. Keypads and push buttons can be useful context, but the license tier is based on counted lights, blinds, thermostats and KNX IP gateways.
Do sensors count as devices?
Not for the core license tier. Motion, presence, contacts and binary inputs can remain review context or project-specific programming scope.
Do KNX IP gateways count?
Yes. KNX IP gateways count because they are part of the reviewed gateway and build context for the Control4 project.
Are thermostats included in the main tier?
Yes. Thermostats count when they are included in the prepared Control4 build, and they still need their own review because the control model varies from project to project.
Estimate the license tier from your ETS project
Import ETS, review counted lights, blinds, thermostats and KNX IP gateways, then prepare the .codu package with a clear project scope.