Capabilities starting with measure_ will automatically try to trigger a Flow , what to define in the app.json?

Developers
1

Reading below is awesome and save some work but what do I need to define in the app.json to make this work.

Thanks Edwin

## Starting Flows for custom capabilities

Custom capabilities starting with  `alarm_` ,  `meter_`  and  `measure_`  will automatically try to trigger a Flow. You only need to define this Flow trigger in your  `/app.json` .

### Numbers

Calling  `setCapabilityValue('measure_my_number', 1)`  will try to start a Flow trigger with ID  `measure_my_number_changed` , with a [Tag](https://apps.developer.athom.com/tutorial-Flow-Tokens.html)  `value` .

### Booleans

Calling  `setCapabilityValue('alarm_my_alarm', true)`  will try to start a Flow trigger with ID  `alarm_my_alarm_true` , with a [Tag](https://apps.developer.athom.com/tutorial-Flow-Tokens.html)  `value` .
2

Moved to Developers.

3

Same goes for in the Device flow:

If your driver has a class that Homey already has support for, like light or socket , your custom card will be added to those cards. For example, if your driver supports a Light bulb that has a special disco mode, the user will see ‘Turn on’, ‘Turn off’, ‘Dim’, ‘Set color’, ‘Disco mode’.

I see the cards Turn off, on and Volume changed (I am working on a TV app) however they do not trigger the flow. The documentation could use an update with better examples in my opinion.

1 Like