DocumentationExtend Gadgets
Ecosystem integrations
Connect other products through explicit capabilities, supported transports and account-owned access.
On this page
Check the transport firstChoose the integration shapeWrite a useful product guideVerify support honestlyRing 3 covers integrations with hardware and services beyond the gadget itself. The SDK's skills/ directory contains guides for product families such as lights, speakers, printers and home gateways.
Those guides are useful knowledge. They are not evidence that every listed product works through the current Impo deployment.
Check the transport first#
The Impo gateway currently does not implement /link-tunnel. A guide that relies on reaching a home-network device through that tunnel cannot run end to end on this gateway yet.
Do not work around the missing transport by handing a generated agent gateway administration credentials or unrestricted network access. A new integration needs a supported, permissioned path with explicit device and account scope.
Choose the integration shape#
| Situation | Appropriate extension |
|---|---|
| A supported cloud service | Use the server's owned connector path and the service's authorization flow. |
| A sensor or actuator attached to a gadget | Add a board or Linux command with a structured contract. |
| Another device on the local network | Implement and review the necessary transport and policy first; then add the product guide or adapter. |
| Reusable user behavior across devices | Use the proposed Ring 1 definition model once its runtime exists. |
Write a useful product guide#
Describe the supported model or firmware, required pairing and authorization, tool names, exact argument shapes and how to read results. State what is read-only and what changes the device. Include unavailable and offline behavior.
Keep credentials out of the guide. Use the platform's credential and ownership mechanisms. Treat content returned by the product as data, not as instructions that can widen the integration's permissions.
Verify support honestly#
A compatibility entry should say which path was exercised: direct local SDK use, a protocol fixture, a deployed account or physical hardware through Impo. Keep these claims separate.
Before describing an integration as supported, verify discovery, authorization, a representative operation, revocation and recovery. For devices that move, heat, lock or otherwise act physically, verify the device-specific limits and local stop behavior.
See the SDK catalog for existing guides and the gateway guide for implemented transport. Platform tool work starts with tools and instructions.