What are the five layers?

L0 field devices and perception, L1 control and execution, L2 edge and gateway, L3 cloud and platform, L4 applications. Each layer has its own failure modes and commissioning checks.

Can PW and SC series devices share one RS-485 bus?

No. Their gateway protocols are not interoperable. On a retrofit, identify the installed series before adding devices, otherwise modules appear offline.

Why keep an OTA path in the application layer?

Because field fixes should not require a site visit. An OTA channel in the architecture lets the platform deliver firmware updates and keep room state synchronised after changes.

Five Layers of a Guest Room Control System

L0 · Field devices and perception

Cardpower

Doorbell

Doordisplay

Doormagnet

Infrared

Lock

Nocard

Panel

Scenepanel

Sensor

Thermostat

Card power, no-card occupancy, door sign, doorbell, door contact, lock, IR blaster, PIR sensor, wall panels and thermostats. A door contact is the base signal for occupancy recovery; a PIR answers a different question — is somebody in the room — so it can drive cardless occupancy. DND must never mask an SOS event.

L1 · Control and execution

Addressing

Audio

Controller

Curtain

Dimming

Hvac

Lighting

Logic

Power

Power220

Relay

Lighting, dimming, relays, curtain motors, HVAC, dry-contact IO, addressing and scene logic. Motor loads need stall-current allowance and an end-limit check; a 0-10 V dimmer controls ballast input only and still needs a relay to isolate mains.

L2 · Edge and gateway

Bridge

Gateway

Local

Mesh

Netparam

Rs485

Upgrade

RS-485 bus, Bluetooth Mesh, gateways, bridges, local logic, network parameters and OTA. Both Zigbee and Bluetooth Mesh use 2.4 GHz, so avoid congested Wi-Fi channels and keep gateways out of metal enclosures and away from power trays. Our PW and SC gateway series do not share a protocol — identify the installed series before a retrofit.

L3 · Cloud and platform

Api

Auth

Cloud

Crm

Data

Downlink

Pms

Scene

PMS, CRM, API, authentication, cloud state, data, downlink and scene services. Test check-in scenes, room-status updates and fault alarms end to end before scaling a room type.

L4 · Applications

Controlscreen

Miniprogram

Mobile

Ota

Report

Roomsync

Thirdapp

Voice

Workorder

Mobile apps, mini programs, control screens, third-party apps, voice, OTA, room sync, work orders and reports. Keep an OTA path available so field fixes do not require a site visit.

Sources and field note

These checks are compiled from HOTEKEY engineering commissioning notes written while specifying, wiring and troubleshooting guest room control hardware. Photographs show our own modules and enclosure layouts. Electrical stress figures on this site are design and verification targets used in hardware development; they are not certification claims. For project-specific values, request the current datasheet from our engineering team.

What are the five layers?: L0 field devices and perception, L1 control and execution, L2 edge and gateway, L3 cloud and platform, L4 applications. Each layer has its own failure modes and commissioning checks.
Why does gateway placement matter for wireless systems?: Zigbee and Bluetooth Mesh both use 2.4 GHz. Avoid congested Wi-Fi channels and keep gateways out of metal enclosures and away from power trays, or the mesh will look unreliable even when devices are healthy.
Can PW and SC series devices share one RS-485 bus?: No. Their gateway protocols are not interoperable. On a retrofit, identify the installed series before adding devices, otherwise modules appear offline.
Why keep an OTA path in the application layer?: Because field fixes should not require a site visit. An OTA channel in the architecture lets the platform deliver firmware updates and keep room state synchronised after changes.