Skip to content

Flows Triggers Device availability changed

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

Device available changed

App Flowcards · Triggers index

Start a Flow when a matching device becomes available or unavailable.

Before you start

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.

Card settings

  • Available (dropdown) — Choose both changes, available, or unavailable.
  • Brand (selector) — Optionally narrow the card to one owning app or brand.
  • Devicetype (selector) — Optionally narrow the card to one device type.

Output tokens

  • Device ID (string) — The device ID reported for this event.
  • Device Name (string) — The device name reported for this event.
  • App ID (string) — The ID of the app that owns the device.
  • Device type (string) — The device type reported by Homey.
  • Available (boolean) — Whether the device is now available.
  • Unavailable Message (string) — The unavailable message, when Homey provides one.
  • Zone ID (string) — The ID of the zone that changed.
  • Zone Name (string) — The name of the zone that changed.

A token is a value produced by a Flow card. Connect it from this card to the matching input on a later card instead of copying a live value by hand.

How it works and limits

Choose Both, Available, or Unavailable. Brand and device-type filters are optional. The unavailable-message token may be blank. Homey availability does not guarantee that a command will succeed.

Example

Choose Unavailable, optionally narrow the brand or device type, and add a notification. Connect Device Name and Unavailable Message to the text. Test with a device whose availability can be safely observed.

Related

General Flow guide · Troubleshooting

Clone this wiki locally