Phase 2 — every light in one place, with her usual settings one tap away

Sequence lives in PLAN.md; the live worklist lives in DOD.md. Builds on phase-1.md (the codec, the transmitter, the lights list, Simple mode). Owes CONTEXT.md two terms: Scene and Full controls, and a sharper Simple mode.

What closing this phase means. Today each light has On, Off, two sliders and one remembered setting. After this phase: a light can be renamed; it carries named scenes (three ready-made, and any she saves) applied with one tap; it can be told to switch itself off in one or two hours; the list has All off; and Simple mode is a real setting that strips the light’s screen down to On, Off and brightness. Asked of a device: the emulator walk at the end, since no lamp is in reach.

The door (closed testing) opens after this phase (PLAN.md). Nothing here adds a permission.

What is in, and what is deliberately not

In: rename, scenes, the switch-off timer, All off, the Simple mode setting.

Not in, and each with a reason rather than a phase:

• Rooms or groups. One person, a handful of lights: All off covers the case that matters.
• A timer in minutes. The only timer the vendor app’s captures show is whole hours (0xA5, arg0 = hours); anything finer is a guess at the protocol.
• Showing whether a light is on. The lamp cannot say (phase 0).
• Scenes shared across lights. A scene belongs to the light it was saved on; a lamp in the bedroom and one in the kitchen want different Evenings.

Checkpoints

1. Scenes

@Serializable data class Scene(val id: String, val name: String? = null, val preset: ScenePreset? = null,
                               val setting: LightSetting)
@Serializable enum class ScenePreset { EVENING, READING, NIGHT_LIGHT }

A preset scene has no name: its label is a string resource, so it follows the app’s language. A scene she saves has a name and no preset. Light.scenes defaults to the three presets, so every light stored by 0.2.0 reads them on upgrade with no migration (LightsJsonTest gains the case).

Coldness assumes 0 is warm; R3 in phase-1.md is still owed, and if it reads backwards the codec flips, not these numbers.

Applying a scene sends On, then colour, then brightness, like On, and records the setting as last sent. Save as a scene asks for a name and stores the sliders’ current values. Deleting asks first; a preset can be deleted too, and does not come back by itself.

2. Rename

From the light’s screen, a pencil in the top bar opens a dialog with the name. Blank is refused.

3. The timer

Two buttons on the light’s screen, Off in 1 hour and Off in 2 hours, sending 0xA5 with arg0 = hours. The lamp keeps the time, so the app holds no alarm and needs no scheduling permission. What the app says afterwards is that it asked the light: it cannot read back that the timer is running.

4. All off

An action in the Lights top bar when there are two or more lights. It sends Off to each in turn and reports the first problem, if any, in the usual banner.

5. The Simple mode setting

A switch in Settings, off by default: the app opens with Full controls, and whoever sets it up for someone non-technical turns Simple mode on. Stored by name in AppPreferences, listed in Keys.SETTINGS.

Add a light is the same in both. Remove and Rename sit under Full controls so that nothing in Simple mode can lose a light.

Tests

• LightsJsonTest: a light stored without scenes reads the three presets; a saved scene round-trips.
• LightCodecTest: the timer frame for 2 hours matches the captured vector (0xA5, args [2,0,0]).
• LightViewModelTest: applying a scene sends On, colour, brightness in that order and records it.

Documents this phase amends

CONTEXT.md (Scene, Full controls), store-listing.md (0.3.0 notes, the feature list), nothing in the privacy documents: no new data leaves the phone and no permission is added.

Readings

Emulator only (owner, 2026-11-11). Each row: pixel-api36, which can advertise.