Inputs to globals

Before every handler the hub builds a small bootstrap script that assigns preference values to globals named after each input's key. Not every type is hydrated.

The table is generated from the runtime on Input types.

Rules of thumbCopy Anchor Link

• Unset is undefined. Inputs without a value are undefined, not their default. Guard: typeof offAfterMinutes === 'number' ? offAfterMinutes : 1.

• Normalise multi-selects when you iterate. The proxy answers Array.isArray and fans out service calls, but a single pick is a lone wrapper:

  Copy Text

  function lightList() {
    return Array.isArray(lights) ? lights : lights ? [lights] : [];
  }

  If all you do is call a service, lights.turnOn() already handles both shapes.

• settings has everything. It is the raw object the installer saved, including types that are not hydrated. settings.recipients for an accountUserId input, settings.mode for a mode input.

• Keys are identifiers. key: 'off-after' cannot become a variable; use camelCase.

• Names must not collide with the global functions (schedule, state, location, settings, …).

Checking what you gotCopy Anchor Link

function installed() {
  console.log('settings', JSON.stringify(settings));
  console.log('sensor', motionSensor?.entityId, 'lights', getEntityIds(lights));
}