# Cannot set parameter 81 (LED Behaviour on Alarms) for Aeotec Multisensor 6

**URL:** <https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811>\
**Category:** Questions & Help\
**Tags:** z-wave, homey-pro\
**Created:** [April 16, 2025, 12:55pm UTC](https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811 "2025-04-16T12:55:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TBrokke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tbrokke/32/122263_2.png) [@TBrokke](https://community.homey.app/u/TBrokke)\
**Post date:** [April 16, 2025, 12:55pm UTC](https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811/1 "2025-04-16T12:55:02Z")

</div>

I’m trying to turn of the blinking LED on movement on some of my Aeotec Multisensor 6’s (in bedrooms, as it’s a bit annoying at night). I can change that parameter to “No” in Homey, but it has zero effect. I’ve tried it on multiple sensors.

Any ideas?

All my multisensors are USB powered, so there should be no need to wake them up before changing parameters.

Getting this to work was no problem with my previous smart home system (Futurehome).

---

<div class="post-metadata">

**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:** [April 16, 2025, 4:18pm UTC](https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811/2 "2025-04-16T16:18:24Z")

</div>

If changing a setting doesn’t have any effect, I think you’d contact the app developer. You can find contact info at the bottom of the homey.app store page of the Aeotec app.

---

<div class="post-metadata">

**Author:** ![TBrokke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tbrokke/32/122263_2.png) [@TBrokke](https://community.homey.app/u/TBrokke)\
**Post date:** [May 12, 2025, 6:04pm UTC](https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811/3 "2025-05-12T18:04:33Z")

</div>

OK, will do. Thanks! 👍

---

<div class="post-metadata">

**Author:** ![K\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k_s/32/11635_2.png) [@K\_S](https://community.homey.app/u/K_S)\
**Post date:** [August 16, 2026, 1:23pm UTC](https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811/4 "2026-08-16T13:23:49Z")

</div>

Did you ever get this resolved? I have the same issue

---

<div class="post-metadata">

**Author:** ![TBrokke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tbrokke/32/122263_2.png) [@TBrokke](https://community.homey.app/u/TBrokke)\
**Post date:** [August 24, 2026, 6:59am UTC](https://community.homey.app/t/cannot-set-parameter-81-led-behaviour-on-alarms-for-aeotec-multisensor-6/134811/5 "2026-08-24T06:59:40Z")

</div>

No, unfortunately not. The issue persists, and I haven’t been able to get a reply from the app developer.