# Add Z-Wave device non-secure? **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave\ **Created:** [April 28, 2019, 8:04pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406 "2019-04-28T20:04:18Z")\ **Posts on this page:** 12\ **Page:** 3
**Author:** ![Jo\_San](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jo_san/32/3732_2.png) [@Jo\_San](https://community.homey.app/u/Jo_San)\ **Post date:** [February 7, 2021, 12:31pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/44 "2021-02-07T12:31:31Z")
No need for adapted app. Just uninstall your (Fibaro) device and then re-add as a Walli Switch. It automatically changes to the correct device, but then insecure. ---
**Author:** ![Tiwas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tiwas/32/10066_2.png) [@Tiwas](https://community.homey.app/u/Tiwas)\ **Post date:** [February 7, 2021, 12:58pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/45 "2021-02-07T12:58:51Z")
I tried this with one of my qubino devices today, but it seems it doesn’t work for those. Either the new beta version of homey isn’t fooled by it or the qubino doesn’t function as non-secure. ---
**Author:** ![Klim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/klim/32/26121_2.png) [@Klim](https://community.homey.app/u/Klim)\ **Post date:** [March 14, 2021, 10:17am UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/46 "2021-03-14T10:17:40Z")
This method still works even on 5.0.1 FW. It’s works with ALL z-wave devices. You doing something wrong. ---
**Author:** ![HengDykk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hengdykk/32/14893_2.png) [@HengDykk](https://community.homey.app/u/HengDykk)\ **Post date:** [May 23, 2021, 8:38pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/47 "2021-05-23T20:38:50Z")
Just wanted to add that this worked for me too today. After doing some last migrations from Fibaro HC2 to Homey, i had some associations issues. After the workaround, Dimmer 2 was added un-secure and associations worked as they should. My case was with Fibaro Dimmer 2 and [Zwave.me](http://Zwave.me) Wall-C (ZME\_WALLC-S) Fibaro app v.3.0.14 [Z-Wave.Me](http://Z-Wave.Me) v.0.4.2 Homey v.6.1.0 ---
**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\ **Post date:** [June 28, 2021, 9:11pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/49 "2021-06-28T21:11:09Z")
Unfortunately the “add as Walli” trick no longer works with V7 firmware. Does anyone know of a device that adds the proper flag to disable S2 security? ---
**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:** [June 29, 2021, 7:31am UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/50 "2021-06-29T07:31:10Z")
If I understand it correctly, it‘s only possible with Authenticated S2 devices when you enter the pin 00000 instead of the original pin. I didn’t tried it myself yet. ---
**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\ **Post date:** [June 29, 2021, 3:27pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/51 "2021-06-29T15:27:48Z")
I wasn’t asked for a pin: the pairing process on the outside was exactly the same as before and the developer page shows S2 (unauthenticated). ---
**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:** [June 29, 2021, 3:41pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/52 "2021-06-29T15:41:15Z")
This was an information from @Caseda on Slack: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/3/730381e199a248312b2848f3f5c841563099886c.jpeg) ---
**Author:** ![Ryvaenge](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ryvaenge/32/13197_2.png) [@Ryvaenge](https://community.homey.app/u/Ryvaenge)\ **Post date:** [August 1, 2021, 11:07pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/53 "2021-08-01T23:07:36Z")
Crisis as my whole network is unsecure due to use of associations… Apps have been totally rewritten I noticed before they all seemed to diasppear from Github. Includesecure=false isn`t working with CLI installed apps either. Can confirm that devices that ask for DSK, you can just enter 00000 (at least tested on one device) ---
**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\ **Post date:** [August 1, 2021, 11:10pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/54 "2021-08-01T23:10:51Z")
I put in a feature request for [[REQUEST] User selectable Z-wave security levels in order for associations to work](https://community.homey.app/t/request-user-selectable-z-wave-security-levels-in-order-for-associations-to-work/49925), hopefully if more people like it Athom will take notice. Any attempts I tried to create Walli like workaround have failed so far. Seems there is no flag to prevent S2 security for newly paired devices. ---
**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\ **Post date:** [December 4, 2021, 12:31pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/55 "2021-12-04T12:31:54Z")
For devices that ask a pin, enter 00000 for unsecure. For devices that do not: there is now a new solution: > [@\[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 … ---
**Author:** ![Jose\_Sally](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jose_sally/32/47942_2.png) [@Jose\_Sally](https://community.homey.app/u/Jose_Sally)\ **Post date:** [April 20, 2022, 8:06pm UTC](https://community.homey.app/t/add-z-wave-device-non-secure/12406/56 "2022-04-20T20:06:58Z")
I have a Homey controlled by Google Home and especially controlling grouped devices are causing problems where I have to retry on/off commands several times.[.](https://get-vidmate.com/vidmate-2019/) [.](https://instasave.onl/) [Previous page](https://community.homey.app/t/add-z-wave-device-non-secure/12406.md?page=2)