# Heiman HS2WD-E siren: state.alert always remains at "none"

**URL:** <https://forum.phoscon.de/t/heiman-hs2wd-e-siren-state-alert-always-remains-at-none/2101>\
**Category:** REST-API Support\
**Created:** [June 15, 2022, 9:40pm UTC](https://forum.phoscon.de/t/heiman-hs2wd-e-siren-state-alert-always-remains-at-none/2101 "2022-06-15T21:40:24Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![BabaIsYou](https://forum.phoscon.de/user_avatar/forum.phoscon.de/babaisyou/32/3079_2.png) [@BabaIsYou](https://forum.phoscon.de/u/BabaIsYou)\
**Post date:** [October 7, 2022, 4:28pm UTC](https://forum.phoscon.de/t/heiman-hs2wd-e-siren-state-alert-always-remains-at-none/2101/21 "2022-10-07T16:28:24Z")

</div>

I’m clearly not familiar with alarm management in Zigbee environment. I used DDF proposed by @Swoop related to issue [https://forum.phoscon.de/t/heiman-warningdevice-ef-3-0-siren-no-battery-and-tampered-status/2346](https://forum.phoscon.de/t/heiman-warningdevice-ef-3-0-siren-no-battery-and-tampered-status/2346) opened by @monpelaud. I just added ZHABattery as a suggestion because the specific cluster 0001 has attributes for that purpose.

---

_[View the full topic](https://forum.phoscon.de/t/heiman-hs2wd-e-siren-state-alert-always-remains-at-none/2101)._
