homelab-optimized/docs/infrastructure/hosts/concord-nuc-runbook.md

Concord NUC Runbook

Intel NUC6i3SYB - Home Automation & DNS

Endpoint ID: 443398
Status: 🟢 Online
Hardware: Intel Core i3-6100U, 16GB RAM, 256GB SSD
Access: concordnuc.vish.local

---

Overview

Concord NUC runs lightweight services focused on home automation, DNS filtering, and local network services.

Hardware Specs

Component	Specification
Model	Intel NUC6i3SYB
CPU	Intel Core i3-6100U (2-core)
RAM	16GB
Storage	256GB SSD
Network	1x 1GbE

Services

Critical Services

Service	Port	Purpose	Docker Image
AdGuard Home	3053/53	DNS filtering	adguard/adguardhome
Home Assistant	8123	Home automation	homeassistant/home-assistant
Matter Server	5580	Matter protocol	matter-server/matter-server

Additional Services

Service	Port	Purpose
Plex	32400	Media server
Invidious	2999	YouTube frontend
Piped	1234	YouTube music
Syncthing	8384	File sync
WireGuard	51820	VPN server
Portainer Agent	9001	Container management
Node Exporter	9100	Metrics

---

Network Position

Internet
    │
    ▼
[Home Router] ──WAN──► (Public IP)
    │
    ├─► [Pi-hole Primary]
    │
    └─► [AdGuard Home] ──► Local DNS
              │
              ▼
        [Home Assistant] ──► Zigbee/Z-Wave

---

Daily Operations

Check Service Health

# Via Portainer
open http://concordnuc.vish.local:9001

# Via SSH
ssh homelab@concordnuc.vish.local
docker ps

Home Assistant

# Access UI
open http://concordnuc.vish.local:8123

# Check logs
docker logs homeassistant

AdGuard Home

# Access UI
open http://concordnuc.vish.local:3053

# Check DNS filtering
# Admin → Dashboard → DNS Queries

---

Common Issues

Home Assistant Won't Start

1. Check logs: docker logs homeassistant
2. Verify config: config/configuration.yaml
3. Check Zigbee/Z-Wave stick
4. Restore from backup if needed

AdGuard Not Filtering

1. Check service: docker ps | grep adguard
2. Verify DNS settings on router
3. Check filter lists: Admin → Filters
4. Review query log

No Network Connectivity

1. Check Docker: systemctl status docker
2. Verify network: ip addr
3. Check firewall: sudo ufw status

---

Home Assistant Configuration

Add-ons Running

• Zigbee2MQTT
• Z-Wave JS UI
• File editor
• Terminal

Backup

# Manual backup via UI
Configuration → Backups → Create backup

# Automated to Synology
Syncthing → Backups/homeassistant/

Restoration

1. Access HA in safe mode
2. Configuration → Backups
3. Select backup → Restore

---

AdGuard Home Configuration

DNS Providers

• Cloudflare: 1.1.1.1
• Google: 8.8.8.8

Blocklists Enabled

• AdGuard Default
• AdAway
• Malware domains

Query Log

Access: Admin → Logs

• Useful for debugging DNS issues
• Check for blocked domains

---

Maintenance

Weekly

• Check HA logs for errors
• Review AdGuard query log
• Verify backups completed

Monthly

• Update Home Assistant
• Review AdGuard filters
• Clean unused Docker images

Quarterly

• Test automation reliability
• Review device states
• Check Zigbee network health

---

Emergency Procedures

Home Assistant Down

Impact: Smart home controls unavailable

1. Check container: docker ps | grep homeassistant
2. Restart: docker-compose restart
3. Check logs: docker logs homeassistant
4. If corrupted, restore from backup

AdGuard Down

Impact: DNS issues on network

1. Verify: dig google.com @localhost
2. Restart: docker-compose restart
3. Check config in UI
4. Fallback to Pi-hole

Complete Hardware Failure

1. Replace NUC hardware
2. Reinstall Ubuntu/Debian
3. Run deploy playbook:

   ansible-playbook ansible/homelab/playbooks/deploy_concord_nuc.yml
   

---

Useful Commands

# SSH access
ssh homelab@concordnuc.vish.local

# Restart services
docker-compose -f /opt/docker/compose/homeassistant.yaml restart
docker-compose -f /opt/docker/compose/adguard.yaml restart

# View logs
docker logs -f homeassistant
docker logs -f adguard

# Check resource usage
docker stats

---

Device Access

Device	Protocol	Address
Zigbee Coordinator	USB	/dev/serial/by-id/*
Z-Wave Controller	USB	/dev/serial/by-id/*

---

Links

• Home Assistant
• AdGuard Home
• Plex
• Invidious