hdhr-discovery-ops

HDHomeRun Discovery Operations

Locates HDHomeRun tuner devices per https://info.hdhomerun.com/info/discovery_api — local UDP broadcast (port 65001) and the SiliconDust cloud discovery HTTP endpoint.

When to use

• You don't know a device's current IP (first-time setup, DHCP re-lease).
• Local broadcast discovery fails (client on a different VLAN/subnet from the tuner) and you need the cloud fallback.
• You want to refresh the on-disk discovery cache before a doctor run.

When NOT to use

• You already have a working device URL → go directly to hdhr-http-api-ops or hdhr-tuner-control.
• Discovering a DVR record engine (separate software/hardware, its own discover.json) → that's documented under hdhr-dvr-ops, not here.

Prerequisites & environment

Connect via the mcp-client skill against the hdhomerun-mcp MCP server. No credentials are required for discovery.

Variable	Required	Notes
DISCOVERYTOOL	optional	Toggle this tool domain (default enabled)

Tools & actions

Condensed tool	Actions
discovery_operations	broadcast, targeted, cloud, cache

Key parameters

• broadcast: {"timeout": 2.0, "device_id": <int, optional wildcard match>}.
• targeted: {"ip": "<known ip>", "timeout": 2.0} — sends the same UDP discover packet directly to a known address (works across VLANs where broadcast doesn't).
• cloud: {"device_id": "<hex DeviceID, optional>"} — omit to list every device SiliconDust has ever seen register from this account/network.
• cache: {} — reads the last cached discovery result (used by hdhr-doctor's freshness check) without hitting the network.

Recipes (params_json)

Broadcast discovery on the local subnet:

{"action": "broadcast", "params_json": "{\"timeout\": 2.0}"}

Rediscover a device you know the (possibly stale) IP for:

{"action": "targeted", "params_json": "{\"ip\": \"10.0.132.114\"}"}

Cloud discovery by DeviceID (works across VLANs, no broadcast needed):

{"action": "cloud", "params_json": "{\"device_id\": \"10ACFCDE\"}"}