# Sabotage alarm fibaro na update V5.0

**URL:** <https://community.homey.app/t/sabotage-alarm-fibaro-na-update-v5-0/42766>\
**Category:** 🇳🇱 Nederlands (Dutch)\
**Tags:** z-wave\
**Created:** [February 11, 2021, 11:39am UTC](https://community.homey.app/t/sabotage-alarm-fibaro-na-update-v5-0/42766 "2021-02-11T11:39:17Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**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 18, 2021, 8:10am UTC](https://community.homey.app/t/sabotage-alarm-fibaro-na-update-v5-0/42766/8 "2021-02-18T08:10:42Z")

</div>

Sorry, alleen Engels:  
(Translated with [deep.com](http://deep.com))

> [@Fibaro Motion Sensor does not report/stuck](https://community.homey.app/t/fibaro-motion-sensor-does-not-report-stuck/8851/56):
>
> 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

---

_[View the full topic](https://community.homey.app/t/sabotage-alarm-fibaro-na-update-v5-0/42766)._