Hotel and Guest-house Control Kept Off the Guest Network
Guest-room, corridor, back-of-house and outdoor lighting each follow different rules. A local-first LoRa architecture keeps controllable lighting on a private network, separates guest-facing automation from safety circuits, and treats documented inputs and outputs as the only integration points.
Site constraints
Guest Wi-Fi has to stay separate
The guest network carries visitor traffic and is expected to change as the property is used. Running building control on it would couple lighting and operations to that traffic, so the control network is kept separate.
Occupancy that changes by the hour
Corridors, restaurants, gardens and back-of-house areas have different occupancy patterns through the day. The rules have to be local and adjustable by staff rather than fixed at commissioning or held only in a remote service.
Safety and critical circuits are not guest automation
Emergency lighting, lifts, fire systems and other critical circuits are outside scope. Only controllable lighting and defined controllable circuits are in view, and the boundary is agreed with the operator and the integrator first.
How the system is arranged
A separate control network
A gateway sits in the plant room, and switches on corridor, back-of-house and outdoor circuits talk to it over LoRa. Guest-facing convenience features and building control are kept on different networks.
Required, optional and degraded behaviour
Required: the gateway and the local schedule and scene engine stay on site. Corridor and back-of-house lighting continue without an uplink.
Optional: cloud management and any link to a property or booking system are added only through documented interfaces, and only as a management layer.
Degraded: if the uplink drops, remote dashboards and alerts pause while local schedules continue. If the gateway loses power, affected circuits fall back to their defined fail states.
Keeping guest automation apart from safety
Guest-facing convenience features are kept apart from safety and critical systems. Only documented inputs and outputs are integrated, so the scope of what the system touches is explicit and reviewable.
What you can verify
- Fewer cable runs for corridor, back-of-house and outdoor control.
- Local rules continue through an uplink outage, so public-area lighting is not tied to a remote service.
- Fault localisation to a single floor or zone rather than the whole property.
- Room-by-room or floor-by-floor rollout, so wings can be migrated as occupancy allows.
- A clear scope boundary with safety and critical systems, agreed in writing before work starts.
Who is involved on site
Site operator or facilities team
Corridor and public-area lighting that behaves predictably through occupancy changes and uplink outages, with an override any duty manager can use.
Systems integrator
Documented interfaces so control links only to specified systems, and a firm boundary around safety and critical circuits.
Electrical contractor or installer
Mounting and enclosure choices that suit a working hotel, plus defined fail states for each circuit.
Pre-specification checklist
- Floor and zone layout, with corridors, public areas and back-of-house spaces marked.
- Which circuits are in scope as controllable lighting, and which are excluded as safety or critical systems.
- Supplies available at each point, and whether any point needs battery power.
- Space for the gateway in the plant room, with power and a network feed.
- Existing systems and the documented interfaces to be integrated.
- Occupancy patterns and the required behaviour out of hours.
- Phasing constraints, such as wings that cannot be closed during the work.
- The target radio band and any local radio rules that apply to the site.
Supported SKUs
Availability in your market — Global (English)
Not currently offered in this market
Radio authorisation, electrical approvals or an authorised importer are not in place for this destination. We will confirm the compliance path when you enquire.
Availability follows the market pack, not the language you are reading.
| Model | Radio band | Maximum load | Supply voltage | Status |
|---|---|---|---|---|
| LS-WS-1G1-gang LoRa wall switch, EU868 | EU868 | 10 A | 230 V | inquirable |
| LS-WS-2G2-gang LoRa wall switch, EU868 | EU868 | 10 A | 230 V | inquirable |
| LS-DIN-4CH4-channel LoRa DIN controller, EU868 | EU868 | 10 A | 230 V | inquirable |
| LS-GW-100LoRa private-network gateway, Ethernet, EU868 | EU868 | 0.5 A | 12 / 24 V | inquirable |
| LS-SN-MTLoRa occupancy sensor, EU868 | EU868 | 0.05 A | 3 V | concept |
Next steps
Send this first
Send the floor layout, the in-scope and excluded circuit lists and the notes above through the site-fit request. A first response confirms which zones look feasible and where a survey is needed.
What happens next
We return a feasibility note covering gateway siting, the proposed radio layout, the agreed scope boundary and any point needing a site visit. A confirmed specification and supported SKU list follow the survey, with the conditions each claim depends on.