# Add Unsecure Fibaro Motion Sensor?

**URL:** <https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333>\
**Category:** Devices\
**Tags:** homey-pro\
**Created:** [November 18, 2022, 10:56am UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333 "2022-11-18T10:56:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [November 18, 2022, 10:56am UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333/1 "2022-11-18T10:56:51Z")

</div>

Hey Guys

Wonder if anyone can help ?

I want to add my Fibaro Motion sensor to the Homey Pro in unsecure mode but not sure how to do this as it adds it in secure mode - had a look arround on the forum but can’t see anthing about it

Thanks  
John

---

<div class="post-metadata">

**Author:** ![Eddy\_Poot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eddy_poot/32/9878_2.png) [@Eddy\_Poot](https://community.homey.app/u/Eddy_Poot)\
**Post date:** [November 18, 2022, 11:06am UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333/2 "2022-11-18T11:06:02Z")

</div>

When adding the sensor, do not select the option Motion sensor but select any Walli device. Homey will still add it as a motion sensor but now it will be included unsecure.

---

<div class="post-metadata">

**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:** [November 18, 2022, 11:36am UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333/3 "2022-11-18T11:36:47Z")

</div>

As far as I know Fibaro doesn’t have security S2 motion sensors, so they will include unsecure as long as your Homey Pro is on v6 or higher. (It will show `Secure (x)` in the developer tools and the device settings, which means unsecure)  
Security S0 gets included unsecure unless otherwise specified by the developer.  
If it was included before Homey Pro V6, you’ll need to reinclude it.

The way @Eddy_Poot describes is the (very) old way and doesn’t work anymore.

If it does have S2 (though I don’t think so):  
If it asks for a number during inclusion use `00000`  
If it doesn’t you’ll need an app from the community app store called “un-z-cure” (I believe it is called)

---

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [November 18, 2022, 12:57pm UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333/4 "2022-11-18T12:57:58Z")

</div>

ok thank you

I’m having problems with my Fibaro Sensor another community member said add it as unsecured that solved his problem - Had a look at the at the developer tools and all the Z Wave devices say Secure(x) I always thought they were all secure

---

<div class="post-metadata">

**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:** [November 19, 2022, 4:02pm UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333/5 "2022-11-19T16:02:11Z")

</div>

As Caseda said here above: Secure(x) is un-secure!

---

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [November 19, 2022, 4:56pm UTC](https://community.homey.app/t/add-unsecure-fibaro-motion-sensor/72333/6 "2022-11-19T16:56:57Z")

</div>

Ok thank you

Been testing the Aqara motion sensor - that is a lot faster to turn a light on than the Fibaro shame the Aqara doesn’t have a temperature gauge but if I works better for me then I can live with that
