Thirteen screens on one kiosk how the whole house looks at a glance

There is a moment when "the one screen for everything" gets narrow: you want the solar output, the room temperatures, which plug is off and when the door was last opened — at the same time. HoumeOS solves this not with a hierarchy of menus but with thirteen screens, each one tap away in the bottom navigation.

How they are laid out

The shipped interface is currently in Bulgarian; the structure is the same everywhere:

• Home — the summary of the house: mode, urgent events, the values that matter.
• Energy — solar, battery, grid and consumption in one flow, plus costs by tariff.
• Climate — heating, cooling and ventilation, stepped per room.
• Plumbing — water, hot water and garden irrigation in one place.
• Security — alarm, doors, cameras and hazard sensors.
• Scenarios — ready-made modes with a single tap.
• Automations — the rules of the house, with a visual editor.
• Devices — the reference for whether everything is online.
• Rooms — setpoint and live values for each room.
• Integrations — the panel for pairing devices.
• Profiles — who has which rights.
• History — the journal of events and commands.
• Lock screen — sign-in with a profile and a PIN.

Rooms are everywhere, so they have their own screen

A room is where you feel the climate, not "device group 4". In the Rooms screen every room has its own target temperature, live readings for the actual temperature and humidity, and its own schedule. The schedule is not a separate system — it runs on the same automation engine with a time trigger. That is why the two cooperate: a rule for "before I get home" and a schedule for "cooler at night" do not fight each other.

Automations are drawn, not written

The Automations screen is the visual editor: trigger → conditions → exceptions → action. The same approach now applies to scenes — there is an editor and icons, so "Leaving" is assembled like a block instead of being configured in JSON. The rules live on the server and run even when no screen is on. For integrators who think in code this matters: the simulation without hardware runs on the same rules.

Devices: the screen that answers "is there a problem"

The most common question in a local system is not "what is 21.4°C" but "why did that plug not respond". The Devices screen is built for it: tabs for *Offline · Online · Unknown · All*, and next to each device — how long it has been silent. A device that has not answered for 45 minutes is different news from a device that is simply switched off. This is the reference both the installer and the homeowner use to decide where to look.

The same screens everywhere

The thirteen screens are not "only for the wall tablet". The same interface runs on a phone, a computer or a wall — and the same server feeds it. If you want to know why, Local-first smart home without cloud explains the architecture; if you arrive with existing equipment, see All brands in one system.

An honest note

The thirteen screens work today in the kiosk and in simulation mode, and the shipped interface is in Bulgarian. Delivery to the phone (email, push and webhook channels) is not enabled yet — for now the critical things show on the screens and in the journal. The current status of every feature is in The roadmap.