# Fibaro Motion Sensor does not report/stuck

**URL:** <https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851>\
**Category:** Devices\
**Tags:** z-wave\
**Created:** [February 7, 2019, 8:07am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851 "2019-02-07T08:07:47Z")\
**Posts on this page:** 1\
**Showing post:** 50

<div class="post-metadata">

**Author:** ![Osorkon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/osorkon/32/43026_2.png) [@Osorkon](https://community.homey.app/u/Osorkon)\
**Post date:** [May 7, 2020, 8:06pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/50 "2020-05-07T20:06:22Z")

</div>

> [@Maikel](#):
>
> How can I change that? It might be worth testing.

> [@Add Z-Wave device non-secure?](https://community.homey.app/t/add-z-wave-device-non-secure/12406/35):
>
> No cli installation necessary!! It works out of the box! grinning You only have to figure out which device forced already a unsecure inclusion. Thanks @TedTolboom Like the Fibaro Walli switch. By selecting the Walli switch you can include every device unsecure (as long the device support unsecure) grinning

---

_[View the full topic](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851)._