Hospitality
Hotel Wi-Fi rated by the guest, not by the survey
Hotel Wi-Fi is judged by one person in one room at 11pm, not by an average across the property. That is why corridor-mounted access points keep disappointing: the survey looks fine, and the guest behind a tiled bathroom wall two rooms down still cannot hold a video call.
The design that consistently works is unglamorous — one access point per room, on the wall, with the wired ports the room already needs behind it.
- 1 per room
- Wall-plate AP — no corridor dead spots
- 4× LAN
- Wired ports behind each room AP
- 48
- Room APs on one riser switch
- 300
- Access points in one self-organising network
What goes wrong
The failure modes this design exists to prevent
Not a list of pain points — the specific ways this kind of deployment gets found out, usually after handover.
Corridor access points do not get through bathroom walls
Tile, concrete, mirrors and lift shafts sit between a corridor AP and the far corner of a room. Coverage measured in the corridor says the floor is covered. The guest at the window, with a bathroom between them and the AP, is on one bar.
Guests still want a cable
The smart TV, the desk, and increasingly a games console all want a wired port. A room with only wireless means either a visible switch on the desk or a support call at check-in.
Lobby and ballroom are a different problem entirely
A conference in the ballroom is 300 devices in one room for four hours. That is a density problem, not a coverage problem, and the AP that suits a guest room is the wrong answer for it.
Guest traffic reaching the PMS
The property management system, the payment terminals and the back office must not share a broadcast domain with guest devices. When they do, it is usually discovered during an audit or an incident.
Every property is managed separately
A group with six hotels ends up with six consoles, six firmware versions and no consistent view of which property has a problem tonight.
The design
How we build it
In build order, with the models that carry each part and why they were chosen.
One wall-plate AP per room
The L7-W is Wi-Fi 7 BE3600 in an 86 mm wall-plate footprint: a 2.5GbE uplink, four Gigabit LAN ports behind it with PoE passthrough on one, 511 total clients and under 15 W. It replaces the room's data faceplate rather than adding to it, and the TV and desk plug straight in.
High-density PoE in the floor riser
The LS2-48GT4SFP-P aggregates 48 room APs on PoE+ with four SFP uplinks and 104 Gbps of switching capacity. One switch per riser, fibre back to the core, and the cabling story per floor stays simple.
Captive portal and PMS integration at the gateway
The LR300G-P carries the branded portal, voucher and room-number authentication, WAN load balancing with automatic failover, and 64 VLANs for guest, staff, PMS, CCTV and IPTV separation — 1.5 Gbps and 100,000 sessions, sized for 300 or so concurrent users.
One console across every property
Lysora Cloud shows all properties in one dashboard with zero-touch provisioning, so a new hotel joins the group's standard on power-up rather than after a two-day commissioning visit.
Reference bill of materials
What typically goes in the quote
A starting point, not a fixed kit. Quantities and models move with the site — that is what the design conversation is for.
| Role | Model | Why this one |
|---|---|---|
| Guest room AP | L7-W | Wall-plate Wi-Fi 7, 2.5GbE uplink, 4× LAN with PoE out, under 15 W |
| Lobby, restaurant, ballroom | L7Pro | Tri-band BE14000 with 10G SFP+ — built for conference density |
| Corridor and back-of-house | L7 | Dual-band BE5040, 511 clients, self-organising to 300 APs |
| Outdoor pool, garden, driveway | L7-T | IP65, −30 to +65 °C, BE5040 on a single 2.5GBASE-T PoE+ run |
| Floor riser switch | LS2-48GT4SFP-P | 48× PoE+, 370 W, 4× SFP, 104 Gbps — one per riser |
| Property gateway | LR300G-P | Captive portal, WAN failover, 64 VLANs, 8× PoE+ out, 300 users |
| Large property gateway | LR1500XS | 4 Gbps and 1,500 clients for resorts and convention hotels |
Field notes
What catches people out on Indian sites
The things a datasheet will not tell you and a survey usually misses, gathered from deployments rather than from a brochure.
- Check whether the room already has a data faceplate. If it does, the L7-W usually goes in on the existing back box and the retrofit is a swap, not a re-cable.
- Heritage properties often forbid visible cabling and ceiling penetrations. Wall-plate APs solve a conservation problem as much as a coverage one.
- Banquet bookings are the real capacity spec. Size the ballroom for the largest event the property sells, not for its average evening.
- Ask the PMS vendor for their network requirements in writing before commissioning. Integration surprises at go-live are the most common delay we see.
- Indian properties frequently run on generator during outages. Confirm which riser switches sit on backed-up circuits, or guest Wi-Fi dies exactly when guests are in their rooms.
FAQ
Hotels and hospitality — common questions
Is a wall-plate AP in every room really necessary?
It is the design that survives guest feedback. Corridor-mounted access points have to get through tiled bathroom walls, mirrors and concrete to reach the far corner of a room, and the guest at the window is the one who writes the review. A wall-plate unit like the L7-W also gives the room four wired ports for the TV and desk, so it usually replaces the existing data faceplate rather than adding hardware.
Can the captive portal carry our branding and connect to the PMS?
Yes. The gateway supports a branded portal with voucher or room-number authentication, and the platform supports PMS integration. We ask for the PMS vendor's network requirements in writing before commissioning, because integration surprises at go-live are the single most common cause of delay on hotel projects.
How do we keep guest devices away from the PMS and payment systems?
VLAN separation at the switch and gateway. Guest, staff, PMS, CCTV and IPTV each get their own VLAN with no route between them — the LR300G-P supports 64, and the managed switch line supports up to 4094. Guest traffic is also rate limited so a conference floor cannot crowd out the back office.
Other deployment patterns
Send the site. Get the design and the BOQ.
A floor plan, a camera count or an existing BOQ is enough to start — and the coverage heatmap comes back with it, free.