# knxUltimateSceneController Node – Tutorial Outline

## 1. Intro (0:00)
- "Welcome back! In this tutorial we automate KNX scenes with the `knxUltimateSceneController` node."
- "We’ll recall, save, and customise scenes directly from Node-RED logic or dashboards."

## 2. Inputs & Outputs (0:20)
- Single input: accepts Node-RED messages to trigger or save KNX scenes.
- Single output: returns operation results or forwarded bus messages."

## 3. Core Configuration (0:40)
- **Server**: choose the KNX gateway.
- **Name**: friendly label for the workspace.
- **Output Topic**: optional override for outgoing messages."

## 4. Scene Recall Settings (1:00)
- **Scene GA / DPT**: select the KNX address and datapoint (supports `1.xxx`, `3.007`, `18.001`, `232.600`, `251.600`).
- **Trigger Payload**: default payload the node sends when you press the scene button in the UI or call the recall function.
- Automatic prompts suggest JSON templates for complex DPTs (e.g., `3.007` dimming or RGB values)."

## 5. Scene Save (1:40)
- Optional second GA/DPT for storing current device states into a scene.
- **Save Trigger**: payload to use when saving.
- You can expose both recall and save in your UI or flows."

## 6. Rule Engine (2:05)
- Inspect incoming messages using typed input field (`msg`, `flow`, or `global`).
- Build rule table: compare values (`eq`, `gt`, etc.) and map them to specific scene numbers or payloads.
- Useful when multiple buttons or states map to different scenes."

## 7. Operation Tips (2:35)
- Use `topicTrigger` and `topicSaveTrigger` to keep default payloads ready for manual testing.
- The node auto-suggests payload structures for DPT `3.007`, `18.001`, `232.600`, and `251.600` to avoid syntax errors.
- Combine with `knxUltimateLogger` to verify scenes in ETS diagnostics."

## 8. Workflow Example (3:05)
- Input links to MQTT commands or dashboards.
- Rule table maps `scene = relax`, `scene = concentrate`, `scene = tv` to numeric scene recalls.
- Save GA triggered manually to capture a new state when the room is perfect."

## 9. Best Practices (3:35)
- Document each scene number in ETS to keep Node-RED and ETS aligned.
- Use `flow` or `global` typed inputs when multiple nodes share triggers.
- Keep JSON payloads formatted (use Node-RED function nodes to build them programmatically)."

## 10. Wrap-Up & CTA (4:00)
- "We linked the gateway, configured recall and save GAs, and set up rules for dynamic scene selection."
- "Like and subscribe for more KNX/Node-RED scene automation tutorials!"