# HomeyKit

**URL:** <https://community.homey.app/t/homeykit/2731>\
**Category:** Apps\
**Created:** [October 12, 2018, 9:41am UTC](https://community.homey.app/t/homeykit/2731 "2018-10-12T09:41:05Z")\
**Posts on this page:** 1\
**Showing post:** 214

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 18, 2022, 5:13am UTC](https://community.homey.app/t/homeykit/2731/214 "2022-04-18T05:13:18Z")

</div>

> [@dthiemann](#):
>
> I already can see the the class type is different (sensor and homealarm).

Yes, and that’s exactly the issue: 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.

---

_[View the full topic](https://community.homey.app/t/homeykit/2731)._
