# Zone is not going active **URL:** \ **Category:** Devices\ **Created:** [January 7, 2023, 7:46pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725 "2023-01-07T19:46:40Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [January 7, 2023, 7:46pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/1 "2023-01-07T19:46:40Z")
Hi, I am wondering if the producer of this app has done it wrong or if it’s missing critical trigger cards. A developer of smart home products just updated their aqpp with a motion detector. I bought it, but it is not making my zone go active as my Aqara or Fibaro motion detectors do. I took a closer look to the When card and saw two things. The one is that EVA Motion Detector (which I am struggling with) miss the card “motion deactivated”. They have also another spelling for motion activity. They call it “motion detected”, but my other sensors call it “motion alarm activated”. What do Homey use to see if a zone is triggered or not? What shall I tell the developers to change so I can use this in my zones? ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/8/58505107e23cff889b8db7b49b3d4ea58baf6470.jpeg) You can see the detector is detecting movement, but the zone is not going active as the others. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/f/9f2f13b980ac2fc816a3a536cae8e9441df90709.jpeg) From Homey app store: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/e/1ef2fd79387ac8021b9bd4d5dc28725d1c02f6d1.jpeg) ---
**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:** [January 7, 2023, 8:03pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/2 "2023-01-07T20:03:42Z")
Hi, The motion or contact capability should be `alarm_*` afaik. When you search for your sensor at the [developer page](https://tools.developer.homey.app/tools/devices), you can check that: ![Screenshot_20230107-205905_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/6/263af4f89b32548fbe9894bcc62c6fad65d95e06.jpeg) > ![Screenshot_20230107-205357_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/b/6b29263b331d4c7e1276a40e837788f6bb5bbe3e.jpeg) #### Did you check this setting? (_a recently added option for sensors_) > ![Screenshot_20230107-205158_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/7/c74ec018918bb75c3ca4aec3d66af38674dc5811.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:** [January 7, 2023, 8:19pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/3 "2023-01-07T20:19:10Z")
Indeed, judging those flow cards they aren’t using any default alarm capabilities, neither for the door/window sensor, or the water alarm for the water sensor. ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [January 7, 2023, 8:35pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/4 "2023-01-07T20:35:41Z")
The sensor is looking like this from the developer page: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/5/b58cbf450c50b53ea38401e4699a7d1019e207c9.png) It does not have the same options as my Aqara sensor. This is which indicator to show: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/8/3898a240b2efba747b5cef096ca3e13ab3fe88f1.png) This is advanced properties from my new sensor: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/5/f5273a8fd6a9c002e4a2ea9bb082c61cb80a0081.png) This is advanced properties from Aqara: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/3346d05dcb1455eb1e054e4893ef0f4508a38930.png) ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [January 7, 2023, 8:36pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/5 "2023-01-07T20:36:24Z")
Should this be communicated to the developers so they can fix it right away? ---
**Author:** ![TedTolboom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tedtolboom/32/12081_2.png) [@TedTolboom](https://community.homey.app/u/TedTolboom)\ **Post date:** [January 7, 2023, 8:58pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/6 "2023-01-07T20:58:42Z")
It indeed uses a custom capability… It should use the default `alarm_motion` capability instead as defined in the SDK. ---
**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\ **Post date:** [January 7, 2023, 9:21pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/7 "2023-01-07T21:21:25Z")
As a temporary workaround (until it is fixed) 1 create a virtual device (sensor) 2 Add this virtual device to the same zone 3 create a flow that is triggered by your sensor and sets the “alarm\_motion” value of the virtual sensor ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/b/7bde508c186d459c4ac2bacdd98e62886b885042.png) 4 reset the “alarm\_motion” by a timer or another flow hat is triggered by your motion sensor Now your zone will become active by the sensor ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [January 8, 2023, 6:43pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/8 "2023-01-08T18:43:30Z")
Which if these ‘then’ cards are yu using to set the “alarm\_motion” value of the AVD? ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/2/c201c148871e0558c716cd2244cc6e8a363d39ab.png) ---
**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:** [January 8, 2023, 7:27pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/9 "2023-01-08T19:27:33Z")
the AVD should have a YesNo field of type alarm\_motion. > ![Screenshot_20230108-201604_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/4/b470b27da492bfc98000bea560448bf0b0aefc93.jpeg) Then a flow card must be available to set/unset it > ![Screenshot_20230108-202134_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/2/b29fee09b6a054418aa30dfb18a9268386f6c82c.jpeg) ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [January 8, 2023, 7:35pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/10 "2023-01-08T19:35:19Z")
Thank you for this! ---
**Author:** ![Tirrazo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tirrazo/32/55444_2.png) [@Tirrazo](https://community.homey.app/u/Tirrazo)\ **Post date:** [January 8, 2023, 10:17pm UTC](https://community.homey.app/t/zone-is-not-going-active/74725/11 "2023-01-08T22:17:09Z")
![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/c/fc8d1a134e06b9c9f94f7da52efc61bc52b6e059.png) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/8/58ee341983c885748acba01eca4412fc6b4bdcf9.png) So the zone itself seems to work, but it is staying active forever as the motion detector triggered. Shouldn’t it deactivate as the motion detector is not detecting movement anymore? Tried to do it this way, seem to work: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/c/cc7d43a3b0cda5cb6bda19a9ff891200bc51f865.png) ---
**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:** [January 9, 2023, 11:05am UTC](https://community.homey.app/t/zone-is-not-going-active/74725/12 "2023-01-09T11:05:33Z")
Just remove the logics card. Yes you should set the AVD ‘alarm’ to NO via a flow. It does not reset by itself.