# Aeotec multisensor first generstion

**URL:** <https://community.homey.app/t/aeotec-multisensor-first-generstion/6117>\
**Category:** Devices\
**Created:** [December 31, 2018, 9:15am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117 "2018-12-31T09:15:41Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Walter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/walter/32/26304_2.png) [@Walter](https://community.homey.app/u/Walter)\
**Post date:** [December 31, 2018, 9:15am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/1 "2018-12-31T09:15:41Z")

</div>

Is it just me?  
I have three aeotec multisensors. Motion detection is not working anymore, other values are ok. Installed the app again, but no luck. All the sensors are usb powered. (on 2.0)

---

<div class="post-metadata">

**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:** [December 31, 2018, 9:53am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/2 "2018-12-31T09:53:57Z")

</div>

I only have one but it it working (as well as it ever has)  
I’ve always had intermittent trigger failures with it but I think it’s the sensor as the LED on the sensor doesn’t come on. It normally fixes itself after a while. Even when it’s not detecting movement the tamper alarm still works. It can also be a bit slow to detect.  
Using Homey V2-rc9.

---

<div class="post-metadata">

**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:** [December 31, 2018, 3:24pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/3 "2018-12-31T15:24:53Z")

</div>

I have the same with my new Multi 6. After adding everything is reported correctly except movement. Every sensor gets updated, tamper alarm works fine, but no movement at all. At some point when i re-added the sensor the movement came on but never went off. Doesn’t make a difference if powered by battery or usb.

---

<div class="post-metadata">

**Author:** ![yemoH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yemoh/32/3545_2.png) [@yemoH](https://community.homey.app/u/yemoH)\
**Post date:** [December 31, 2018, 9:44pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/4 "2018-12-31T21:44:34Z")

</div>

I’m not sure which version I have for the multi sensor, but movement detection is working fine for me. It activated lights multiple times a day. My Honey is still on 1.5.13.

---

<div class="post-metadata">

**Author:** ![KonradWalsh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/konradwalsh/32/147_2.png) [@KonradWalsh](https://community.homey.app/u/KonradWalsh)\
**Post date:** [January 1, 2019, 9:36pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/5 "2019-01-01T21:36:09Z")

</div>

yes … me too

---

<div class="post-metadata">

**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:** [January 2, 2019, 12:37pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/6 "2019-01-02T12:37:09Z")

</div>

Eh, me too what exactly?

---

<div class="post-metadata">

**Author:** ![KonradWalsh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/konradwalsh/32/147_2.png) [@KonradWalsh](https://community.homey.app/u/KonradWalsh)\
**Post date:** [January 2, 2019, 12:45pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/7 "2019-01-02T12:45:30Z")

</div>

Sorry… I was replying to the OP.

I am having the same issue originally stated… No motion

---

<div class="post-metadata">

**Author:** ![yemoH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yemoh/32/3545_2.png) [@yemoH](https://community.homey.app/u/yemoH)\
**Post date:** [January 2, 2019, 6:47pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/8 "2019-01-02T18:47:32Z")

</div>

Are you on Homey 1 or 2?

---

<div class="post-metadata">

**Author:** ![KonradWalsh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/konradwalsh/32/147_2.png) [@KonradWalsh](https://community.homey.app/u/KonradWalsh)\
**Post date:** [January 2, 2019, 10:50pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/9 "2019-01-02T22:50:23Z")

</div>

Homey 2

---

<div class="post-metadata">

**Author:** ![yemoH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yemoh/32/3545_2.png) [@yemoH](https://community.homey.app/u/yemoH)\
**Post date:** [January 3, 2019, 4:17pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/10 "2019-01-03T16:17:46Z")

</div>

I think there is a correlation when three out of four user who report an issue are on Homey 2.

---

<div class="post-metadata">

**Author:** ![KonradWalsh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/konradwalsh/32/147_2.png) [@KonradWalsh](https://community.homey.app/u/KonradWalsh)\
**Post date:** [January 3, 2019, 5:04pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/11 "2019-01-03T17:04:50Z")

</div>

In fact… The new insights 2.0 page doesn’t even show the Motion as an option the device

---

<div class="post-metadata">

**Author:** ![bvdbos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bvdbos/32/2352_2.png) [@bvdbos](https://community.homey.app/u/bvdbos)\
**Post date:** [January 3, 2019, 5:46pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/12 "2019-01-03T17:46:23Z")

</div>

boolean data isn’t shown atm, you can file a report:  
[https://support.athom.com/hc/nl/requests/new](https://support.athom.com/hc/nl/requests/new)  
(I did, asking for a 0/1 graph for booleans)

---

<div class="post-metadata">

**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:** [January 4, 2019, 8:08am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/13 "2019-01-04T08:08:55Z")

</div>

You can see the on/off log in the actual device on the … ‘tab’/view.

---

<div class="post-metadata">

**Author:** ![B3rt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b3rt/32/9435_2.png) [@B3rt](https://community.homey.app/u/B3rt)\
**Post date:** [January 5, 2019, 7:54pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/14 "2019-01-05T19:54:05Z")

</div>

same here, got 2 of these sensors and both NO motion detection anymore.  
I use Homey 1…

It seems it stopped working around 28 december

---

<div class="post-metadata">

**Author:** ![Walter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/walter/32/26304_2.png) [@Walter](https://community.homey.app/u/Walter)\
**Post date:** [January 5, 2019, 9:35pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/15 "2019-01-05T21:35:47Z")

</div>

I hope someone is looking at this.

---

<div class="post-metadata">

**Author:** ![bvdbos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bvdbos/32/2352_2.png) [@bvdbos](https://community.homey.app/u/bvdbos)\
**Post date:** [January 6, 2019, 7:30am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/16 "2019-01-06T07:30:37Z")

</div>

Did you guys file a report at [https://support.athom.com/hc/nl/requests/new](https://support.athom.com/hc/nl/requests/new) ?

---

<div class="post-metadata">

**Author:** ![Walter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/walter/32/26304_2.png) [@Walter](https://community.homey.app/u/Walter)\
**Post date:** [January 6, 2019, 9:25am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/17 "2019-01-06T09:25:47Z")

</div>

Yep

---

<div class="post-metadata">

**Author:** ![Christian](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/christian/32/8183_2.png) [@Christian](https://community.homey.app/u/Christian)\
**Post date:** [January 6, 2019, 11:06am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/18 "2019-01-06T11:06:27Z")

</div>

I have the same issue, no motion is ever reported. Homey sw 1.5.13, aeotec app version 2.0.18. The problem started when I upgraded to the latest aeotec app. In the same update my aeotec RGB ledbulbs also stopped responding to on/off commands.

---

<div class="post-metadata">

**Author:** ![B3rt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b3rt/32/9435_2.png) [@B3rt](https://community.homey.app/u/B3rt)\
**Post date:** [January 15, 2019, 10:29pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/19 "2019-01-15T22:29:38Z")

</div>

i allready reported this issue to Athom, they looked into it and reported this issue to the app developer.

Athom could not find anything wrong in my logs, the advise was to try to repair the devices and reinstall the app.  
I declined that because this would destroy a lot of my flows, they then advised to wait for an update of the app in the hope the developer would fix this problem.

---

<div class="post-metadata">

**Author:** ![Walter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/walter/32/26304_2.png) [@Walter](https://community.homey.app/u/Walter)\
**Post date:** [January 30, 2019, 8:58pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/20 "2019-01-30T20:58:31Z")

</div>

Still no solution for this?

[Next page](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117.md?page=2)
