Project profile: Customer type: hotel automation engineering company / system integrator. Market: South Asia (generalized to protect commercial confidentiality). Project type: 420-room hotel KNX guest-room automation. Project stage: mock-up room engineering and validation before rollout. Solution at a glance: one integrated KNX RCU per guestroom, three presence sensors covering the entrance, bathroom and bed area, conventional hotel panels connected through potential-free dry contacts, and third-party DND/MUR integration.
Project Overview
An engineering company asked WinSmartHome to prepare a cost-conscious KNX guest-room control proposal for a hotel with approximately 420 rooms. The first objective is to build and validate one mock-up room. After the room functions, installation details and guest experience are approved, the design can be standardized for the remaining guestrooms.
The proposed architecture uses one integrated KNX room control actuator as the room-level control core. It connects lighting, dimming, curtains, fan-coil control and other room functions, while ordinary hotel switch panels and third-party DND/MUR devices can be integrated through potential-free dry-contact inputs.
This approach allows the project to keep the selected conventional hotel panel design while bringing the room functions into the KNX system. It also reduces the number of separate DIN-rail modules required in each room.
To protect commercial confidentiality, the customer name, exact project location and identifying RFQ details are not disclosed. The room count has also been generalized.
Initial Requirements and Project Constraints
The client initially requested a cost-conscious KNX hotel-room solution that could be proven in one furnished mock-up room before any multi-room order. KNX was the preferred protocol, while the selected conventional hotel panels, third-party DND/MUR devices, lighting and dimming circuits, curtains, fan-coil control and three-zone presence detection all had to work through one repeatable room architecture.
The main constraints were commercial as well as technical: retain the chosen panel appearance, use potential-free dry contacts for ordinary switches and DND/MUR interfaces, keep the room controller compact and economical, and verify every function before rollout. The final quotation and production BOM still depend on confirmed lighting loads, the selected 0–10 V or DALI method, fan-coil type, curtain motors, panel point schedule, DND/MUR signal logic, sensor coverage, wiring drawings and ETS parameters.
Confirmed Room Requirements
The proposed mock-up room includes:
- KNX as the preferred room-control protocol;
- one integrated KNX RCU per guestroom;
- conventional hotel bedside and entrance panels connected to the RCU through dry contacts;
- third-party Do Not Disturb (DND) and Make Up Room (MUR) devices connected through dry-contact interfaces;
- switched lighting circuits and 0–10 V dimming control;
- curtain control;
- fan-coil-unit control;
- three KNX true-presence sensors;
- presence-based master lighting and dimming scenes;
- one mock-up room before the final multi-room order;
- a competitively priced, repeatable room design suitable for a large hotel rollout.
How the Product Combination Was Selected
The product combination was selected by matching each room function to the project’s cost, installation and repeatability requirements—not simply by choosing the largest number of KNX devices.
- Integrated KNX RCU: One room controller was selected as the control core because its relay, dimming, curtain, fan-coil, dry-contact, interface and power-supply functions can replace several separate DIN-rail modules. This reduces device count, inter-module wiring and room-panel space, while making an approved mock-up easier to reproduce across approximately 420 rooms.
- Conventional hotel panels with dry contacts: The customer wanted to retain the selected panel appearance. Potential-free dry-contact inputs allow those ordinary hotel switches to trigger KNX scenes and room functions without requiring native KNX keypads at every control point.
- Third-party DND/MUR devices: Dry-contact input and output channels were chosen so compatible door-side and in-room DND/MUR devices can be integrated without locking the project to a single panel supplier. The mock-up must confirm contact logic, signal direction and priority rules.
- Three true-presence sensors: Separate sensors for the entrance, bathroom and bed area were selected because one conventional motion sensor cannot reliably cover all zones or detect a resting guest. The three sensors provide better occupancy evidence for comfort and energy-saving logic.
- 0–10 V or DALI dimming: The RCU supports either approach, but the final choice must follow the approved luminaire drivers, grouping requirements, scene strategy, wiring and maintenance preference. The production BOM should not freeze this item until the mock-up room has been tested.
The reference model KN/RC1805A is therefore a functional starting point rather than an automatic final selection. Before quotation and rollout, the project team must verify channel capacity, connected loads, fan-coil type, curtain motors, panel point schedule, ETS database, firmware, certification requirements and the approved wiring diagram.
Why Use an Integrated KNX RCU?
Traditional hotel-room designs may require separate power supplies, relay actuators, dimming modules, curtain actuators, binary inputs and gateway devices. An integrated RCU combines the principal room-control functions in a single DIN-rail device.
For this reference design, the proposed KNX room control actuator, model KN/RC1805A, combines:
- four 10 A relay channels and fourteen 5 A relay channels;
- fan-coil control outputs;
- four curtain-control channels;
- twenty-one potential-free dry-contact inputs;
- twenty-one passive outputs, with output type and 22–24 V electrical characteristics to be confirmed against the approved wiring diagram;
- four 0–10 V control channels or one DALI channel, selected according to the project configuration;
- KNX, RS485, infrared and Ethernet interfaces;
- a built-in standard KNX IP gateway;
- a built-in 29 V DC / 320 mA KNX bus power supply, 16 V / 250 mA DALI power supply, and 24 V / 2 A auxiliary power supply;
- optional integration functions such as smart-speaker or third-party system communication, subject to project validation.
The combined architecture can simplify the room distribution board, reduce inter-module wiring and make it easier to reproduce the approved mock-up-room design across hundreds of rooms.
Technical note: Final channel allocation, loads, interfaces, ETS database, applicable certification status and firmware must be checked against the current product documentation before quotation and project approval.
Integrating Ordinary Hotel Panels Through Dry Contacts
The client selected conventional hotel switch panels rather than native KNX keypads. These panels can still participate in the KNX room logic by connecting their potential-free contacts to the RCU‘s digital inputs.
When a guest presses a button, the panel closes or opens a dry-contact circuit. The RCU reads that input and executes the programmed KNX function, such as:
- Master ON/OFF;
- reading or working scene;
- night scene;
- lighting circuit switching;
- dimming scene selection;
- curtain or sheer control;
- other room functions defined in ETS.
This gives the interior designer greater freedom in panel appearance while the RCU provides the centralized KNX logic behind the panel. Before production, every button contact type, common terminal and input mapping must be checked in the mock-up room.
Connecting Third-Party DND and MUR Devices
The same dry-contact architecture allows compatible third-party DND and MUR devices to be included even when they are not supplied by the RCU manufacturer.
A typical design can include:
- an in-room DND/MUR command from the selected hotel panel;
- a corridor or door-side DND/MUR indicator;
- dry-contact inputs and outputs for status exchange;
- optional integration with a hotel room-management system, access-control system or property-management workflow.
The mock-up must confirm the exact signal direction, contact logic, priority rules and status synchronization. DND and MUR should not be treated as simple decorative indicators; the approved logic must define what happens when housekeeping, guest commands and the wider hotel system send different states.
Three Presence Sensors and Their Locations
Each guestroom uses three KNX true-presence sensors in different functional zones:
1. Bathroom sensor
The bathroom sensor detects occupancy for bathroom lighting, delayed switch-off and any required night or energy-saving logic. Its position should avoid blind spots caused by doors, partitions or shower enclosures.
2. Entrance sensor
The entrance sensor detects a guest entering or leaving the main room area. It can participate in welcome-scene, pathway-lighting and occupancy-state logic, but it should not be used alone to decide that the entire room is vacant.
3. Bed-area sensor
The sensor above or close to the bed area helps maintain reliable presence detection when the guest is resting or moving very little. This is important because a basic motion sensor may incorrectly turn off lights or change the HVAC state when a guest remains in the room without making large movements.
The three sensors should be combined through ETS logic rather than treated as three independent light switches. Detection coverage, timeout values, scene priorities and false-trigger conditions must be tested in the furnished mock-up room.
Example Room-Level BOM
| Function | Proposed item | Reference configuration | Quantity per room |
|---|---|---|---|
| Integrated room control | KNX Room Control Actuator | KN/RC1805A; integrated relay, dimming, dry-contact input/output, curtain, FCU and interface functions | 1 |
| Presence detection | KNX True Presence Sensor | Model KN/SMR01.1 or approved equivalent | 3 |
| Guest controls | Conventional hotel switch panels | Potential-free contacts connected to RCU digital inputs | According to room panel schedule |
| DND/MUR | Third-party DND/MUR panel and indicator | Dry-contact interface; final logic confirmed during mock-up | According to door and room schedule |
The final BOM must also specify lighting loads, dimming drivers, curtain motors, fan-coil type, power distribution, protective devices, panel quantities, cables, terminal assignments and any gateway or hotel-system interfaces.
Recommended Control Logic
The RCU and three presence sensors can support a practical sequence such as:
- The entrance sensor detects arrival and activates the approved welcome or pathway-lighting scene.
- Room and bed-area presence detection maintains occupied mode even when the guest is sitting or sleeping.
- The bathroom sensor controls bathroom lighting independently while contributing to the overall occupied state.
- The guest uses the conventional dry-contact panel for Master, Reading, Night, Relay, Curtain and Sheer commands.
- DND/MUR commands and indicators exchange status through dedicated dry-contact channels.
- When all presence zones indicate vacancy for the approved delay period, the RCU changes lighting and HVAC to the programmed energy-saving state.
- Manual guest commands, DND/MUR status and safety-related functions receive the priorities defined in the ETS control logic.
The exact sequence should be approved by the hotel operator because guest comfort, housekeeping procedures and energy-saving policies vary between projects.
Sample and Compatibility Validation Workflow
The mock-up room should follow a documented sample-validation workflow so the final BOM is supported by test evidence rather than assumptions. Each stage should produce a clear record that can be reviewed by the hotel operator, system integrator and supplier.
- Freeze the inputs and test scope. Confirm the room function list, electrical load schedule, panel point schedule, lighting drivers, curtain motors, fan-coil type, DND/MUR interfaces, sensor locations, target market and certification requirements. Output: approved input checklist and marked-up room drawing.
- Prepare the sample kit. Assemble the KNX RCU, three presence sensors, selected conventional hotel panels, third-party DND/MUR devices, representative dimming drivers, curtain motor, fan-coil interface or simulator, power supplies and required cables. Output: sample register with model numbers, quantities, firmware and ETS database versions.
- Complete electrical and wiring checks. Verify supply voltage, relay ratings, 0–10 V or DALI wiring, potential-free dry contacts, common terminals, input/output direction, protective devices and terminal allocation before energizing the room. Output: signed wiring checklist and terminal schedule.
- Commission the KNX devices. Download physical addresses and ETS parameters, then configure group addresses, lighting scenes, curtain logic, fan-coil control, DND/MUR status and occupancy timing. Output: dated ETS project file and parameter record.
- Validate each subsystem. Test switching loads, dimming range and flicker, curtain direction and interlocks, fan speeds and temperature commands, every hotel-panel button, DND/MUR indicators and each presence-sensor zone. Output: function-by-function pass/fail sheet with photos or videos where useful.
- Run cross-system and recovery tests. Check combined scenes, repeated commands, priority conflicts, short guest movements, a resting guest, vacancy delay, power loss and recovery, KNX communication interruption and third-party device synchronization. Output: issue log with cause, correction and retest result.
- Freeze the approved versions. Record the accepted hardware models, firmware, ETS product databases, application versions, parameters, wiring drawings and substitutions. Any later change should trigger a controlled compatibility retest. Output: approved-version register.
- Approve the mock-up and production BOM. The project team signs the final test report and updates the room-level BOM, drawings and quotation to match the approved sample room. Output: signed mock-up acceptance record and released BOM.
WinSmartHome’s validation service can therefore deliver a practical evidence package: input checklist, sample register, wiring schedule, ETS file, functional test report, issue-and-retest log, approved-version register and final BOM. This makes the proposed hotel-room solution easier to review, quote and reproduce at scale.
Mock-Up Room Validation Checklist
Before duplicating the design across approximately 420 rooms, the project team should:
- Freeze the room function list, electrical load schedule and panel layout.
- Map every conventional panel button to a dry-contact input and KNX function.
- Confirm the third-party DND/MUR input/output logic and indicator behaviour.
- Verify relay loads, 0–10 V or DALI selection, curtain motors and fan-coil wiring.
- Confirm the positions and detection coverage of the bathroom, entrance and bed-area sensors.
- Program the ETS group addresses, scenes, priorities, delays and occupancy logic.
- Test normal use, rapid repeated commands, power recovery and communication failure.
- Confirm panel labels, finishes, installation depths and terminal access.
- Record the approved RCU firmware, ETS product database and parameter settings.
- Update the BOM and wiring drawings so the quotation, samples and production order all match the approved mock-up.
Why This Is a Mature Solution
The integrated KNX RCU architecture is not an untested concept. This type of solution has already been applied in multiple domestic hotel and building projects. Its maturity comes from combining established hotel-room functions—relay switching, dimming, curtains, fan-coil control, dry-contact panels and room-status interfaces—inside a repeatable control architecture.
However, a mature architecture does not remove the need for project-specific validation. Every hotel has different loads, panel designs, room layouts, DND/MUR devices, HVAC equipment and operating procedures. The mock-up room is therefore the point where a proven platform is adapted and approved for this particular project.
Benefits for Hotel Owners and Integrators
- Retains the chosen conventional hotel-panel appearance.
- Brings ordinary dry-contact controls into a KNX automation architecture.
- Supports third-party DND/MUR devices without forcing one panel supplier.
- Consolidates multiple room-control functions into one RCU.
- Reduces module count and can simplify room-board wiring.
- Uses three-zone presence detection for more reliable occupancy logic.
- Creates one repeatable, tested room standard before a large rollout.
- Allows function-based sourcing while keeping one coordinated BOM and validation process.
Planning a KNX Hotel Mock-Up Room?
Send us your room schedule, electrical drawings, panel design, DND/MUR interface requirements, HVAC type and target budget. WinSmartHome can help prepare the RCU channel schedule, KNX product shortlist, room-level BOM and mock-up validation plan.