# Custom Capability does not show up as a possible action in a flows

**URL:** <https://community.homey.app/t/custom-capability-does-not-show-up-as-a-possible-action-in-a-flows/41472>\
**Category:** Questions & Help\
**Created:** [January 20, 2021, 9:21am UTC](https://community.homey.app/t/custom-capability-does-not-show-up-as-a-possible-action-in-a-flows/41472 "2021-01-20T09:21:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Peters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chris_peters/32/1851_2.png) [@Chris\_Peters](https://community.homey.app/u/Chris_Peters)\
**Post date:** [January 20, 2021, 9:21am UTC](https://community.homey.app/t/custom-capability-does-not-show-up-as-a-possible-action-in-a-flows/41472/1 "2021-01-20T09:21:16Z")

</div>

I’m building a heating controller for a ESP8266 based room thermostat and wallheating controller which I have build. I’m using Homeyduino for the communication between Homey and the device. Because each controller can manage the temperature in multiple rooms, I originally planned to use sub capabilities. That does not realy work on Homeyduino however. So in the end I decided to create sub cababilities for things like measure\_temperature an target\_temperature. The capabilities do shwo up in the the Homey app, and I can change them etc. The problem is that they are not available in flows. I have off course read all documentation that Homey provides, but that is really quite limited, so any help would be appreciated.

So far I have defined te capabilities in app.json under capabilities

```
"capabilities": {
"thermostat_mode_0": {
  "type": "enum",
  "title": {
    "en": "Thermostat mode 0",
    "nl": "Thermostaat modus 0",
    "de": "Thermostat-Modus 0",
    "fr": "Mode thermostat 0"
  },
  "desc": {
    "en": "Mode of the thermostat",
    "nl": "Modus van de thermostaat",
    "de": "Modus des Thermostates",
    "fr": "Mode du thermostat"
  },
  "values": [
    {
      "id": "0",
      "title": {
        "en": "Active",
        "nl": "Aktief",
        "de": "Aktive",
        "fr": "Active"
      }
    },
    {
      "id": "1",
      "title": {
        "en": "Inactive",
        "nl": "Niet Aktive",
        "de": "Nicht Aktive",
        "fr": "Inactive"
      }
    },
    {
      "id": "2",
      "title": {
        "en": "Away",
        "nl": "Niet Aanwezig",
        "de": "Abwesend",
        "fr": "Ne pas la :-)"
      }
    }
  ],
  "getable": true,
  "setable": true,
  "uiComponent": "picker"
},

```

I have also added the new capabilities to the drriver capabilties in app.json

```
  "drivers": [
{
 ...
  "capabilities": [
    "thermostat_mode_0", "thermostat_mode_1", "thermostat_mode_2", 
    "measure_temperature_0", "measure_temperature_1", "measure_temperature_2",
    "target_temperature_0", "target_temperature_1", "target_temperature_2"
  ],

```

I has expected that that would be enough and that homey would automatiucally created flow cards for these capabilutes, what am I missing?

---

<div class="post-metadata">

**Author:** ![Shakesbeard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/shakesbeard/32/15112_2.png) [@Shakesbeard](https://community.homey.app/u/Shakesbeard)\
**Post date:** [January 20, 2021, 10:10am UTC](https://community.homey.app/t/custom-capability-does-not-show-up-as-a-possible-action-in-a-flows/41472/2 "2021-01-20T10:10:12Z")

</div>

Flowcards are created automatically only for the standard capabilities.  
For custom capabilities you need to define the flowcards yourself.