# App for configuring scene controllers

**URL:** <https://community.homey.app/t/app-for-configuring-scene-controllers/14391>\
**Category:** Ideas & Suggestions\
**Created:** [June 13, 2019, 8:46pm UTC](https://community.homey.app/t/app-for-configuring-scene-controllers/14391 "2019-06-13T20:46:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kentok](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kentok/32/11765_2.png) [@kentok](https://community.homey.app/u/kentok)\
**Post date:** [June 13, 2019, 8:46pm UTC](https://community.homey.app/t/app-for-configuring-scene-controllers/14391/1 "2019-06-13T20:46:14Z")

</div>

Does anyone know a smart way for configuring a large number of scene controllers while minimizing the number of flows? I believe that this should be solved either in an app or with native support in Homey. Check out the details on my problem here:

> [@Creating flows for scene controllers](https://community.homey.app/t/creating-flows-for-scene-controllers/14054/9):
>
> Does anyone from the Homey team have a best practice to share on configuring a huge amount of scene controllers?

---

<div class="post-metadata">

**Author:** ![kentok](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kentok/32/11765_2.png) [@kentok](https://community.homey.app/u/kentok)\
**Post date:** [August 10, 2019, 2:32pm UTC](https://community.homey.app/t/app-for-configuring-scene-controllers/14391/2 "2019-08-10T14:32:17Z")

</div>

Any ideas on this issue?

---

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [August 10, 2019, 2:36pm UTC](https://community.homey.app/t/app-for-configuring-scene-controllers/14391/3 "2019-08-10T14:36:28Z")

</div>

Yeah. Was wondering: 1 topic for an app for scene controllers and 1 topic for flows for scene controllers both with the same purpose?

---

<div class="post-metadata">

**Author:** ![kentok](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kentok/32/11765_2.png) [@kentok](https://community.homey.app/u/kentok)\
**Post date:** [August 10, 2019, 4:11pm UTC](https://community.homey.app/t/app-for-configuring-scene-controllers/14391/4 "2019-08-10T16:11:09Z")

</div>

Potential solution: An app where I can easily map the 8 buttons on the HeatIt scene controller with 8 different flows. Then I will avoid creating 8 new flows to get this job done for every single scene controller that I have. Since I have 10+ scene controllers throughout the house, such an app would make life a lot easier!

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 10, 2019, 4:28pm UTC](https://community.homey.app/t/app-for-configuring-scene-controllers/14391/5 "2019-08-10T16:28:57Z")

</div>

It is really hard to create such an app for all devices that can be supported, pretty much all 2 (and more) buttons controllers have their own way to activate flows in the corresponding app, so there is no standard way that has been used for this.  
Without any standard, every app, no every device would need to be separately added into this app, and that are, a lot of devices already.  
Or there should be listened to **all** devices that can trigger a flow, and filter out the “wrong” ones, which is in _impossible_ job.

The only way i could think of and is reasonable, is for Athom to create such a thing in the core.  
But don’t think that will happen soon, also because it’s a mayhem to create such a GUI but still keep it user friendly.
