Repository navigation
Use Cases
The examples below illustrate patterns enabled by Device Capabilities. They are starting points, not ready-made automations: adapt capability IDs, values, fields, and filters to the devices on your Homey.
Use the capability listener to watch a device capability that has no suitable trigger in its own app.
- Add Listen (watch) from Device for Capability.
- Select the device and capability from autocomplete.
- Use its value token in a condition or following action.
- For example, when a vacuum's
bin_fullcapability becomes true, send a notification.
User/client tokens are only available when Homey provides the origin information for that capability.
Use a zone action to set a capability on all matching devices in one room or zone.
For example, set a curtain position capability across the Home zone, optionally including subzones. Select the correct device class and capability, then choose a value that the device drivers accept. Use brand or device-type filters when only some devices should be affected.
Build an AVD with buttons for media or lighting, text fields for track/artist information, and number fields for curtain position or volume. Add Flows to:
- send commands when an AVD control changes;
- update the AVD when a real device changes;
- show a status on the tile.
The AVD forum tutorial demonstrates combining music controls, media information, multiple curtains, and TV/Xbox buttons on a single Living Room device.
For a complete walkthrough and more community-inspired examples, see AVD Examples and the individual field guides.
Use an AVD to display values that would otherwise occupy several dashboard tiles. Create an appropriate number or text field, then update it from real-device capabilities. For textual tile status, select a Text field in the Homey mobile device settings. Where the app's reflection/calculation configuration is available, aggregate multiple numeric sources (for example, mean or maximum) and format the resulting value.
The AVD's device class and selected tile field affect how Homey displays information, so test the result in the client where you plan to use it.
Use Retrieve Insight Log Value with the device, capability, and number of minutes. Pass the value and, when present, user/client tokens into a notification or log action. Use zero minutes for the most recent value.
This pattern requires the capability to have suitable Insight history. It cannot provide missing historical records.
Use App started to run setup after an integration restarts. Use the availability trigger or All devices are available condition to coordinate an operation that needs a set of devices online.
Availability is Homey's reported state. It may not prove that every device-specific command will succeed.
For integrations that report a useful error when a requested state is already reached, use Set Device.Capability to True or False and wait for error. The official forum gives a television power-on example.
Because the card retries writes while it waits for the selected error, use it only when repeated commands are safe and the expected error can be matched reliably. See Conditions.
The linked Public Announcement tutorial combines text-to-speech/media apps with speaker devices. It uses Device Capabilities in an example involving a TV capability monitor so playback starts after the TV is ready. The tutorial is an integration example; its other apps and device setup are separate requirements.
Support development - If Device Capabilities is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!