Back to home

Solutions

Guestroom control technology, capability modules and engineering references for hotel projects.

  • 4 routesDeployment routes
    Wireless · wired · RS485· modular
  • 6 pointsStandard room BOM
    Same hardware categories per route
  • 36+RCU host models
    Series selection by route
  • 4 typesCore engineering tables
    Schedule · wiring · address · slots

* Routes and tables are engineering convention summaries; contracts should attach versioned drawing sets — no ad-hoc address or slot changes on site.

Four routes · selection summary

Select the route by property type and construction window first, then open the matching tech page for tables and topology. The master solutionStandard room guest controlpage "Four deployment routes" tab mirrors this directory — focused on decision comparison.

Wireless RCU guestroom control

Mesh / ZigBee / LoRa gateway + wireless panels and card-power modules — minimal LV chase work; suited to retrofit, B&B and partial renovation.

Retrofit · short schedule
  • Load:128–256 channels/gateway (by protocol)
  • Deliverables:Retrofit schedule compare · network topology
Open wireless solution →

Wired smart guestroom control

LV enclosure RCU + star panel wiring; card power, door sign and multi-circuit modules centralized in enclosure — preferred for new-build and upscale hotels.

New build · star topology
  • Response:Local scenes <100ms
  • Deliverables:Per-room star wiring table · terminal cross-reference
Open wired solution →

RS485 bus guest control

Modules and panels share bus addresses; chain standard-room template signed once and copied — open Modbus RTU for third-party host systems.

Chain · standard room
  • Convention:9600 bps · per-room 01–0F
  • Deliverables:Bus address allocation table · fault isolation notes
Open RS485 solution →

Modular enclosure guest control

Relay / dimming / HVAC function modules mixed in slots; multi-zone suites with stackable circuits; hot-swap spares bound to slot codes.

Upscale · suite expansion
  • Expansion:4–8 slots · 8–32 relay channels
  • Deliverables:Enclosure slot configuration table · terminal cross-reference
Open modular solution →

Four routes · comparison matrix

The "Tech routes" tender section may cite this table whole; models per signed drawing set and BOM revision — wire gauge and addresses per drawings.

DimensionWireless RCUWired guest controlRS485 busModular enclosure
Typical propertyRetrofit · B&BNew hotel · upscaleChain standard propertyLuxury · connecting suites
Low-voltage traitsMinimal chase · gateway zoningStar · per-room isolatedBus daisy-chain / star tapCentral enclosure · slot expansion
Construction window3–7 days/room (typical)With civil LV rough-inCopy after mock-up sign-offSchedule by circuit design
Core engineering tablesRetrofit schedule compareStar wiring tableAddress allocation tableSlot configuration table
Protocol / integrationMesh · ZigBee · LoRaProprietary / Modbus optionalModbus RTU openSame-series register table
Detail linkWireless solutionWired solutionRS485 solutionModular solution

Per route · engineering deliverables

Tech pages focus on wiring tables, address tables, slot tables and otherprintable engineering deliverables; capability linkage logic seeGuestroom capabilities (B).

Wireless RCU page

  • New build / retrofit / partial renovation schedule compare
  • Gateway load and wall-material zoning notes
  • Panel power form (battery / live-neutral) selection
  • Per-room network topology and BOM entry

Wired guest control page

  • Per-room star LV topology and wire-gauge convention
  • RCU terminals · panels · card-power cross-reference
  • Six-point BOM and circuit expansion notes
  • Local scene persistence and response metrics

RS485 bus page

  • Per-room 01–0F address allocation template
  • A/B/GND/shield four-wire installation convention
  • Baud rate and register table citation method
  • Multi-property chain copy and fault isolation

Modular enclosure page

  • CPU + function module slot configuration table
  • Relay / dimming / HVAC slot planning
  • Hot-swap spare codes bound to slots
  • Economy → upscale same-series appearance
Route 1

Wireless RCU guestroom control

Key attachment: retrofit schedule compare table

Route 2

Wired smart guestroom control

Key attachment: per-room star wiring table

Route 3

RS485 bus guest control

Key attachment: bus address allocation table

Route 4

Modular enclosure guest control

Key attachment: enclosure slot configuration table

By property type · recommended route

PurePoint Smart project conventions below; hybrid routes (e.g. wired public areas + wireless guestrooms) can be aligned with engineers during quoting.

Retrofit · operating property renovation

Prefer wireless RCU to limit chase work and downtime; card power and door sign still per power-code install — relay modules in enclosure.

View wireless solution & schedule →

Chain standard property · multi-property copy

RS485 address template signed once; register table issued with BOM revision — use chain BOM topic for tender drafting.

View RS485 address table →

Luxury suite · multi-circuit expansion

Modular enclosure mixed slots; relay / dimming / HVAC planned by zone — spare slot codes in O&M manual.

View enclosure slot config →

Mapping to product center · capability solutions

