# \[Abandoned\] deCONZ

**URL:** <https://community.homey.app/t/abandoned-deconz/29390>\
**Category:** Apps\
**Tags:** app, zigbee, devices\
**Created:** [May 5, 2020, 9:57am UTC](https://community.homey.app/t/abandoned-deconz/29390 "2020-05-05T09:57:44Z")\
**Posts on this page:** 1\
**Showing post:** 875

<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 18, 2022, 7:29pm UTC](https://community.homey.app/t/abandoned-deconz/29390/875 "2022-04-18T19:29:19Z")

</div>

There’s one “thingy” tho.  
It seems the “sensor” capability is used for measure devices.  
And “homealarm” is used for PIR and contact sensors.  
(But then all PIR and motion sensors shouldn’t work @ Homey ?)

> [@HomeyKit](https://community.homey.app/t/homeykit/2731/214):
>
> the `alarm_motion` capability is only supported for `sensor` devices, not for `homealarm` devices. It doesn’t really make sense to use the latter device class, because that’s meant for home alarm _controller_ devices, not for sensors that might be used to trigger an alarm but have lots of other applications too.

So it’s a bit of trial and error probably if you change the code

Search command:  
[https://github.com/ZeppDK/HomeyCONZ/search?p=1&q=homealarm](https://github.com/ZeppDK/HomeyCONZ/search?p=1&q=homealarm)

---

_[View the full topic](https://community.homey.app/t/abandoned-deconz/29390)._