# Omada Controller Query Instructions

**Date**: 2026-01-05  
**Purpose**: Query Omada controller to find device using 192.168.11.14

---

## Omada Controller Information

| Property | Value |
|----------|-------|
| **VMID** | 103 |
| **Host** | r630-02 (192.168.11.12) |
| **IP Address** | 192.168.11.20 |
| **Port** | 8043 (HTTPS) |
| **Web Interface** | https://192.168.11.20:8043 |
| **Status** | ✅ Running |

---

## Query Methods

### Method 1: Web Interface (Recommended)

1. **Access Omada Controller**:
   - URL: `https://192.168.11.20:8043`
   - Login with admin credentials

2. **Navigate to Devices**:
   - Go to **Devices** section
   - Look for device with IP `192.168.11.14`
   - Check MAC address `bc:24:11:ee:a6:ec`

3. **Device Information**:
   - Device name
   - Device type (router, switch, AP, client)
   - Connection status
   - Port assignment

### Method 2: API Query (If Credentials Available)

**Using query-omada-devices.js**:
```bash
cd /home/intlc/projects/proxmox

# Ensure credentials are in ~/.env:
# OMADA_CONTROLLER_URL=https://192.168.11.20:8043
# OMADA_ADMIN_USERNAME=admin
# OMADA_ADMIN_PASSWORD=<password>
# OMADA_SITE_ID=<site-id> (optional)

node query-omada-devices.js | grep -A 10 "192.168.11.14"
```

**Using MCP Omada Server** (if configured):
- Use `omada_list_devices` tool
- Filter for IP 192.168.11.14
- Get device details

### Method 3: Direct Container Access

```bash
# Access Omada container
ssh root@192.168.11.12
pct enter 103

# Check Omada logs or database for device information
# (Requires knowledge of Omada internal structure)
```

---

## What to Look For

### Device Information Needed

1. **Device Name**: What is the device called in Omada?
2. **Device Type**: Router, Switch, AP, or Client?
3. **MAC Address**: Does it match `bc:24:11:ee:a6:ec`?
4. **Connection Status**: Online/Offline?
5. **Port Assignment**: Which switch port is it connected to?
6. **VLAN Assignment**: What VLAN is it on?

### Expected Findings

**If it's a container/VM**:
- Should show as a "Client" device
- May show hostname or container name
- MAC address will match

**If it's a network device**:
- Will show as Router/Switch/AP
- Will have device model information
- May show firmware version

**If it's not in Omada**:
- Device might be on different network segment
- Device might not be managed by Omada
- Device might be using static IP outside Omada management

---

## Next Steps After Query

1. **If Device Found in Omada**:
   - Document device information
   - Determine if it's a container, VM, or network device
   - Plan IP reassignment

2. **If Device Not Found in Omada**:
   - Device is likely not managed by Omada
   - May be on different network segment
   - May require network scan or physical inspection

3. **Resolution**:
   - Stop/remove container if found
   - Reconfigure device if network device
   - Reassign IP to r630-04 when powered on

---

## Troubleshooting

### Cannot Access Omada Web Interface

1. **Check container status**:
   ```bash
   ssh root@192.168.11.12 "pct status 103"
   ```

2. **Check network connectivity**:
   ```bash
   ping -c 2 192.168.11.20
   curl -k https://192.168.11.20:8043
   ```

3. **Check firewall rules**:
   - Ensure port 8043 is accessible
   - Check if Cloudflare tunnel is needed

### API Query Fails

1. **Check credentials**:
   - Verify ~/.env file exists
   - Check OMADA_* variables are set
   - Test credentials manually

2. **Check SSL certificate**:
   - May need to set `OMADA_VERIFY_SSL=false`
   - Check certificate validity

---

**Last Updated**: 2026-01-05  
**Status**: 📋 **INSTRUCTIONS READY**  
**Next**: Access Omada web interface to query devices