All four routes share thesix-point per-room BOM(door sensor/sign · card power · thermostat · bedside scenes · desk · RCU) — same hardware categories, models switch by route. Card power logic →Card power· Panel scenes →Scene-linked lighting· Protocol integration →Third-party protocols+API documentation. Full model list:RCU catalog,smart switches, andproduct selection catalog.

Tender drafting · suggested order

① On theStandard room guest controlmaster solution, set property type and six-point BOM structure → ② In this directory, pick a deployment route and citeengineering tables and topology→ ③ OnGuestroom capability solutions, add linkage logic and register notes → ④ OnEngineering topics, cite energy, chain BOM and other tender topics. Need per-room wiring, terminal table or route comparison? Share new-build/retrofit and schedule — we help with selection and document alignment.

Need per-room wiring, terminal, address table or route comparison? Share property type, new-build/retrofit and schedule — we help with selection and document alignment.

  • 9 itemsGuestroom capabilities
    Check-in · experience · ops · integration
  • 6 pointsPer-room BOM mapping
    Aligned with master solution structure
  • 11Product categories
    Locks · card power · panels etc.
  • 3 layersPlatform integration
    Modbus · DI/DO · REST

* Capability pages focus on hardware linkage and engineering tables; savings ratios and access timing are conventional ranges — tenders should state "calibrate per mock-up room."

Check-in chain · three-phase capabilities

When drafting tenders, integrators can chain the capability pages below as pre-stay → in-stay → operations; hardware nodes and software scope are footnoted on each page.

All 9 capabilities · full index

Each page includes decision trees, linkage tables or topology sketches and recommended models — cite directly in tender sections.

Per-room BOM · capability mapping

Standard-room six-point hardware list maps 1:1 to column-B capability pages; circuit count and key positions per contract BOM revision.

BOM #Per-room pointFunction highlightsCapability pageProduct catalog
1Door sensor · doorbellDND/MUR · door sensor card-power linkageDoor sign DND/MURHotel door signs
2Entry triple panelCard power · clean/DND · corridor lightCard / keyless powerCard power
3ThermostatFCU/VRF · Welcome/vacancy presetsHVAC comfort controlHVAC modules
4Left · right bedsideScene keys · curtain open/close · read/sleepScene lighting·Motorized shadingSmart switches
5Desk triple panelDesk light · outlet · USBScene lightingInfo panels
6RCU hostLocal scenes · open protocol · offline persistenceProtocol integrationRCU catalog
+Lock · sensors · public areasCheck-in access · vacant cut-off · back-of-house schedulesDoor lock·Energy sensors·Public areasDoor lock·Sensors

By group · engineering deliverables

Capability pages focus onlinkage logic and cross-reference tables; wiring and address tables seeGuest control tech (A).

Check-in · access (3 items)

  • Lock: PMS room-state event mapping · four lock-network compare
  • Card power: 4-way decision tree · delayed disconnect parameter table
  • Door sign: DND/MUR dry contact · exterior LED sequence

In-stay · scenes (3 items)

  • Lighting: key legend · illuminance/scene cross-reference
  • Curtains: dual-track linkage · Welcome/vacancy scenes
  • HVAC: FCU/VRF module · open-window protection logic

Operations · public areas (2 items)

  • Energy: vacant cut-off 5-step sequence · sensor I/O table
  • Public areas: 4-zone split · 24h schedule template

Integration (1 item)

  • Protocol: Modbus registers · DI/DO terminal definitions
  • REST / Webhook mapping examples
  • Hardware boundary notes (not SaaS deliverable scope)
Check-in · access

Access and card power

Check-in chain hardware nodes

Guest experience

Scenes and comfort

In-stay scene linkage

Operations · public areas

Energy and back-of-house

Vacant cut-off · schedules

Integration

Protocol and platform

Integrator handles software integration; PurePoint Smart provides hardware and event sources

By project type · capability bundles

Conventional bundles below — align circuit count and key positions with engineers during quoting.

Chain standard property · copy-first

Card power + door sign + scene lighting + RS485 protocol mapping signed once — reuse register table and key legend across properties.

Start with card-power logic →

Upscale / full-service · experience-first

Bedside scene keys + dual-track curtains + HVAC presets + touchscreen entry; lock and PMS contactless check-in linkage.

Start with scene lighting →

Retrofit · energy-first

Card-power door linkage + vacant cut-off sequence + wireless module retrofit — energy loop with minimal chase work.

Start with energy sensors →

Integrator platform · mapping-first

Set Modbus/DI/DO mapping table and RCU model first, then expand capability-page linkage into the host system.

Start with protocol integration →

Mapping to product center · tech routes

Door lock →Hotel door locks· Card power →Card power· Curtains →Smart curtains· Environment →HVAC modules/Thermostat panels· Sensors →Smart sensors· Door sign →Hotel door signs· Protocol →RCU gateway+API documentation. Network routes seeGuest control tech (A); full models seeproduct selection catalog.

