# Adding back change flow triggers on internal capabilities

**URL:** <https://community.homey.app/t/adding-back-change-flow-triggers-on-internal-capabilities/75688>\
**Category:** Developers\
**Created:** [January 28, 2023, 10:55am UTC](https://community.homey.app/t/adding-back-change-flow-triggers-on-internal-capabilities/75688 "2023-01-28T10:55:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Edwin\_Biemond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_biemond/32/72686_2.png) [@Edwin\_Biemond](https://community.homey.app/u/Edwin_Biemond)\
**Post date:** [January 28, 2023, 10:55am UTC](https://community.homey.app/t/adding-back-change-flow-triggers-on-internal-capabilities/75688/1 "2023-01-28T10:55:40Z")

</div>

I like to use the internal default capabilities like measure\_power and it sub ones like measure\_power.export etc on my smpl display, that is not so hard if I only add measure\_power to capabilities on my sdk 3 app. then power ,export are showing up on smpl.

But this has a downside and now measure\_power change triggers are gone.

If there an easy way to have both or besides adding cap , should I also add these flow trigger definitions to the device flow json.

thanks

---

<div class="post-metadata">

**Author:** ![Edwin\_Biemond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_biemond/32/72686_2.png) [@Edwin\_Biemond](https://community.homey.app/u/Edwin_Biemond)\
**Post date:** [January 28, 2023, 11:44am UTC](https://community.homey.app/t/adding-back-change-flow-triggers-on-internal-capabilities/75688/2 "2023-01-28T11:44:06Z")

</div>

Also is there a good way to check all the real flow triggers you have on the app (with the real names, not translated). To see if I broke something.  
I see it on the app store and while creating a flow but not on homey app validate etc.

---

<div class="post-metadata">

**Author:** ![Edwin\_Biemond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_biemond/32/72686_2.png) [@Edwin\_Biemond](https://community.homey.app/u/Edwin_Biemond)\
**Post date:** [January 28, 2023, 6:17pm UTC](https://community.homey.app/t/adding-back-change-flow-triggers-on-internal-capabilities/75688/3 "2023-01-28T18:17:28Z")

</div>

it seems besides the default caps I can also add matching change triggers , I used this as reference for caps and the trigger [Tutorial: Device Capabilities - Homey Apps SDK v3](https://apps-sdk-v3.developer.homey.app/tutorial-device-capabilities.html)

---

<div class="post-metadata">

**Author:** ![Edwin\_Biemond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_biemond/32/72686_2.png) [@Edwin\_Biemond](https://community.homey.app/u/Edwin_Biemond)\
**Post date:** [January 28, 2023, 7:26pm UTC](https://community.homey.app/t/adding-back-change-flow-triggers-on-internal-capabilities/75688/4 "2023-01-28T19:26:11Z")

</div>

now I like to pre define subcapabilities in homey compose like measure\_power.import etc. so smpl can see them also.

weird thing is with meter\_power I see all the sub ones on smpl but not for measure\_power.
