Developer Hub / docs, paths and evidence

Build smart lighting with the important details visible.

The light source is only the beginning. Use product records, build guides, compatibility paths and test records to choose hardware you can configure, explain and maintain.

Technical scope

595 products / 57 guidesTechnical status shown per item

Choose your next layer

Start with the question in front of you.

A developer-friendly catalog should make the physical product, connection path and evidence easy to move between. These are four entry points into the same record.

01System map

Start here: Smart Lighting Guide

Understand the light source, driver, controller, protocol, housing and automation layers before you choose parts.

Start the guide

026 paths

Compatibility matrix

Trace the actual path from light source to controller, gateway, firmware and Home Assistant entity.

Check compatibility

034 records

Test Lab

See the method, condition, result and limit behind a technical claim before it becomes a buying signal.

Open the lab

04595 records

Product records

Find the physical light first, then inspect its input, control path, variant and evidence status.

Browse products

The product record is the interface

Hardware first. Configuration next. Evidence throughout.

Smart lighting becomes easier to build when the product page keeps the physical light and the software path in the same view. Protocol names are useful only when the exact route, variant and boundary are stated.

Open product catalog

RECORD / LC-PRODUCTVERSIONED

01Light sourceFixture, strip or module

02Control pathLocal, mesh, cloud or wired

03ConfigurationFirmware, pinout and variant

04EvidenceMethod, condition and result

A practical workflow

From shortlist to a build you can recover.

Use the site in the same order you would debug a real installation: establish the light, make the electrical path believable, then validate software and behavior.

01 / SELECT

Choose the light source

Start with form, voltage, light engine, optic and installation boundary.

02 / CONNECT

Name the control path

Record controller, gateway, transport, firmware and the features exposed.

03 / VERIFY

Check the evidence

Separate tested, documented, community and planned states before ordering.

04 / MAINTAIN

Keep recovery possible

Leave pinouts, reset access, service loops and a known-good configuration.

Need a different path?

Send the SKU, constraint or drawing. We will help define the next test.

Contact the team