Getting started

One command finds the lamps, checks what is usable, and writes the config.

$ lume setup
Scanning the network for 3 s…

  ● keylight-2399    192.168.1.131   ready           off
  ! keylight-99da    192.168.1.29    not trusted     reachable, but it does not accept this certificate
  ● hue              192.168.1.53    ready           10 rooms, 2 zones, 34 lights
      room   Büro                       → buero
      room   Küche                      → kueche
      light  Hue go 1                   → hue-go-1
      …

Needs you
  · The lamp at 192.168.1.29 is probably still paired with the Elgato app.
    Factory-reset it, then run: lume onboard "<your wifi>"

At a terminal, setup asks. It offers to create your certificate authority, to pair with a Hue bridge while you hold its button down, and to name each lamp before it writes anything.

Every lamp is written down individually — each Elgato, each Hue room, each zone and each single light — so anything you own can be named on the command line. Use --groups for rooms and zones only. Existing entries are never touched, which makes running setup again after buying a lamp perfectly safe.

$ lume ls
$ lume buero on --brightness 40
$ lume all off

When something else is driving

Whether setup asks questions is decided the way Unix tools have always decided it: a terminal on both ends means a person is there. Piped or redirected — a script, a cron job, an agent — it asks nothing and changes nothing, and reports instead.

lume setup --json    # the same findings, as data
lume setup --write   # save them without asking

The JSON carries a next array holding exactly the actions that need a human hand — press this button, factory-reset that lamp — so an automated caller can do everything else and hand back a short, precise list.

The pieces, separately

setup is a front end over commands that also stand alone.