# Pair list\_devices data transfer to my custom view **URL:** \ **Category:** Developers\ **Created:** [October 11, 2018, 10:00am UTC](https://community.homey.app/t/pair-list-devices-data-transfer-to-my-custom-view/2702 "2018-10-11T10:00:44Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\ **Post date:** [October 11, 2018, 12:01pm UTC](https://community.homey.app/t/pair-list-devices-data-transfer-to-my-custom-view/2702/2 "2018-10-11T12:01:43Z")
Already answered … > [@Pair list\_devices data to next view](https://community.homey.app/t/pair-list-devices-data-to-next-view/2276/6): > > The [device groups app](https://github.com/swttt/com.swttt.devicegroups/tree/master/drivers/devicegroup/pair) does that by emitting data in custom events from the view to the driver. For instance, the [“class” template emits an addClass event](https://github.com/swttt/com.swttt.devicegroups/blob/3e58128209e1036c5509b5ff6de5296e4addce33/drivers/devicegroup/pair/class.html#L12) that contains the device class that the new device group should get. The driver [listens to that event](https://github.com/swttt/com.swttt.devicegroups/blob/3e58128209e1036c5509b5ff6de5296e4addce33/drivers/devicegroup/driver.js#L19) and stores it in the pairingDevice object which will eventually contain all data for the new device. The next template, “capabilities”, [emits the startedCapabilities event](https://github.com/swttt/com.swttt.devicegroups/blob/3e58128209e1036c5509b5ff6de5296e4addce33/drivers/devicegroup/pair/capabilities.html#L6), and upon reception, the [driver returns the pairingDevice object](https://github.com/swttt/com.swttt.devicegroups/blob/3e58128209e1036c5509b5ff6de5296e4addce33/drivers/devicegroup/driver.js#L24) that… --- _[View the full topic](https://community.homey.app/t/pair-list-devices-data-transfer-to-my-custom-view/2702)._