# Aeotec multisensor first generstion **URL:** \ **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:** 2
**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 30, 2019, 9:22pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/21 "2019-01-30T21:22:47Z")
No solution as far as I know. I reported to athom 7th of January and got the following reply the 10th: **Bram** (Athom) Jan 10, 12:51 CET Hi Christian, This “bug” should be resolved in the next update of the Aeotec app. Sorry for the inconvenience! Best Regards, Bram Athom Support Stay posted on Facebook by liking our page: [https://www.facebook.com/homey](https://www.facebook.com/homey)! ---
**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:** [February 20, 2019, 9:46pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/22 "2019-02-20T21:46:05Z")
Hmmm still nothing… ---
**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:** [February 21, 2019, 6:26am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/23 "2019-02-21T06:26:33Z")
Indeed, is it that difficult? The sensors did there job perfectly on early versions. I hope someone is working on a solution? ---
**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:** [February 28, 2019, 8:27pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/24 "2019-02-28T20:27:13Z")
@Bram I received a mail form github that the issue is fixed on the beta app. I installed the beta app but the problem is still not fixed, no change. Motion sensor is still not working. Sadly they shutdown github issues so reporting back (as asked in the mail) is not possible. So after long waiting this problem is still not fixed, hope athom can fixed it this time a bit quicker, this takes really to long… ---
**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\ **Post date:** [March 1, 2019, 1:28am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/25 "2019-03-01T01:28:43Z")
Since github has been shut down : For support or issue resolution, first have a look at [https://support.athom.com](https://support.athom.com) and if you cant find an answer there then you create a new ticket here [https://support.athom.com/hc/requests/new](https://support.athom.com/hc/requests/new). If you need help in how to create a support request you can find more information [here](https://support.athom.com/hc/en-us/articles/360015784034-Submit-a-support-request). ---
**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:** [March 1, 2019, 9:08pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/26 "2019-03-01T21:08:45Z")
@Bram received again an update of the beta app and now the whole app crashes constantly… ---
**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:** [March 6, 2019, 9:08am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/27 "2019-03-06T09:08:14Z")
Same here, the app crashes. ---
**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:** [March 10, 2019, 5:21pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/28 "2019-03-10T17:21:42Z")
Please send in a support to athom about it otherwise they do nothing… I reported it but nothing seems to be happening, sadly i first had a partly working sensor and now a fullny NONE function sensor. The sensor became fully unusable since last update, thx for that… ---
**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:** [March 10, 2019, 7:24pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/29 "2019-03-10T19:24:57Z")
Found a way to fix this. Seeing @Caseda’s [comment on the old forum](https://forum.athom.com/discussion/comment/36130/#Comment_36130). First set motion to “no” and save settings (push black button and then press save within a few seconds). Then set motion to “yes” and save the settings again. After that it will work (at least for me). I also set the raw parameter “5,1,2”, [but that shouldn’t be needed](https://github.com/athombv/com.aeotec/blob/ead76ab114b1d1062c10363b4226fbf27e621c69/drivers/ZW074/driver.compose.json#L41). ---
**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:** [March 10, 2019, 8:17pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/30 "2019-03-10T20:17:40Z")
currently the whole app is not working, i installed the beta app and since the last beta app update the app constantly crashes which makes the sensor complete useless. I cannot change any setting etc, the whole sensor icon is greyed out in devices… Also it seems impossible to install the stable version over the beta version, to do that i have to completely remove the app and install it again, doing that all flows brake which use the sensor… ---
**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:** [March 10, 2019, 9:26pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/31 "2019-03-10T21:26:01Z")
What’s the crash (log) say? (you can see it by clicking on the app, then on the red tekst that it u stopped working) ---
**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:** [March 10, 2019, 10:43pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/32 "2019-03-10T22:43:03Z")
don’t know, i disabled the app, it kept crashing and nothing worked anymore. The crash log was send to athom. Sadly just enable and disable the app is not the solution, the app only disables when you reboot homey. So when it keeps crashing and you disable the app it keeps reporting it crashed until you reboot homey, after reboot the app is really disabled and does not send and reports any crashes anymore. So i do not enable it only to look for a log… I wait until athom fixes the problem, i hope it will be shortly… ---
**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:** [March 11, 2019, 5:22am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/33 "2019-03-11T05:22:52Z")
> probably ---
**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:** [April 1, 2019, 7:26pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/34 "2019-04-01T19:26:04Z")
Hi, I still have the same issue, no motion detection on the latest beta app 2.0.29. Anyone else got it working? ---
**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:** [April 14, 2019, 5:59pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/35 "2019-04-14T17:59:18Z")
Still no solution for our sensors? Aeotec is a normal brand… ---
**Author:** ![JoakimOgren](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joakimogren/32/9225_2.png) [@JoakimOgren](https://community.homey.app/u/JoakimOgren)\ **Post date:** [April 19, 2019, 8:41am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/36 "2019-04-19T08:41:33Z")
I have the same issue when when I remove and add a MultiSensor 6 (ZW100-C). Motion is not reported at all. Tampering alarm is reported. Workaround as proposed by @bvdbos works: - Add the device - Set “Motion Sensor Sensitivity” setting to “Off” - Save (and wake up device by pressing button at the back) - Set “Motion Sensor Sensitivity” setting back to “Level 5 (maximum)” (or whatever you want) - Save (and wake up device by pressing button at the back) Another observation is that “Wake-up interval” is now disabled. I think it used to be enabled by default earlier (1-2 years ago or more). ---
**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:** [April 23, 2019, 5:01pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/37 "2019-04-23T17:01:47Z")
Tried a lot, but no luck with my first generation sensors ds805-zweu 😢 ---
**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:** [May 9, 2019, 10:15pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/38 "2019-05-09T22:15:31Z")
Problem is solved last week, download latest beta app from store. I send my gen1 sensor to athom, they used it to fix the problem and can confirm the fix works now. Motion detection is finally working again on 4on1 multisensor gen1 ---
**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:** [May 10, 2019, 4:58am UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/39 "2019-05-10T04:58:43Z")
Wow, that’s great. I am happy. Gonna try tonight. And Thank you for sending your device 😉 ---
**Author:** ![Cyril](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cyril/32/13111_2.png) [@Cyril](https://community.homey.app/u/Cyril)\ **Post date:** [July 22, 2019, 4:48pm UTC](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117/40 "2019-07-22T16:48:57Z")
Hi, I have the same problem with my DSB05 and 2.0.29 stable app version. The changelog say **2.0.24 - 2.0.26** - Fixes motion alarm on the DSB05 Multisensor 4-in-1 I have tried off/save/on/save for the motion detection parameter without success Problem is solved for other users ? Thanks Edit : works with beta version 2.0.30. is it planned to update the stable version with the fix ? Thanks [Previous page](https://community.homey.app/t/aeotec-multisensor-first-generstion/6117.md?page=1)