# Room shows as "active" even after motion alarms turns off **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave, homey-pro-2023\ **Created:** [September 9, 2024, 1:50am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730 "2024-09-09T01:50:57Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Giovanni\_Dienstmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni_dienstmann/32/112852_2.png) [@Giovanni\_Dienstmann](https://community.homey.app/u/Giovanni_Dienstmann)\ **Post date:** [September 9, 2024, 1:50am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/1 "2024-09-09T01:50:57Z")
I use Aeotec Trisensor motion sensors all over my house (Z-Wave device), with Homey Pro 2023. Many times it’s happening for me that a motion sensor is turned off, and yet that area of the house is still marked as “Active” in the Homey system for minutes—sometimes for hours. This breaks some of my Flows that depend on an area being “inactive for X minutes” to turn off lights. Any idea how to fix this? ---
**Author:** ![Rmb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rmb/32/79135_2.png) [@Rmb](https://community.homey.app/u/Rmb)\ **Post date:** [September 9, 2024, 4:43am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/2 "2024-09-09T04:43:06Z")
Did you try to refresh the screen by switching to another tab (ie flows) and back to devices? I know did doesn’t change the state of the flow, but then you know for sure that you will not be misled. ---
**Author:** ![Giovanni\_Dienstmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni_dienstmann/32/112852_2.png) [@Giovanni\_Dienstmann](https://community.homey.app/u/Giovanni_Dienstmann)\ **Post date:** [September 9, 2024, 9:47am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/3 "2024-09-09T09:47:14Z")
Yes. I tried killing the app and restarting it. It stays stuck in that state sometimes for days. ---
**Author:** ![Rmb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rmb/32/79135_2.png) [@Rmb](https://community.homey.app/u/Rmb)\ **Post date:** [September 9, 2024, 10:52am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/4 "2024-09-09T10:52:51Z")
Then you have to do some testing to find the cause. Maybe it is some device being in alarm state all the time, or a bug. Start by moving all alarm devices moving to another temporary zone. ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [September 9, 2024, 11:21am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/5 "2024-09-09T11:21:13Z")
All device that can set the zone as active should have a setting to exclude it: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/8/d8545b220ffa1d3b1ce5b5609dfdeb19b403191b.png) So make sure there aren’t any devices that have the option set to Yes that shouldn’t be used in the zone active check. ---
**Author:** ![Giovanni\_Dienstmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni_dienstmann/32/112852_2.png) [@Giovanni\_Dienstmann](https://community.homey.app/u/Giovanni_Dienstmann)\ **Post date:** [September 9, 2024, 10:48pm UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/6 "2024-09-09T22:48:43Z")
I can try this. In that case, I’ll have to turn on the lights based on motion triggered event, rather than Zone Active. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [September 9, 2024, 11:44pm UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/7 "2024-09-09T23:44:52Z")
It’s easy to find the device which keeps the zone active. Go to the Devices tab, hit Activity, select an active zone and you should notice the active device. Adrian tried to explain you can decide at this point to exclude the device from triggering zone activity. Or, maybe you’ll discover a device is active for longer time somehow, while it shouldn’t, and needs to be fixed. ---
**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:** [September 10, 2024, 12:44pm UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/8 "2024-09-10T12:44:15Z")
Because you wrote in another topic that you also use Aeotec Door and Window Sensor, I guess that one of these sensors is responsible for your Flow not working the way you want it to. Copied a post regarding _ **Zone Activity** _ here as info: > Acc. the [Using Zone Activity](https://support.homey.app/hc/en-us/articles/360026209853-Using-Zone-Activity) support article, _ **Zone Activation** _ can be used with motion and door/contact sensors only: > > ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/e/4ef891eb5d4078d5daba4e256070f70568a6c186.png) > > The [Homey SDK documentation](https://apps.developer.homey.app/the-basics/devices/capabilities#zone-activity-capability-options) also states that only devices with the `alarm_motion` and `alarm_contact` capabilities can be used for the Zone Activity option: > > ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/d/fd5ad243871a7d8d59552d7a46ea06f2938ee4cc.png) ([Source](https://community.homey.app/t/zone-activity-doesnt-work-with-zooz-tilt-sensor-zse43/115444/4)) ---
**Author:** ![Giovanni\_Dienstmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/giovanni_dienstmann/32/112852_2.png) [@Giovanni\_Dienstmann](https://community.homey.app/u/Giovanni_Dienstmann)\ **Post date:** [September 11, 2024, 4:45am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/9 "2024-09-11T04:45:36Z")
Hi @DirkG, Yes, I’m aware that both door/window sensors and motion sensor mark a zone as active. In the bug I’m experiencing, there is no particular door/window sensor in that zone at all, just a motion sensor. It keeps the zone as active for several hours. I would imagine this is a defect with the Aeotec motion sensor itself? ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 11, 2024, 5:33am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/10 "2024-09-11T05:33:55Z")
> [@Giovanni\_Dienstmann](#): > > I would imagine this is a defect with the Aeotec motion sensor itself? That’s easy enough to check: find the motion sensor device in Homey and see what it’s state is. If it says “motion detected” when it shouldn’t have, there’s an issue with the sensor (or with Homey not receiving or passing the “no more motion” event back to the app). ---
**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:** [September 11, 2024, 9:15am UTC](https://community.homey.app/t/room-shows-as-active-even-after-motion-alarms-turns-off/115730/11 "2024-09-11T09:15:45Z")
As @robertklep already mentioned, it’s really easy to check if there is a misbehavior with the motion sensor. But because you had trouble with some Z-Wave devices that lost the connection to the HP23, this could of course also be a reason for this. Because now you know how to check if the motion sensor is still reachable in the Z-Wave network, I suggest to check this.