Bridge Somfy RTS (unidirectional RF) awning motors into a smart-home ecosystem
domain: smart-home.somfy-rts-bridge-integration · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Recognize Somfy RTS is a one-way (unidirectional) RF protocol; the motor has no way to report status back, unlike Somfy's bidirectional io-homecontrol/TaHoma line
For voice-assistant or app control of RTS-only awning motors, use a third-party RF bridge (e.g., Bond Bridge) that learns the RTS remote's signal and re-broadcasts commands via Wi-Fi/cloud to Alexa/Google Home
Pair the bridge by selecting the RTS/Somfy RTS device type in the bridge's app, then hold PROG on the physical Somfy remote and confirm pairing from the app
Because RTS has no feedback, expect the smart-home dashboard to show commanded (not actual) awning position/state; build any automation with that limitation in mind
Do not conflate this RF-bridge approach with Somfy's own TaHoma ecosystem, which uses different (bidirectional) hardware and a separate integration path
Known gotchas
RTS awnings cannot report real position/state through any bridge, since the limitation is in the motor's one-way protocol, not the bridge software
Full Somfy TaHoma bridges are priced/built for bidirectional io devices and aren't the cost-effective path for a purely RTS install; a lower-cost RF bridge is the documented approach instead, with the state-feedback tradeoff noted above
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?