# Fibaro Motion Sensor does not report/stuck **URL:** \ **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:** 20\ **Page:** 3
**Author:** ![Maikel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maikel/32/12410_2.png) [@Maikel](https://community.homey.app/u/Maikel)\ **Post date:** [May 6, 2020, 9:14pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/41 "2020-05-06T21:14:29Z")
This issue keeps bugging me. Now the lights were on again because of this sensor. According to the app (and developer site) the sensor was last triggered 4 hours ago, but the current movement status is still ‘true’, even though nobody was around for the past 2,5 hours. This keeps the zone marked ‘active’ and therefore doesn’t turn of the lights. I’m thinking of replacing the Fibaro with the Xiaomi sensor, but I hope it can be fixed otherwise. ---
**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:** [May 7, 2020, 6:54am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/42 "2020-05-07T06:54:50Z")
If you have found a solution, I would be very interested in. I could not detect the problem with the Fibaro HC2. In combination with Homey both the Fibaro MotionSensors and the Aeotec 4in1 sensor get stuck from time to time. Therefore I assume that it is due to Homey and not a special Fibaro MotionSensor problem. Have you already tried NEO Coolcam? I don’t have any other Zigbee devices in use, so Xiaomi is not really an option for me. I also don’t find the sensors visually appealing. We all can contact Athom ([support@athom.com](mailto:support@athom.com)) and see what they have to say about it. ---
**Author:** ![Maikel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maikel/32/12410_2.png) [@Maikel](https://community.homey.app/u/Maikel)\ **Post date:** [May 7, 2020, 6:59am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/43 "2020-05-07T06:59:06Z")
The sensor has been working fine for years in the past, so Homey should be able to handle it well. Not sure what changed though. I don’t have a NEO Coolcam, so I didn’t try it. Don’t having any other Zigbee devices shouldn’t matter, right? Unless the distance between the sensor and Homey is too much. I do like the looks of the Fibaro more as well, but on the other hand the Xiaomi is very small. ---
**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:** [May 7, 2020, 7:24am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/44 "2020-05-07T07:24:47Z")
I am not a Zigbee expert, I just know that Zigbee also builds up a mesh to route. So you just have to try it out. ---
**Author:** ![Maikel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maikel/32/12410_2.png) [@Maikel](https://community.homey.app/u/Maikel)\ **Post date:** [May 7, 2020, 7:30am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/45 "2020-05-07T07:30:23Z")
I was wondering what you meant when you said that Xiapmi is not an option, because you don’t have any other Zigbee devices. I myself have tried it out and it worked just fine. Even with just one sensor. It does build a mesh network, but that also works with just one sensor and Homey. ---
**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, 7:40am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/46 "2020-05-07T07:40:23Z")
I started to switch all my z-Wave Devices from Secure to unsecure. The delays I had before are gone. Overall the Z-Wave is more reliable. ---
**Author:** ![Shakesbeard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/shakesbeard/32/15112_2.png) [@Shakesbeard](https://community.homey.app/u/Shakesbeard)\ **Post date:** [May 7, 2020, 8:11am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/47 "2020-05-07T08:11:50Z")
Never had an issue with the Fib.Motion Sensors here. Maybe battery issue or too far away from next repeater node? ---
**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:** [May 7, 2020, 10:13am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/48 "2020-05-07T10:13:26Z")
> [@Maikel](#): > > I was wondering what you meant when you said that Xiapmi is not an option, because you don’t have any other Zigbee devices. If I only use battery powered Zigbee devices (e.g. sensors), I’m afraid that I will get some problems with reception. My remaining SmartHome components are mostly Z-Wave devices (except Philips Hue and Ikea Tradfri, both with their own bridge), so I don’t necessarily want to use another standard without repeaters. > [@Shakesbeard](#): > > Maybe battery issue or too far away from next repeater node? Not in mine case. ---
**Author:** ![Maikel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maikel/32/12410_2.png) [@Maikel](https://community.homey.app/u/Maikel)\ **Post date:** [May 7, 2020, 10:59am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/49 "2020-05-07T10:59:31Z")
> Never had an issue with the Fib.Motion Sensors here. Maybe battery issue or too far away from next repeater node? I wish my living room was that big. 🙂 The sensor is about two meters away from Homey and they have a line of sight. > I started to switch all my z-Wave Devices from Secure to unsecure. The delays I had before are gone. Overall the Z-Wave is more reliable. How can I change that? It might be worth testing. ---
**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")
> [@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 ---
**Author:** ![victoroos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/victoroos/32/8344_2.png) [@victoroos](https://community.homey.app/u/victoroos)\ **Post date:** [September 28, 2020, 2:15pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/51 "2020-09-28T14:15:28Z")
I still have this big time, it just doesn’t see me. the sensor it seems. It worked before, but after changing battery, nope ---
**Author:** ![Shakesbeard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/shakesbeard/32/15112_2.png) [@Shakesbeard](https://community.homey.app/u/Shakesbeard)\ **Post date:** [September 28, 2020, 3:42pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/52 "2020-09-28T15:42:10Z")
hmm… maybe it is broken? What you also could try is delete the device and re-add it unsecure. Might help, maybe not, no promises. ---
**Author:** ![victoroos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/victoroos/32/8344_2.png) [@victoroos](https://community.homey.app/u/victoroos)\ **Post date:** [October 5, 2020, 12:08pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/53 "2020-10-05T12:08:17Z")
I tried… seesm to have done something, will get back to you 🙂 ---
**Author:** ![solo99](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/solo99/32/30068_2.png) [@solo99](https://community.homey.app/u/solo99)\ **Post date:** [October 20, 2020, 9:17am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/54 "2020-10-20T09:17:00Z")
I got a simular issue with my motion sensors…Just moved from Vera Edge to Homey Pro, and these devices has worked perfectly on my Vera. inclusion to Homey works fine , and i got all values , like temp ,lux etc. But after a while it stops reporting temp and lux. sabotage and motion sensor seems to work and get reported into the app. i have 4 of these devices and all behaves like this. Anybody seen behaviors like this? ---
**Author:** ![Philipp\_Karl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/philipp_karl/32/12702_2.png) [@Philipp\_Karl](https://community.homey.app/u/Philipp_Karl)\ **Post date:** [November 11, 2020, 6:23am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/55 "2020-11-11T06:23:59Z")
Hello, I have 2 Fibaro Motion Sensor FGMS-001 since a few days. But I am not satisfied, motion sensor and tamper alarm freeze or do not go off. Also the movement is not sent reliably to Homey, i.e. the light does not always switch on, if I get up in the morning the motion detector does not switch at all, then the whole day quite reliable, does anyone know advice? Greetings Philipp ---
**Author:** ![Bob\_Smits](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bob_smits/32/35275_2.png) [@Bob\_Smits](https://community.homey.app/u/Bob_Smits)\ **Post date:** [February 15, 2021, 5:50pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/56 "2021-02-15T17:50:06Z")
Yes, I do have the same problem after upgrading towards 5.0.0 The fibaro motion sensor triggers the motion detection or the tamper alarm. Randomly one or two do not return to their cancellation ( so the orange exclamation mark stays active and the icon keeps on blinking. I tried several settings in parameters, removing sensors and connecting them again without result. Looks like a small bug. Bob Smits ---
**Author:** ![Ype](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ype/32/8406_2.png) [@Ype](https://community.homey.app/u/Ype)\ **Post date:** [February 15, 2021, 11:03pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/57 "2021-02-15T23:03:31Z")
Same here. Movement is stuck after update 5.0 ---
**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:** [February 16, 2021, 5:49am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/58 "2021-02-16T05:49:09Z")
Yesterday Athom released a new test version of the app. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/c/7c0326bd7e37419282d7625f68ab70c7c91cbfa1.jpeg) > **[Fibaro](https://homey.app/de-de/app/com.fibaro/Fibaro/)** > > Dein Zuhause ist dein Schloss ---
**Author:** ![tlangelaar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tlangelaar/32/10980_2.png) [@tlangelaar](https://community.homey.app/u/tlangelaar)\ **Post date:** [February 16, 2021, 6:46am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/59 "2021-02-16T06:46:49Z")
Before and after the installation yesterday of the 3.0.6 version I got a couple of tamper alerts (reported via Heimdall). This sensor never showed this behaviour before v5. I have removed the battery, triple pressed its button and set the sensitivity to 25 (was on 20). Have not received a tamper alert since (half a day). Possibly this has resolved my situation. ---
**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:** [February 16, 2021, 7:01am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/60 "2021-02-16T07:01:30Z")
Some user had to exclude and re-include the motion sensor to fix the problem. [Previous page](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851.md?page=2) [Next page](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851.md?page=4)