# Save a register of devices configuration

**URL:** <https://community.homey.app/t/save-a-register-of-devices-configuration/657>\
**Category:** Devices\
**Created:** [August 27, 2018, 11:51am UTC](https://community.homey.app/t/save-a-register-of-devices-configuration/657 "2018-08-27T11:51:00Z")\
**Posts on this page:** 1\
**Showing post:** 12

<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 31, 2018, 9:14pm UTC](https://community.homey.app/t/save-a-register-of-devices-configuration/657/12 "2018-08-31T21:14:46Z")

</div>

If you change the driver yourself, sure.  
I’m not gonna do it for the general driver, as within homey and zwave devices currently I would need to add every possible contact/alarm type to make all people happy.  
For zwave devices there is just no way to choose during pairing unless it’s a socket type, which is a default homey thing, not app related.  
That’s about 12 capabilities (times 2), so not going to happen.

Easier is to create 2 [virtual devices](https://apps.athom.com/app/com.arjankranenburg.virtual), each for every input, and couple them together with flows.

---

_[View the full topic](https://community.homey.app/t/save-a-register-of-devices-configuration/657)._