# knxUltimateHueMotion Node – Tutorial Outline

## 1. Intro (0:00)
- "Welcome back! We’re integrating Hue motion sensors with KNX using the `knxUltimateHueMotion` node."
- "Great for presence-driven lighting, security alerts, or HVAC control."

## 2. Prerequisites (0:20)
- Optional `knxUltimate-config` gateway for CSV autocomplete.
- Required `hue-config` bridge credentials.
- Hue motion sensor paired with the bridge."

## 3. Inputs & Outputs (0:40)
- Inputs: none (Hue events feed the node).
- Output: single boolean payload representing motion detection state."

## 4. KNX Mapping (1:00)
- Select the KNX group address (usually `1.004` for movement). Autocomplete filters to `1.xxx` DPTs.
- Name the GA for clarity using ETS metadata.
- Pick the target DPT from the list of `1.xx` boolean datapoints."

## 5. Hue Device Selection (1:35)
- Type the sensor name; autocomplete lists `rtype=motion` resources.
- Selected ID is stored so the node subscribes to the correct device."

## 6. Behaviour Options (1:55)
- **Node PINs**: toggle the behaviour tab to hide/show the output pin depending on whether you want to wire the message stream."
- Tip: even with pins hidden the node still emits messages for downstream `link` nodes."

## 7. Runtime Behaviour (2:15)
- Hue motion events are converted into `true/false` payloads.
- Use with `knxUltimate` writer nodes to update KNX actuators or logic."

## 8. Best Practices (2:35)
- Add a debounce function if your KNX logic requires hold/release delays.
- Combine with `knxUltimateHueLightSensor` for ambient light compensation."
- Use names that include location (“Hallway Motion”) for easier debugging."

## 9. Demo Ideas (3:00)
- Turn on corridor lights when motion is detected after sunset.
- Feed a KNX security input to log unexpected movement."

## 10. Wrap-Up & CTA (3:25)
- "We connected the Hue bridge, mapped the GA, and discussed best practices for motion-triggered flows."
- "Subscribe for more Hue sensor integrations and leave your automation examples below!"
