# ZWave Route **URL:** \ **Category:** Questions & Help\ **Created:** [January 27, 2021, 8:46am UTC](https://community.homey.app/t/zwave-route/41856 "2021-01-27T08:46:11Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [February 2, 2021, 6:00pm UTC](https://community.homey.app/t/zwave-route/41856/12 "2021-02-02T18:00:51Z")
Instead of selecting the exact device in the inclusion process, use a Fibaro device from the Walli series, e.g. Walli Switch. I have heard that this also works with all Qubino devices, but I have not tried it myself yet. Don’t worry, based on different IDs (manufacturer, device type, device) the device will still be included correctly. **EDIT** After release of Homey firmware v7.x the “Walli method” for including devices unsecure doesn’t work anymore. Please follow this thread: > [@\[APP\]\[Pro\] UnZ-Cure (add z-wave devices unsecure)](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597): > > Add Z-wave devices unsecure Z-wave associations are a very important. The main reason is that if Homey isn’t working for some reason, the lights can still be controlled. As of version 7.0, Homey supports more z-wave security levels. That is great for locks and such, but not so much for z-wave associations, because associations need the same security level for both associated devices in order to work. As not all devices support the same security level, and Homey picks the security level based … --- _[View the full topic](https://community.homey.app/t/zwave-route/41856)._