Back to Solutions

Public area scenes

Lobby, corridor and back-of-house scene templates for hospitality projects.

  • 4 zonesTypical public areas
    lobby · corridor · meeting · back-of-house
  • 24hDaily schedule
    base + occupancy overlay
  • Same SKUsHardware reuse
    same modules as guestrooms
  • LocalRCU execution
    schedule survives offline

* Tables below are engineering convention examples; holiday, banquet and DST adjustments go into contract scene-table version — confirm per property measurement.

Public-area daily schedule execution

Public-area daily schedule

Cite directly in tender docs — lighting, HVAC and scene outputs by time slot;base schedule + PIR or overlayis public-area engineering convention.

TimeLobbyCorridor / stairsMeeting roomBack-of-house
00:00–06:00Standby low 30%PIR OFF · safety base 10%All off · pre-cool OFFPIR + base light
06:00–08:00Welcome 80%· FCU presetPIR fill 50%Pre-set 1h before booking (optional)Full base on
08:00–18:00Open 100%· daylight compensationPIR + 5 min delayPer booking · projection scenePIR 70%
18:00–22:00Ambient 60%· accent washPIR + 3 min delayPer session · discuss/projectPIR 50%
22:00–24:00Standby 40%PIR OFF · base 15%All off · vent delayBase + PIR

Four-zone engineering notes

BOM differences by zone — same module SKUs as guestrooms, different circuits and schedules.

Reception lobby

Multi-circuit lighting + wash/chandelier groups;FCU modulewelcome preset; daylight compensation.

Corridor / stairs

PIR+ timed base; aligned withguestroom energycorridor policy; may use separate enclosure.

Back-of-house / linen

Long base + PIR; same bus as public RCU or sub-enclosure; spare parts unified with guestrooms.

Restaurant / all-day dining

Meal-period scenes (breakfast/lunch/dinner); dimming + schedule — seehospitality venues.

Gym / SPA

Open-hours schedule + PIR floor; optional humidity/temp sensors on RCU DI.

Public vs guestroom · control differences

ItemPublicGuestroom
Primary triggerSchedule + PIR fillCard power+ scene keys
Typical modulesRelay/dim + PIRCard power + panel + FCU
ExecutionRCU local scheduleRCU scene table
Platform dependencyBooking/event table (optional)PMS room state (optional)
Offline behaviorKeep schedule + PIRKeep scenes + card-power logic

Office · guestroom hardware reuse

Public-area hardware topology

Hardware layer · same modules

Public and guestrooms may use separate enclosures; RS485 bus may interconnect — fewer spare SKUs and simpler maintenance.

All products →
Optional booking linkage

Platform layer · booking linkage (optional)

Meeting booking, banquet events, group schedule push by integrator BMS/meeting system — PurePoint Smart providesprotocol mappingand DI/Modbus docs.

  • Not a PurePoint Smart SaaS core product
  • RCU runs local day schedule when offline
  • Event days allow manual panel override
Developer API →

Hardware topology reference

Public schedule topology
Schedule + sensors → RCU scene engine → public relay circuits; booking/event via integrator platform (optional). Tender docs may cite this diagram +commercial office reference.

Acceptance checklist

Schedule switch

Simulate 06:00 / 22:00 boundaries; measure lobby and corridor levels.

PIR overlay

Corridor lights on when occupied, off after delay; no conflict with base schedule.

Meeting scenes

Project/discuss/all-off keys; curtain and lighting linked.

Offline keep-alive

Disconnect host; RCU still runs local day schedule.

Recommended models