# knxUltimateHueButton Node – Tutorial Outline

## 1. Intro (0:00)
- "Hey everyone! Let’s connect Hue button events to KNX using the `knxUltimateHueButton` node."
- "We’ll bind Hue taps and dim gestures to KNX group addresses and optional status feedback."

## 2. Requirements (0:25)
- `knxUltimate-config` gateway (optional but recommended for ETS autocomplete).
- `hue-config` bridge with valid credentials.
- Hue wireless button or switch already paired with the bridge.

## 3. Inputs and Outputs (0:45)
- Inputs: none (Hue webhooks feed the node automatically).
- Output: single output delivering KNX-ready payloads for the configured addresses (dimming, single press, double press, status).

## 4. KNX Gateway and Hue Bridge (1:05)
- Select KNX gateway (`server`) to enable CSV lookup and secure GA formatting.
- Select Hue bridge (`serverHue`) so the node can query Hue resources.

## 5. Dimming (Repeat) Mapping (1:25)
- **Group Address** (`GArepeat`): GA for dimming step telegrams (DPT `3.007`).
- **Name**: descriptive label for the dimmer channel.
- **DPT**: dropdown auto-populated with `3.007` variants.

## 6. Short Press Mapping (1:55)
- **GA Short Release**: GA triggered on short release (typically `1.001`).
- **Status GA**: optional GA to update the KNX button LED state.
- **Toggle Values**: when enabled, the node alternates between `true/false`; otherwise, specify static send values and status updates separately.

## 7. Double Press Mapping (2:30)
- Optional rows for double short release and status, each with their own GA and DPT (`1.xxx`).
- Autocomplete uses ETS CSV to fill names and datapoints.

## 8. Send Options (2:55)
- **Switch Send**: typed input (bool) controlling the payload used when the button toggles.
- **Dim Send**: typed input with options `up`, `down`, `stop` for hue dim events converted to KNX step commands.

## 9. Hue Device Selection (3:20)
- Start typing the Hue button name; autocomplete lists `rtype=button` resources.
- The selected Hue device ID is stored in the hidden field; one KNX node can track a single Hue hardware button.

## 10. Flow Behaviour (3:45)
- Hue press/hold/dim events arrive via the bridge, the node maps them to the configured GAs.
- Output payloads are ready to be injected into `knxUltimate` nodes or other automation logic.
- Status GAs let you keep KNX feedback LEDs in sync with Hue button state.

## 11. Best Practices (4:10)
- Keep GA names aligned with ETS naming for clarity.
- Use separate KNX GA for short press status to avoid bus collisions.
- Combine with `knxUltimateAlerter` to supervise Hue button battery or connectivity via additional nodes.

## 12. Wrap-Up & CTA (4:35)
- "We linked Hue and KNX, mapped dimming, single/double presses, and configured toggle behaviour."
- "Like and subscribe for more Hue-to-KNX integrations, and comment with your button automations!"