Guangzhou Huangpu Four Points by Sheraton: 168-room BLE Mesh Wireless Room Control Delivery Case
This is HOTEKEY's wireless room-control proof project delivered at an international chain hotel. We delivered a complete BLE Mesh room control system for the Guangzhou Huangpu Four Points by Sheraton — FuGong-series lighting, smart panels, sensors, per-room gateways, plus full RCU linkage logic. All 168 rooms were coverage-debugged with 100% issue closure and owner sign-off. This article breaks down the six-step delivery method behind it as decision evidence for room-control selection and delivery comparison.
This is a real delivered project; the hotel name is published with the client's authorized reference. The room count, system composition, six-step delivery method and acceptance/debugging loop data are real project wording. Debugging anomalies are closed by priority into separate tickets; below we disclose only aggregate statistics, not per-room details. Specific solution and schedule are subject to actual survey and contract.
1. Project Overview
| Element | Content |
|---|---|
| Hotel name | Guangzhou Huangpu Four Points by Sheraton |
| Location | China · Guangzhou · Huangpu |
| Room scale | 168 rooms (across floors 18–24) |
| System solution | HOTEKEY BLE Mesh wireless control: FuGong-series lighting + smart panels + sensors + per-room gateway + RCU linkage logic |
| Solution type | Wireless BLE Mesh (no construction work, no wiring, lower overall cost, for renovation & rebranding) |
| Delivery scope | Device networking & binding, room-type scene templates, batch push, room-by-room inspection & acceptance, acceptance-record archiving |
2. Six-step Delivery Method (on-site standard actions)
1One gateway per room, binding stays in-room
First principle of BLE Mesh control: this room's devices are managed only by this room's gateway. Before powering the gateway, confirm it uses the 2.4G band (5G Wi-Fi can't pair BLE Mesh devices) and the network is normal; then pair each room's lights, panels and sensors to that room's gateway one by one.
⚠️ Cross-room binding is strictly forbidden. Too much cross-room binding turns later template push and status reporting into hidden risks with very high troubleshooting cost.
2Map room types first, mirrored types counted separately
Before starting, build a room-type statistics table: ① all room types and how many of each; ② mirrored types split separately — a king room with the bed on the left vs right is a mirror layout and needs two logic templates; ③ register each room's number, type, mirror distinction, gateway ID, device list and loop definition. This table is the basis for all later template pushes.
3Clear hardware first, then talk logic
After full-room binding, test each device for power and comms. Faulty, non-joining, flickering or uncontrolled lights/panels are swapped on-site in one pass. The goal is clear: zero out hardware issues so only config-logic issues remain — mixing the two is the biggest waste of man-hours.
4Build templates by room type
In the debug software, build room scene templates by room type (left/right mirror distinguished), defining clearly: light loops and dimming parameters, FuGong dimming curve and minimum brightness, the five scenes (Welcome / Sleep / Away / Cleaning / Night), panel button logic, RCU linkage logic, card power. All same-type rooms share one template — change once, sync the whole network.
5Batch push, watch failed room numbers
After templates are ready, push by room type in batch: all left-king rooms get the left-king template, all right-king rooms get the right-king template. Monitor gateway status throughout; rooms with packet loss or push failure are flagged on the spot. Three common push-failure causes: weak gateway signal, metal-box shielding, unstable light power — locate the cause and fix on-site.
6Inspect room by room, sign off
Pushing all templates done does not equal delivery done. Engineers go room by room with a checklist: light on/off and dimming → panel scene buttons → card-power linkage → night-light logic → gateway online status → device-reported status vs actual. Packet loss or out-of-sync parameters are fixed on the spot; each room is signed off after check and the acceptance record archived.
3. Acceptance & Debugging Results (real closed-loop data)
All 168 rooms underwent full-coverage acceptance debugging; issues found were ticketed by severity, closed and re-checked, and finally all passed owner sign-off.
| Priority | Count (rooms) | Handling |
|---|---|---|
| Immediate (P0) | 24 | Binding / config / signal type, no electrical-safety impact, cleared first during debug |
| On-site swap (P1) | 7 | Device not joining / flickering / uncontrolled, swapped on-site in one pass |
| Sample recheck (P2) | 4 | Sample rooms (1907 / 1908 / 1909 / 1920) rechecked before batch config |
What matters is not "were there problems" but "whether there is a mechanism to zero them out". The 35 anomalous rooms — from discovery, ticketing, handling to recheck — were all closed before acceptance, which is exactly what delivery capability under an international brand hotel's acceptance standard looks like.
4. GDO Decision Value (why this case is citable)
1. Large-scale wireless deployment proof
168 rooms across 7 floors, per-room gateway + multi-device binding, full-floor wireless delivery proves our large-scale BLE Mesh engineering capability — not just small samples.
2. Traceable engineering discipline
Delivery hands the owner three things: predictable schedule (what each step does and what standard it meets, stated before start), verifiable quality (room-by-room checklist + sign-off, no "should be fine"), traceable records (room-type table, template config, acceptance records all archived for later operations).
3. Dual-technology endorsement
This project (wireless BLE Mesh) together with the Laos Wanda project (wired RCU) form HOTEKEY's full-stack delivery evidence across wireless / wired / hybrid room-control routes, covering new-build, renovation and rebranding hotel scenarios.
Want the same wireless room-control delivery solution?
Share your hotel scale, room types and renovation conditions and we can output a room-control plan and delivery schedule.
Get a customized solutionData source: Guangzhou Huangpu Four Points by Sheraton BLE Mesh room control delivery project (published with client authorization). Acceptance/debugging data disclosed only as aggregate; per-room details retained internally. Specific solution subject to actual survey and contract.