Repository navigation
Flows Actions Set JSON capabilities in zone
Send a JSON value to a matching capability across a zone.
Select the exact device, app, zone, capability, or saved AVD field that the card should use. When a card changes device state, test it on a non-critical device first.
- Deviceclass (selector) — Optionally narrow the card to one Homey device class.
- Brand (selector) — Optionally narrow the card to one owning app or brand.
- Devicetype (selector) — Optionally narrow the card to one device type.
- Capability (selector) — Choose a capability offered by the selected device.
- JSON (text input) — Enter the value in the type expected by the selected capability.
- Zone (selector) — Choose a Homey zone.
- Tag (text input) — Alternatively, supply a zone ID as text or a Flow tag.
- Subzones (dropdown) — Choose whether matching subzones are included.
This card does not provide output tokens.
The app parses the input as JSON before sending it. A JSON string needs double quotes ("eco"); numbers and Booleans do not (25, true). The target integration must accept that value and structure.
For a test capability that expects an object, enter {"mode":"eco"} and run the Flow. Verify the device response; replace this sample with the exact JSON it requires.
Support development - If Device Capabilities is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!