# 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:** 2
**Author:** ![Patrick92](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick92/32/12947_2.png) [@Patrick92](https://community.homey.app/u/Patrick92)\ **Post date:** [February 15, 2019, 7:56am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/21 "2019-02-15T07:56:37Z")
Did you also tried to ‘send node information frame’ via Homey Developers page? [http://developer.athom.com/tools/zwave](http://developer.athom.com/tools/zwave) In the left panel go to ‘Tools’ and then ‘Z-wave’. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/0/003166302910cba0fff7f91f995ea5f739bde765.png) ---
**Author:** ![Andre\_86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andre_86/32/6066_2.png) [@Andre\_86](https://community.homey.app/u/Andre_86)\ **Post date:** [February 16, 2019, 8:01am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/22 "2019-02-16T08:01:44Z")
it says ‘node information frame ok’ ---
**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")
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… ---
**Author:** ![mirius](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mirius/32/12478_2.png) [@mirius](https://community.homey.app/u/mirius)\ **Post date:** [May 25, 2019, 8:25pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/24 "2019-05-25T20:25:38Z")
Hi. I’m in the process of migrating from Smartthings to Homey Pro and I’m also experiencing the issue with the motion alarm being stuck at “Yes” for the two Fibaro Motion sensors I’ve migrated so far. These were working flawlessly with the Smartthing hub, so this is a big disappointment… Has anyone got an update from Athom on the issue? Is a downgrade to 2.1.16 the only workaround currently present? Thank you. ---
**Author:** ![McFluffy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcfluffy/32/11534_2.png) [@McFluffy](https://community.homey.app/u/McFluffy)\ **Post date:** [May 30, 2019, 6:01pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/25 "2019-05-30T18:01:34Z")
Hello, Any update on this issue? Got Fibaro Door/window sensor and motion sensor pretty much “bricked”. They report lux and temperature as they should but motion and/or tamper larm won’t update. 2 fibaro motion sensors and 3 fibaro door/window sensors are affected. All other philips lamps and devices are working as expected. ---
**Author:** ![Damon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/damon/32/8194_2.png) [@Damon](https://community.homey.app/u/Damon)\ **Post date:** [June 22, 2019, 3:14pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/26 "2019-06-22T15:14:02Z")
Have the same problem. Just Received 4 fibaro zwave plus motions sensors. Just installed 2 and they are stuck on the motion alarm. Reinstalled the app, reboots , deleting and adding them again. Nothing seems to work 😭 ---
**Author:** ![per\_82](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/per_82/32/14270_2.png) [@per\_82](https://community.homey.app/u/per_82)\ **Post date:** [August 7, 2019, 8:02pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/27 "2019-08-07T20:02:07Z")
I have this issue also. I’m on 2.5.0. Have you heard anything about a solution? ---
**Author:** ![Tangodelta](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tangodelta/32/9471_2.png) [@Tangodelta](https://community.homey.app/u/Tangodelta)\ **Post date:** [August 7, 2019, 8:53pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/28 "2019-08-07T20:53:26Z")
Get an Aeotec extender, place it within 1 meter from Homey if range issues! The Fibaro door/window sensors/magnet have to be perfectly aligned or they will show as described! ---
**Author:** ![Lars\_Faber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lars_faber/32/8118_2.png) [@Lars\_Faber](https://community.homey.app/u/Lars_Faber)\ **Post date:** [August 13, 2019, 6:51pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/29 "2019-08-13T18:51:18Z")
In the new Fibaro app version they changed the way the motion sensor is added. If you add the Motion Sonsor (zwave plus) now , it’s not added secure anymore. And i think the response from the sensor is better now. I also read on the web that adding a non secure vs secure device the response and range is better. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [August 13, 2019, 9:13pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/30 "2019-08-13T21:13:35Z")
This was a bs post, sorry ---
**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:** [August 13, 2019, 9:29pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/31 "2019-08-13T21:29:19Z")
No, that’s not correct! ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/e/e84890116db8fa3acdec511f419267171bf7b9ea.jpeg) ---
**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:** [August 13, 2019, 9:39pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/32 "2019-08-13T21:39:07Z")
you are confusing it with Aeotec devices, Fibaro has only secure inclusion unless the controller insists to not include the device secure. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [August 13, 2019, 9:44pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/33 "2019-08-13T21:44:36Z")
Ooops, you’re 100% right. My bad and my apologies for the confusion… 😊 ---
**Author:** ![Lars\_Faber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lars_faber/32/8118_2.png) [@Lars\_Faber](https://community.homey.app/u/Lars_Faber)\ **Post date:** [August 14, 2019, 3:05pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/34 "2019-08-14T15:05:04Z")
no problem 😉 So if people have problems with the motion sensor plus , try to remove and add the device again. ---
**Author:** ![Mic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mic/32/12430_2.png) [@Mic](https://community.homey.app/u/Mic)\ **Post date:** [August 28, 2019, 8:46pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/35 "2019-08-28T20:46:36Z")
Good News! Hopefully the problem with the motion sensor being stuck will soon be fixed. A friend of mine got this reply from Athom recently: We are aware of these issues and they have been fixed. Please wait until your Fibaro integration is updated to 2.1.43 (which is currently in alpha and will be released soon) and pair these devices again. We are sorry for any inconvenience this may have caused you, and want to thank you for bringing this to our attention. All the best, Best regards — Athom Support ---
**Author:** ![Alexander\_Lavin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alexander_lavin/32/12433_2.png) [@Alexander\_Lavin](https://community.homey.app/u/Alexander_Lavin)\ **Post date:** [September 14, 2019, 7:33am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/36 "2019-09-14T07:33:25Z")
Any updates on the fix? ---
**Author:** ![Christer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/christer/32/15794_2.png) [@Christer](https://community.homey.app/u/Christer)\ **Post date:** [September 28, 2019, 8:35pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/37 "2019-09-28T20:35:10Z")
Im still having the issue, with motion alarm stuck , it does not reset. All is updated to latest version. Seems like the motion sensor sends a reset signal but homey doesn’t not recieve/acknowledge? Has anyone looked at the logs? ---
**Author:** ![Mic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mic/32/12430_2.png) [@Mic](https://community.homey.app/u/Mic)\ **Post date:** [November 4, 2019, 4:02pm UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/38 "2019-11-04T16:02:16Z")
Try to exclude the sensor, and then include again. It worked for me. ---
**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:** [April 14, 2020, 9:24am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/39 "2020-04-14T09:24:27Z")
Yesterday this problem turned up again. I noticed the lights in the living room didn’t turn off and noticed the motion sensor was still triggered. After triggering the sabotage alarm, it did reset the movement alarm but then the sabotage alarm didn’t reset anymore. ---
**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:** [April 14, 2020, 9:48am UTC](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/40 "2020-04-14T09:48:41Z")
Two or three weeks ago I had the same problem every now and then, even with an Aeotec multisensor 4-in-1. By triggering the motion sensor again (just walk through the detection area) the state was resetted. Meanwhile the problem does not occur anymore. I have not made any changes. > [@Maikel](#): > > the sabotage alarm didn’t reset anymore I was only able to eliminate this problem by excluding / including. [Previous page](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851.md?page=1) [Next page](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851.md?page=3)