# \[APP\]\[Pro\] UnZ-Cure (add z-wave devices unsecure)

**URL:** <https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597>\
**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:** 4\
**Page:** 3

<div class="post-metadata">

**Author:** ![Bart\_Duisters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bart_duisters/32/123975_2.png) [@Bart\_Duisters](https://community.homey.app/u/Bart_Duisters)\
**Post date:** [January 6, 2025, 8:22pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/45 "2025-01-06T20:22:56Z")

</div>

Is there already a solution for forcing unsecure inclusion z-wave devices for Homey Pro 2023?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 6, 2025, 9:13pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/46 "2025-01-06T21:13:00Z")

</div>

Try PIN `00000`

> ![1000040823](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/4/e413f03ddf4d454bbe91b35fa41a954dbf5de0c4.jpeg)

---

<div class="post-metadata">

**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:** [January 7, 2025, 8:22am UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/47 "2025-01-07T08:22:40Z")

</div>

> [@Peter\_Kawa](#):
>
> Try PIN `00000`

That’s correct, but…

> [@Edwin\_D](#):
>
> If you own a device that requires a pin during the pairing process, you do not need this app to pair the device unsecure. simply use 00000 as the pin. But if your device does not require a pin, this app may be of use to you.

So there are two different S2 security classes. For Z-Wave devices with **S2 Authenticated** the `00000` PIN works, but not for Z-Wave devices with **S2 Unauthenticated** , because no PIN is requested during the inclusion process.  
The only way I know to include devices with **S2 Unauthenticated** is the UnZ-Cure App.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 7, 2025, 5:46pm UTC](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597/48 "2025-01-07T17:46:17Z")

</div>

Thanks for the extended info, Dirk 🍻  
That’s what the KB article I showed said, but without any detail:

> it’s possible with _some_ z-wave devices

Athom should add your input to that KB article imho!

[Previous page](https://community.homey.app/t/app-pro-unz-cure-add-z-wave-devices-unsecure/55597.md?page=2)