Winning a hotel project takes a strong proposal. Keeping it takes disciplined delivery.
At the Four Points by Sheraton project in Guangzhou (Huangpu), HOTEKEY delivered a complete BLE Mesh guest room control system: lighting fixtures, smart panels, sensors, one gateway per room, and full RCU linkage — welcome scenes, keycard power, and night-light logic included.
Wireless guest room control is attractive for obvious reasons: no rewiring, no civil work, lower total cost. But wireless raises the bar for commissioning discipline. Signal planning, device binding, templates, batch provisioning — every step has to be locked down, because the system you deliver is only as good as the room you last checked.
Here is the six-step commissioning playbook we ran on site. For how BLE Mesh compares with RS-485, PLC and KNX on paper, see the hotel room control technology guide.
Step 1: One Room, One Gateway — Binding Never Crosses Rooms
Before the gateway goes online, two checks come first: the network must be on the 2.4 GHz band (5 GHz Wi-Fi cannot provision BLE Mesh devices), and connectivity must be stable.
Then every device in the room — luminaires, panels, sensors — is provisioned and bound to that room's own gateway. One room, one gateway, no exceptions.
Cross-room binding is strictly prohibited. This is not procedure for its own sake: stray bindings are the single biggest source of downstream provisioning failures and status-reporting errors, and they are miserable to trace after handover.
Step 2: Map Every Room Type First — Mirror Layouts Get Separate Templates
Before any configuration work starts, we build a room-type matrix:
- All room types, with room counts for each;
- Mirror layouts split out — a king room with the bed on the left and one with the bed on the right are the same room type, but their device layouts mirror each other, so each gets its own logic template;
- Room-by-room records: room number, room type, mirror flag, gateway ID, device list, and circuit definitions.
This spreadsheet is the foundation for every template pushed later. Get it wrong, and every downstream step inherits the error.
Step 3: Clear Hardware Faults Before Touching Logic
Once all devices in a room are bound, each one is power-tested and communication-tested. Faulty fixtures, panels that fail to join the network, flickering lights, unresponsive loads — all replaced on the spot, in one pass.
The goal is simple: zero hardware issues before configuration begins. Mixing hardware faults with configuration errors in the same debugging session is the most expensive way to spend engineering hours.
Step 4: Build a Template for Every Room Type
In the commissioning software, a scene template is built for each room type — mirrored types get separate templates. One template defines:
- Lighting circuits and dimming parameters, including each fixture's dimming curve, minimum brightness level, and power-on default state;
- Five core scenes: Welcome, Sleep, Check-out, Cleaning, and Night;
- Panel button logic, RCU linkage, and keycard power behavior.
Every room of the same type shares one template. The payoff is direct: change a parameter once, and every room of that type stays in sync — no room-by-room rework.
Step 5: Batch-Provision — and Watch Every Failed Room
Templates are pushed to the field in batches by room type: all left-king rooms receive the left-king template, all right-king rooms the right-king one. Gateway status is monitored throughout the push, and any room showing packet loss or failed provisioning is flagged immediately.
The usual suspects behind failed pushes: weak gateway signal, metal enclosure shielding, or unstable fixture power. Each one gets located and fixed on site.
Step 6: Room-by-Room Inspection, Signed Acceptance
Provisioning complete does not mean delivery complete.
Engineers walk every room with a checklist: lighting on/off and dimming, scene buttons, keycard power linkage, night-light logic, gateway online status — and whether the states devices report actually match what the room is doing. Anything out of sync is fixed on the spot.
Every room is then signed off, and the acceptance record goes into the project archive.
What the Owner Actually Gets
- A schedule you can predict. Every step has a defined scope and pass criteria, agreed before work starts.
- Quality you can verify. Signed, room-by-room inspection records — no "it should be fine".
- Documentation you can trace. Room-type matrices, template configurations, and acceptance records are all archived, so future maintenance starts from facts, not memory.
That last point matters more than it sounds. International brand standards are exacting, and an owner who can show signed room-level acceptance records is an owner who closes projects without disputes.
Related: Four Points by Sheraton Huangpu project · protocol trade-offs: RS-485 vs BLE Mesh vs PLC vs KNX guide · full index: Knowledge Hub.