LUMA-6CH / System architecture
Design lighting for the day something is missing.
How we prepare and verify this contentA local-first system runs essential control, configuration and state retention inside the building. Remote services can add access or automation, but their absence should not remove basic controls, operational safety or customer access to data.
The essential path should be shortest.
Separate four layers: power and outputs, local control, LAN integration and optional remote services. An essential physical command should reach the controller without crossing the internet. Local configuration should remain accessible even when a vendor account does not exist or is unavailable.
| Layer | Responsibility | Allowed dependency |
|---|---|---|
| Outputs | Safe load drive | No network |
| Local control | Commands, essential scenes, setup | LAN / device |
| Integration | Automation and supervision | Local network |
| Remote | Optional off-site access | Internet |
Write expected behaviour before causing failure.
- Internet unavailable: local commands and essential setup remain available.
- Access point unavailable: local buttons or inputs retain defined functions.
- Controller restart: outputs return to a documented safe state.
- Integration stalled: timeouts prevent a request from holding the system.
- Vendor unavailable: documented configurations and interfaces remain with the customer.
Ownership means being able to operate and migrate.
The customer should know where configuration, logs and credentials reside, how to export them and who can change them. Integrations should use documented interfaces and revocable identities, not shared accounts or untracked secrets.
Updates and remote access require a separate policy: authentication, signing, rollback, maintenance window and behaviour after failure. Local-first does not mean never updating; it means not surrendering operational control in order to update.
Accept the system without internet, not only with it.
During handover disconnect WAN, temporarily turn off the access point, restart supply and controller and simulate integration unavailability. Record retained functions, recovery times and output state. The result becomes part of installation documentation.
Architecture is a system property. LUMA-6CH is configured locally in a browser and normal operation does not require a cloud, account or app. Final resilience still depends on how supply, network, inputs and automations are designed in the installation.
Explore the local control architecture of LUMA-6CH.
LUMA-6CH