Control a Remootio-equipped gate or garage door over the local WebSocket API
domain: remootio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the Remootio app, enable the WebSocket API on the device and note the API Secret Key, API Auth Key, and device LAN IP (this Remootio > API Settings > Advanced Settings).
Open a WebSocket connection to ws://<device-ip>:8080 (default port 8080).
Send an unencrypted AUTH frame with your Auth Key; the device replies with a challenge containing an initialActionId/initialSessionId.
Derive the AES session key from the API Secret Key and send an ENCRYPTED frame (PKCS7-padded, AES-CBC) containing a QUERY action with actionId = (lastActionId+1) % 0x7FFFFFFF to finish authenticating.
Send further ENCRYPTED frames with action "OPEN", "CLOSE", or "TRIGGER" to operate the connected gate/garage door; the device pushes a STATE_CHANGE frame with the new door state.
Known gotchas
The API must be explicitly toggled on per-device in the app before any client can connect; it is off by default.
The v2 and v3 spec versions differ (v3 adds secondary-output/trigger support) — confirm which spec version your firmware implements before parsing frames.
This is a local-network-only endpoint; remote access requires separately enabling the rate-limited cloud Device API.
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?