# ZWave Timeout with Homey Pro **URL:** \ **Category:** Questions & Help\ **Created:** [December 9, 2021, 4:09am UTC](https://community.homey.app/t/zwave-timeout-with-homey-pro/56252 "2021-12-09T04:09:16Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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 9, 2021, 7:22am UTC](https://community.homey.app/t/zwave-timeout-with-homey-pro/56252/4 "2021-12-09T07:22:23Z")
If the switches were added secure, worst of all s0 security, you could try adding them unsecure. That helped out a lot of people, including me. You can check this here: [https://tools.developer.homey.app/tools/zwave](https://tools.developer.homey.app/tools/zwave), where secure(x) means unsecure. You can only change security during pairing. If the device asks for a pin, entering 00000 will add it unsecure. For devices that do not ask a pin, you will need: > [@\[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-timeout-with-homey-pro/56252)._