# knxUltimateWatchDog Node – Tutorial Outline

## 1. Intro (0:00)
- "Hey! The `knxUltimateWatchDog` node monitors KNX gateway connectivity and optional group address heartbeats."
- "We’ll configure Ethernet-only checks, KNX telegram monitoring, retry intervals, and outputs."

## 2. Inputs & Outputs (0:20)
- Input: optional control messages (start/stop commands).
- Output: emits watchdog status objects (OK, retry count, error)."

## 3. Core Settings (0:40)
- **Server**: select the KNX gateway to supervise.
- **Check Level**: choose `Ethernet` (ping gateway IP) or `Eth+KNX` (also monitor a KNX GA heartbeat).
- **Topic**: used when `Eth+KNX` to select the GA to monitor (must be `DPT1.x`).
- **Name**: optional label.
- **Auto Start**: begin monitoring immediately after deploy."

## 4. Advanced Options (1:15)
- **Retry Interval**: seconds between connectivity checks.
- **Max Retry**: number of failed attempts before raising an error.
- After the threshold, the node emits an alarm and can restart the gateway or notify users."

## 5. Operation Modes (1:45)
- *Ethernet*: checks if the gateway host responds (ICMP/HTTP depending on implementation).
- *Eth+KNX*: also expects the KNX GA to toggle (heartbeat). Use a `knxUltimate` node or clock to publish to that GA."

## 6. Output Payload (2:10)
- Status `OK`, `Retry`, or `Error`, including counts and timestamps.
- Combine with dashboard or `knxUltimateAlerter` for notifications."

## 7. Best Practices (2:30)
- Choose a dedicated GA for heartbeat (`DPT1.001`) and pulse it periodically.
- Set `maxRetry` high enough to avoid false alarms when the network hiccups.
- Integrate output with `knxUltimateAutoResponder` or scripts to reboot gateways."

## 8. Demo Ideas (2:55)
- Use dashboard indicator to show gateway health (green/yellow/red).
- Trigger SMS or push notification if the watchdog hits max retries."

## 9. Wrap-Up & CTA (3:15)
- "We configured check levels, retry timers, and GA heartbeats."
- "Subscribe for more KNX maintenance workflows and share your watchdog setups!"