Reference
What am I looking at?
Flight Day shows real data or says plainly what it’s waiting for. A missing value is never a default, and an old value carries its age.
The headline in each area
| Area | Look here first |
|---|
| Home | The big clock and the line under it: the next event, the wake time or a launch’s T-minus. Then Weather, and Today or Tomorrow. |
| Space | The top row of the manifest, with its T-minus, and the brief under the globe. |
| House | The lights that are on, what’s playing, and the thermostat’s mode and setpoint. |
| Night | Tomorrow’s wake time, whether the alarm is armed, and Tonight: what Goodnight will do. |
| Status | What’s connected and what isn’t, and plan limits. |
Fresh, old and missing
| You see | It means |
|---|
| “as of 6:10 AM” on a dimmed tile | The data is older than it should be. It’s the last value received, not a fresh reading. |
| A standby line, such as “Thermostat not connected” or “Calendar not connected” | That source isn’t connected. Nothing is filled in for it. |
| “Not connected” in Status, with a list | The sources that have no connection, each with a link to the setting that fixes it. |
| “Home Assistant · not connected — add URL + token in Settings” | No house is set up on this screen. |
| “This card could not load · try again from Settings → Reload” | A tile failed to draw. |
| “House action not confirmed · reconnecting” | A command didn’t come back confirmed. Don’t assume it worked. |
The alarm
| You see | It means |
|---|
| “T-04:12 · liftoff 6:50 AM” | The count to your wake time. |
| “liftoff 6:50 AM · up by 7:20 AM · 1 snooze” | The alarm header: liftoff, the up-by time and snoozes used so far. |
| “Snoozed · liftoff 7:00 AM”, or “snoozing · liftoff …” at night | Waiting to count down again. |
| “No more snoozes — up by …” | The up-by time is too close for another snooze. |
| “Final launch” | The last liftoff before up-by. I’m up needs a hold. |
| “muted · the lights will still rise” | The bedroom speaker is muted. Flight Day never unmutes it in the morning. |
| “house offline — lights not held” | The screen is running its own backup alarm, without the house. |
| “Up … · no answer” | Nobody answered; the alarm stopped after 15 minutes. |
The house
| You see | It means |
|---|
| “Comfort · waiting for the house” or “Comfort offline” | No comfort status has arrived from Home Assistant yet. |
| “Room sensors · waiting for Apple Home” | No room readings have arrived yet. |
| “· not counted” on a dimmed room | That reading is too old, or the room is left out, so comfort ignores it. |
| “Comfort is quiet for the night” | A bedroom screen at night: comfort controls wait until morning. |
| “Choose Heat or Cool to see its setpoint” | The thermostat is Off, so there’s no setpoint to show. |
| “Needs a hand” | The vacuum is stuck or needs maintenance. |
Labels and badges
| You see | It means |
|---|
| LIVE banner | A launch is in flight. Watch opens it. |
| Plan limits: live, standby, “report from …”, “limit hit”, “est.” | The state of each AI plan’s usage report. A limit the service doesn’t report is never made up. |
| A yellow “demo” chip | That tile shows sample data, on purpose. |
| “AI” on a line | The line was made by AI. |
| “Estimated · typical ascent, not telemetry” | Flight Director’s altitude and speed are a typical ascent, not live data. |
Coming later
Go / No-Go Concept: a line at the top of the briefing, for example “Checks incomplete · weather as of 6:10 AM”. Until then, the briefing shows each input with its own age.