Tender drafting · suggested order

① On theStandard room master solutionset six-point BOM structure → ② OnTech routes, set network and engineering tables → ③ In this directory, expandlinkage logic and cross-reference tables→ ④ OnEngineering topicscite energy, contactless, chain BOM and other tender topics. Need per-room wiring, linkage table or BOM? Share circuit count and hotel type — we help bundle capability modules and align stocking codes.

Need per-room wiring, linkage table or BOM? Share circuit count and hotel type — we help bundle capability modules and align stocking codes.

  • 7 itemsEngineering topics
    Tender summary · signature blocks
  • 4 typesTender chapters
    Energy · check-in · experience · LV
  • SVGArchitecture / case diagrams
    Citable per page
  • HardwareDelivery boundary footnotes
    Not an ops software catalog

* Topic matrices and timelines are engineering summaries; savings ratios and alarm SLA should state "calibrate per mock-up/property measurement."

Tender drafting · three-phase citation path

Topic pages paste into technical tenders; return to B/C/A main solutions for wiring and model detail.

All 7 topics · full index

Each page includes signature-block tables and architecture/case SVG; hardware boundaries in footnotes.

Topics · tender chapters · main solution mapping

Left: common owner tender chapters; right: B/C main solution entry points for detail.

TopicCommon tender chapterCore citable deliverablesDetail main solution
Energy savingGreen energy · energy managementVacant cut-off decision tree · strategy matrixGuestroom energy
Contactless check-inSmart check-in · contactless service6-step access timeline · three-node coordinationSmart door lock
Panel scenesGuest experience · smart controlKey legend · illuminance cross-reference tableScene lighting
After-sales diagnosticsOps response · fault diagnosisAlarm tier matrix · terminal definitionsProtocol integration
Chain BOMStandardization · multi-property copyE1–X1 five tiers · versioned checklistChain rollout
Security sensorsSecurity monitoring · sensor linkageAlarm responsibility swimlane · sensor matrixEnergy and sensors
Weak-current topologyLV systems · multi-network convergence5-layer responsibility stack · interface splitStandard room topology

By group · signature block notes

“Signature blocks” are core charts on each topic page that can be cited whole in tenders; non–PurePoint Smart deliverables are footnoted on each page.

High-frequency tender (3 items)

  • Energy: vacant × card-power form decision tree
  • Contactless: book→check-in→check-out 6-step timeline
  • Chain: E1–X1 tiers and BOM v2.x version rules

Experience · ops (3 items)

  • Panel scenes: key legend and illuminance curve cross-ref
  • After-sales: alarm tier × response responsibility matrix
  • Security sensors: DI I/O × audiovisual push swimlane

LV · general contractor (1 item)

  • LV topology: RCU/network/PMS/fire 5-layer responsibilities
  • Guest control vs IPTV/phone/CCTV interface split
  • GC coordination notes (integrator scope)

Shared notes

  • Architecture/case SVG on each page citable
  • Hardware node descriptions aligned to BOM version
  • PMS/NOC/energy dashboards not primary manufacturer deliverable
Common in tenders

Energy · check-in · chain

High-frequency owner tender chapters

Experience · ops

Scenes · after-sales · security

In-stay experience and ops response

Low voltage

Weak-current topology

Multi-network responsibility split

Further reading

Main solution entry

After topics, expand main solutions here

By bid type · topic bundles

Owner tender focus varies — pick topic bundles below for the matching technical section.

Energy / green hotel bid section

Cite energy decision tree and strategy matrix first; use card-power and sensor pages for hardware cut-off nodes and acceptance criteria.

Open energy-saving topic →

Chain standardization bid section

E1–X1 five-tier BOM + chain rollout — version in contract; new properties accept points and scenes per checklist.

Open chain BOM topic →

Smart check-in / experience bid section

Contactless timeline + panel scene cross-ref; PMS by integrator, PurePoint Smart delivers entry and bedside hardware.

Open contactless check-in topic →

LV GC / multi-network bid section

LV stack defines RCU, network, PMS, fire boundaries — then link to standard-room topology and wired wiring table.

Open weak-current topology topic →

Topics vs B/C columns · capability mapping

Energy saving →Guestroom energy· Contactless →Smart door lock· Panel scenes →Scene lighting· After-sales →Protocol integration· Chain BOM →Chain rollout· Security →Sensor nodes· LV topology →Standard room topology. Registers and API seedeveloper documentation.

Usage · hardware delivery boundary

Topic matrices, timelines and SVG are fortender citation; PMS access, NOC dashboards, energy SaaS and fire linkage are implemented by integrators or property IT — PurePoint Smart deliversRCU, panels, modules, sensors and protocol documentation. Retain boundary notes in footnotes when citing; bind BOM version and register table version in contract attachments.

Need custom matrices or register tables? Share property type and topic section — we align hardware node descriptions and document packs.