# \[APP\]\[PRO\] Danfoss Icon

**URL:** https://community.homey.app/t/app-pro-danfoss-icon/92122
**Category:** Apps
**Tags:** app, zigbee, homey-pro
**Created:** [October 18, 2023, 7:42am UTC](https://community.homey.app/t/app-pro-danfoss-icon/92122 "2023-10-18T07:42:47Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![nckrtl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nckrtl/32/88999_2.png) [@nckrtl](https://community.homey.app/u/nckrtl)
#### Post date: [October 19, 2023, 7:31am UTC](https://community.homey.app/t/app-pro-danfoss-icon/92122/3 "2023-10-19T07:31:57Z")

</div>

**Status update**  
I’m currently stuck at supporting a dynamic amount of thermostats, I explained it here [here](https://community.homey.app/t/can-you-create-sub-devices-programmatically-or-conditionally/92150). Meaning I would need to create separate apps for people that have 1 thermostat, another app if you have 2 thermostats etc. This is not a viable option.

I contacted Homey to see if there is a solution. One of the following things would help me continue developing this app:

- Allow to select devices from a list before pairing/after Zigbee pairing
- Allow to define a condition in the driver manifest whether a device should be added or not
- Allow to delete/remove/destroy sub devices in device.js upon initializing (due to access to zlcNode)
- Allow to delete a sub device in the Homey without deleting all other related sub devices

---

_[View the full topic](https://community.homey.app/t/app-pro-danfoss-icon/92122)._