# 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:** 23

<div class="post-metadata">

**Author:** ![epkulse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/epkulse/32/9694_2.png) [@epkulse](https://community.homey.app/u/epkulse)\
**Post date:** [May 4, 2019, 3:38pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/23 "2019-05-04T15:38:12Z")

</div>

I have 3 Fibaro FGMS001 Motion sensors that were working “somewhat” when connected to my Vera Plus. As I now have moved to Homey 2.0, they have become completely unreliable… I am now testing Xiaomi Aqara Motion sensors and that appear to be more reliable…  
Seems like Fibaro is the source of the problem, even though the controller implementation on Vera was somewhat better…

---

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