Order, on the spot

Guests come and go, yet every room is the right temperature and the right light. This local boutique hotel didn’t wire each room with a rigid “off at 11pm” rule, nor does the front desk walk a checklist room by room. It hands “what to do, and when” to seenzus — and seenzus acts on what the room actually is right now.

The setting

A local boutique hotel: a handful of guest rooms, a front desk, a few common areas, run by the owner together with front-desk and housekeeping staff. Guests stay briefly; people come and go. The devices already live on Home Assistant — lights, air conditioning, blinds, and the occupancy sensors (motion / door) that tell whether a room is empty.

Owner No rigid rules — judgment left to the room

Front desk / housekeeping Wake & reset collapse into one sentence

Guest (no login) Comfortable on arrival, nothing to switch off

How it’s wired

• One Site = this hotel. Each guest room and common area is a Space. seenzus scopes its actions and memory to Spaces — “Room 305” is a definite unit to it.
• Source: Home Assistant, bridged via seenzus Bridge. Beyond controllable devices, occupancy sensing (motion / door) is the keystone of this case — it’s the only basis seenzus has for judging whether a room is empty. Without it, the “empty-room saving” step below has nothing to stand on and falls back to manual.
• Who logs in, who doesn’t: the owner owns this Smart Space; front-desk and housekeeping join as members (scoped to just this hotel if you like). Guests never log in — to seenzus a guest is an Occupant of the space, someone it looks after, not someone who operates it.

Note

This section is what makes every later step hold up: everything seenzus does rests on which devices this hotel actually connected, and who uses it.

The journey

Follow one guest, from arrival to departure. For each step: what the guest does, how seenzus knows, and who has one less thing to mind because of it.

1. 1 Check-in
2. 2 In the room
3. 3 Stepping out
4. 4 Back again
5. 5 Checkout

Checking in

The guest taps in and the room is already at a pleasant temperature and light — not a wall of stuffy heat.

What you see in the product · room woken up

Front desk

305 has a guest now.

seenzus

Got it — 305 is awake: lights softened, AC to the comfort range.

305 · ready

Main light warm

AC 24°

Bedside soft

Blinds open

How it knows: the front desk said “305 has a guest now” in chat, or the room’s motion / door sensor felt someone enter — the Space switches from energy-saving standby to a welcoming state. Doable today.

Who minds one less thing

Front desk doesn’t run upstairs ahead of time to start the AC and test the lights. A sentence, or the guest walking in, wakes the room.

Staying in the room

The guest nudges the dimmer down and drops the AC a degree. seenzus remembers this room’s preference for this stay and follows it.

What you see in the product · preference remembered

seenzus

Noted — 305 likes it a touch warmer and dimmer this stay; I’ll follow that.

remembered · this stay

Main light low

AC 23°

Bedside warm

Blinds half

How it knows: the devices’ operation history — who did what in 305 leaves a trace.

Who minds one less thing

The owner needn’t set rigid rules like “lights off at X” or “AC locked at 26°”. The room follows how the guest actually lives in it, not a timetable taped to the wall.

Stepping out (AC left on)

The guest heads out, leaving the AC and lights on. After a while the room quietly settles down — AC eased back to saving, lights off.

How it knows: the room has been empty for a sustained stretch (motion / door) — not a misread off a single door-open. It acts on “genuinely nobody here,” not on “it’s the afternoon.” Doable today.

What you see in the product · empty-room saving

seenzus

No one’s in 305 right now — I’ll ease the AC back and turn the lights off; I’ll restore it when someone returns.

eased back · will restore on return

Main light off

AC saving

Bedside off

Blinds closed

Who minds one less thing

The owner: an empty room simply isn’t burning power — nobody has to remember to switch off after a guest.
Housekeeping: daytime comings and goings won’t be misread as “occupied” — the judgment is sustained absence, not one door-open.

Back in the room

The guest returns and the room is comfortable again, just as they left it.

What you see in the product · back, restored

seenzus

Someone’s back in 305 — restoring the lights and AC to how you left them.

restored · as you left it

Main light low

AC 23°

Bedside warm

Blinds half

How it knows: it senses someone present again (motion / door) — and restores the guest’s earlier settings.

Checking out

The guest grabs their bag and leaves, minding none of the lights, AC, or blinds.

What you see in the product · checkout reset

Front desk

305 has checked out.

seenzus

Got it — resetting 305: AC and lights off, blinds closed, ready for housekeeping.

305 reset · awaiting cleaning

Main light off

AC off

Bedside off

Blinds closed

How it knows: this step seenzus does not know on its own. It isn’t wired to the hotel’s PMS and can’t read the door lock — “this guest checked out” is a sentence the front desk or housekeeping tells it in chat. Once told, it resets the whole room in one go.

Who minds one less thing

Housekeeping doesn’t enter each room to switch things off and check them one by one; the front desk’s checkout wrap-up collapses into a single sentence.

What it doesn’t do

Stating the edges up front is what makes the rest believable:

• It doesn’t know who the guest is. Guests don’t log in — an Occupant, not an account holder. It looks after the room, not the individual.
• It isn’t wired to the PMS and can’t read the lock. Events that live in the hotel’s systems — like “checked out” — don’t reach it; a person says it in chat, and it never pretends to know on its own.
• It doesn’t act on guesses. It won’t switch off the AC because “it’s the afternoon”; it acts because “this room is genuinely empty.” A room with no occupancy sensor honestly degrades to manual — it won’t fake a reading.
• It doesn’t act behind your back. Every write is confirmed with a person first — it’s the butler, not the master.

One line for each

• Owner: no need to pile up rigid rules for peace of mind — an empty room settles itself and a busy one stays lively; the judgment is left to what’s actually happening on site.
• Guest: never aware there’s an AI at work — the room is comfortable on arrival, and there’s nothing to remember to switch off on the way out.
• Front desk / housekeeping: waking a room and resetting after checkout both collapse into a single sentence in chat — no walking a checklist room by room.