Hi all,
Sharing this in case others run into the same thing — and to flag it for Lafaer.
I'm running the LWR02 on Homey via Matter/Thread, and it works great for lighting automation. However, it currently only exposes the alarm_presence capability in Homey. A number of popular third-party Homey apps — including the DIY security app "Heimdall" — only scan for alarm_motion, alarm_contact or alarm_vibration when building their device lists, so the LWR02 isn't picked up automatically by them.
For comparison, other mmWave sensors like the Aqara FP300 expose both alarm_motion and alarm_presence in parallel, so they work with these apps out of the box — no manual workarounds needed.
I've sent a feature request to support@gl-inet.com asking if the Homey integration could map the occupancy event to alarm_motion as well (in addition to alarm_presence), the way FP300 does. Curious if anyone else has hit this, or found a cleaner workaround than a virtual device + flow to mirror the capability.