# \[APP\]\[Pro\] UnZ-Cure (add z-wave devices unsecure) **URL:** \ **Category:** Apps\ **Tags:** app, z-wave, tools, devices, homey-pro\ **Created:** [November 28, 2021, 11:38am UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597 "2021-11-28T11:38:45Z")\ **Posts on this page:** 20\ **Page:** 2
**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:** [April 19, 2022, 12:17pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/21 "2022-04-19T12:17:35Z")
Some time ago I suffered the expected rejection from the official Homey App Store on the grounds that unsecure Z-wave adding is already possible with the 00000 pin (which doesn’t help if a pin is not required), combined with the statement “if there are issues with unsecure adding, we should contact support” (Please do, and good luck with that 😉 ). The upside is, now the app will get pretty pictures and icons in the Community app store soon. 🙂 I also tested UnZ-cure against the 7.4.0 firmware, but no changes were needed. So unless you really like the new app icon there’s not much need to update. ---
**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\ **Post date:** [April 19, 2022, 12:33pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/22 "2022-04-19T12:33:29Z")
I now only register my devices via your app ! Very good work ! ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [October 15, 2022, 7:50pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/23 "2022-10-15T19:50:15Z")
I have added a Z-wave dimmer through your app and it seems to work fine, at least today. But in Homey, the device still says it’s secure. Does it mean it was not added unsecure? ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/4/7435e07ba5649a156cf7952e229325286618f583.png) ---
**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\ **Post date:** [October 15, 2022, 7:55pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/24 "2022-10-15T19:55:13Z")
Secure = secure Secure (x) = unsecure. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [October 15, 2022, 7:57pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/25 "2022-10-15T19:57:50Z")
I think it would be secure(✓) for secure devices. Or this way for S2 devices: ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/4/14966066e35fbbb116389ddf5204bd73f4dfdfaf.png) Remembers me to re-add this one device with UnZ-Cure, too 🙂 ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [October 15, 2022, 8:11pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/26 "2022-10-15T20:11:24Z")
I have 2 dimmers. The top is added through the Namron app directly, the one at the bottom through this app. Both has the Secure (x). ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/2/22e7e9285183fde31950ca269d1e909612cb44ec.png) ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [October 15, 2022, 8:12pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/27 "2022-10-15T20:12:41Z")
Then these devices are added unsecure by the app. Perhaps the devices don’t support secure mode. ---
**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:** [October 15, 2022, 8:43pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/28 "2022-10-15T20:43:07Z")
> [@RonnyW](#): > > secure(✓) for secure devices. The different options are: Unsecure: - Secure (x) Secure: - Secure (S0) - Secure (S2 (Unauthenticated)) (no 5# DSK code) - Secure (S2 (Authenticated)) (with 5# DSK code) ---
**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:** [October 15, 2022, 9:37pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/29 "2022-10-15T21:37:47Z")
There are multiple reasons Homey will add Z-Wave devices unsecure since firmware V7: 1. The device does not support secure 2. The device only supports S0 security (Homey no longers adds this secure by default) 3. The device asked for a pin and you entered 00000 4. Adding it though UnZ-Cure, which instructs Homey to ignore S2 And as stated above, Homey shows unsecure as Secure (x), which is confusing to say the least. For some x means no, for other it is meant as a checkmark. ---
**Author:** ![Eibo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eibo/32/16812_2.png) [@Eibo](https://community.homey.app/u/Eibo)\ **Post date:** [January 9, 2023, 10:54pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/30 "2023-01-09T22:54:51Z")
I have a Sunricher SR-ZV9101FA-CCT (Producer ID: 816, ProductType ID: 512, Product ID: 53250) I have both the Namron app and the Sunricher/Homey\_EasyLighting app installed. I prefere to use the EasyLighting app, but when associated through UnZ-Cure it chooses Namron 4512743 Z-Wave LED Controller. Can I force UnZ-Cure in any way to prefere the Homey\_EasyLighting app? ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [January 10, 2023, 12:39am UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/31 "2023-01-10T00:39:52Z")
You can temporarely disable the App that you don’t want to be used, during the include process. ---
**Author:** ![Eibo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eibo/32/16812_2.png) [@Eibo](https://community.homey.app/u/Eibo)\ **Post date:** [January 10, 2023, 1:01am UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/32 "2023-01-10T01:01:02Z")
Thanks. That worked. Yeah, I feel a little embarrassed now 😉 ---
**Author:** ![matrover](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matrover/32/12112_2.png) [@matrover](https://community.homey.app/u/matrover)\ **Post date:** [March 26, 2023, 11:47am UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/33 "2023-03-26T11:47:22Z")
Hi @Edwin_D Are you planning to make this app compatible with the Homey pro 2023? The app installs but its not showing up in the add device page. ---
**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:** [March 26, 2023, 12:33pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/34 "2023-03-26T12:33:27Z")
Sorry to hear all is not well for Homey Pro, it was built with SDK3 so it should have worked out of the box. Unfortunately I no longer own a working Homey at all that enables me to test, ~~so I transferred the ownership of the app to TedTolboom. Hopefully he can shed some light~~ EDIT - oops, that was another app, not this one. ---
**Author:** ![TedTolboom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tedtolboom/32/12081_2.png) [@TedTolboom](https://community.homey.app/u/TedTolboom)\ **Post date:** [March 26, 2023, 4:48pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/35 "2023-03-26T16:48:00Z")
> [@Edwin\_D](#): > > Unfortunately I no longer own a working Homey at all that enables me to test, so I transferred the ownership of the app to @TedTolboom. Hopefully he can shed some light. You didn’t transfer this particular app… 🤨 ---
**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:** [March 26, 2023, 5:56pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/36 "2023-03-26T17:56:37Z")
Oops, didn’t look which app it was… Assumptions… There’s nothing to transfer either as the app never got approved. But the problem remains I cannot do anything anymore, I do not own a Homey anymore, let alone a Homey Pro 2023. My code is public, the only thing it does is add a property to a fake z-wave device. I used the wizard to create a base implementation and set the property. Nothing more, nothing less. My guess is Homey now figures that the fake z-wave device is missing some required implementation. Repeating the process may fix it, but Unfortunately I cannot. The code is linked in the top post, the property I added is: > “security”: [“none”] Maybe some-one else owning a Pro 2023 can try it, or add the property to any other real z-wave device that does not implement security, thereby effectively creating a new “Walli”. Who knows, if the device is real, it might even get through the approval process as long as you don’t tell why it was changed 🙂 ---
**Author:** ![matrover](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matrover/32/12112_2.png) [@matrover](https://community.homey.app/u/matrover)\ **Post date:** [March 27, 2023, 8:06pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/37 "2023-03-27T20:06:58Z")
Hmm 🤨 i tried to add the property to another app that is running ok on the new homey and every time i install the app the lines get deleted… ?! ---
**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:** [March 27, 2023, 8:19pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/38 "2023-03-27T20:19:10Z")
you are probably editing `app.json` directly, but you (most likely) need to edit the composing file that needs editing as it composes (merges) into the app.json: `/drivers/[DRIVER ID]/driver.compose.json` ---
**Author:** ![matrover](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matrover/32/12112_2.png) [@matrover](https://community.homey.app/u/matrover)\ **Post date:** [March 27, 2023, 8:22pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/39 "2023-03-27T20:22:56Z")
Yes! that did the trick, i can indeed add unsecure devices this way 😃 Thanks both @Caseda & @Edwin_D ---
**Author:** ![Stanga](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stanga/32/79116_2.png) [@Stanga](https://community.homey.app/u/Stanga)\ **Post date:** [September 25, 2023, 8:01pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/40 "2023-09-25T20:01:54Z")
Will this app be available for HP23? 🙂 [Previous page](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597.md?page=1) [Next page](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597.md?page=3)