Skip to content

Templates and Exchanger

Arie J. Godschalk edited this page Nov 14, 2026 · 1 revision

Templates and The Exchanger File

TEF means The Exchanger File. Device Capabilities uses TEFs to exchange Flow definitions and Advanced Virtual Device templates between Homey users.

Choose the right community topic

The topics include other language editions; see References.

Export an AVD template

  1. Open the AVD's repair/settings screen.
  2. Choose Open Share Your Device.
  3. Select whether to include icons and associated Flows.
  4. Create the TEF.
  5. Use Post Template to open the appropriate forum topic with a prepared post.
  6. Add a clear title and short explanation, include a screenshot if useful, and paste the TEF in a preformatted code block.

The community post should explain the purpose of the AVD and identify required apps or assumptions. Never include credentials, tokens, or private account data in a template.

Export Flow templates

  1. Open The Flow Exchange(r) from the Device Capabilities app settings.
  2. Choose the export workflow and select one or more Flows.
  3. Create the TEF and choose Post Template.
  4. In the forum reply, paste the prepared description and TEF into a preformatted code block.
  5. Explain the required devices, apps, tags, and any setup the importer must perform.

Import a Flow TEF

  1. Copy the TEF from the template post.
  2. Paste it into the import area under The Flow Exchange(r) in app settings.
  3. Choose Read Flows to inspect what the file references.
  4. Replace the creator's devices, users, variables, app references, and other objects with suitable objects on your Homey, or remove references you do not need.
  5. Review the generated content before using it. The documented workflow produces a Homey API Playground script to create the Flow(s).
  6. If you are comfortable with the script and its references, open the official Homey API Playground, paste it, and run it.
  7. Verify the created Flow(s) and adjust any settings that are Homey-specific.

The import tool helps map references, but it cannot make a template's devices, apps, or logic identical to yours. A Flow that imports successfully may still need editing.

Import an AVD template

Templates can be selected while creating an AVD and through the app settings or AVD repair workflow. Review the template description, required apps, fields, and icons before applying it. If the TEF includes Flows, follow the app's generated import instructions to create those Flows as well; do not assume every template applies device configuration and Flows in one automatic step.

The discussion's AVD example demonstrates creating a multi-control "Living Room" device for media, curtains, and buttons. A separate example shows a three-room light-switch AVD connected to Flows.

Compatibility and safety

  • Templates can refer to apps that are not installed on your Homey. Install required apps or remove/replace those references.
  • The standard and HCS template topics differ in which store apps their templates may use.
  • Names and IDs in an exported Flow belong to the creator's Homey; map them to your own devices and variables.
  • Read and understand generated API Playground code before executing it.
  • Start by importing into a non-critical setup, then verify every created Flow and device.
  • Keep a backup of important Flow logic before replacing or importing shared configurations.

Related guides

Clone this wiki locally