Control a Tailwind iQ3 garage door controller over its local HTTP API
domain: gotailwind.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable Local Control in the Tailwind app and retrieve the device's 6-digit Local Control Key.
Discover the device on your LAN via mDNS/Bonjour — it advertises as tailwind-<id>.local.
Send an HTTP request to the device's /json endpoint with the Local Control Key as a TOKEN header to read device info (model ID, firmware version) and current status.
Send a JSON command payload to the same /json endpoint to open/close a configured door output or toggle an attached Tailwind light controller.
Track the community-maintained spec repo (Scott--R/Tailwind_Local_Control_API) for payload changes, since Tailwind still labels local control as beta.
Known gotchas
Tailwind explicitly labels local network control as beta with evolving security — don't assume long-term endpoint stability.
The Local Control Key is separate from any cloud/account credentials; losing it requires re-pairing in the app to regenerate.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?