That would be the difference, DirkG is using the LWR01, whereas I am using an LWR02 that has the additional sensors (temp & humidity) instead of the USB C powered option, and is roughly half the size of the older LWR01.
It looks like they have changed the PIR & 24GHz mmWave detection sensor endpoint from ‘alarm_motion’ to ‘alarm_presence’.
If you compare the drivers of both sensors on GitHub (link), the LWR01 uses alarm_motion and the LWR02 uses alarm_presence. In my opinion, alarm_presence or alarm_occupancy is technically correct.
I already pointed out this issue last year (link), but @Doekse hasn’t fixed it yet, for whatever reason.
However, this difference is likely the reason why the LWR002 is not yet supported.
Totally missed that GitHub issue! My bad.
The thing is, I don’t actually decide whether a device uses alarm_motion or alarm_presence. Homey simply maps the Matter clusters supported by the device, and Matter has separate clusters for motion and presence.
When the LWR01 launched, presence wasn’t part of the Matter specification yet, so they used the motion cluster instead. That’s why it shows up as alarm_motion rather than alarm_presence.
But indeed, this doesn’t affect the actual functionality!
I was hoping you’d respond to my post… 
It’s true that this generally doesn’t affect the functionality, but it would still be nice if the correct capability were used.
That would be some feedback for Lafaer, they would need to do a firmware update to change the cluster
It’s getting OT here, sorry!
Are you sure @Doekse?
Because this is what the LWR01 provides:
Is there a way to get these different Matter clusters for alarm_motion, alarm_presence & alarm_occupancy to be supported by apps like Device Watchdog?
With all the problems that have been plaguing the Aqara FP300’s (of which I have many of, all with varying problems, false positives, stuck detection, dropping off the network etc) I have been trying a Lafaer LWR02 for the last couple months, and it has been faultless with its detection reliability and sensor readings… the only sticking point I have with it, is this issue with some community apps not seeing it due to this difference between alarm_motion and alarm_presence 
Is there no way to group the Matter clusters, or alias them in the device settings or drivers… there must be something programmatic that can be done to make them compatible?
Is there no way that Homey can alias the different names for essentially the same function… to save all the different manufacturers having to change their firmware for their various products?
I have no clue how these apps work, to be honest. An app could simply map all capabilities that trigger Zone activity. We don’t restrict apps to only looking at alarm_motion. Both alarm_occupancy and alarm_presence are also standard system capabilities that an app can use.
I’ll need to dive into this, maybe for newer batches they used the right clusters. What capabilities get added when you pair it with Homey?
Pls. see my post #1869.
The Sensor was added already 11-2025.
Repairing might do the trick!
Before even turning to the forum, the first things I tried were repairing, removing and re-adding, resetting the device to factory and re-adding, restarting the Lafaer app, deleting and reinstalling the Lafaer app, restarting the Device Watchdog app, re-booting Homey. All the standard fault finding and resolving steps I’ve grown accustomed to doing having worked 2nd and 3rd line IT support. Only when all those steps failed to resolve the issue did I come here to try and find more answers, not having any access to logs (which I find highly bizarre and frustrating that the developer tools page had zero log access… so you just end up blindly firing off Diagnostic reports in to the ether hoping they are helpful to whoever is on the receiving end). I find it highly irregular that you can’t access information about your own device in this way… GDPR and all that… surely you should have the right and ability to access information about your own device and all information it may hold about you and your home?
I think it would also be helpful to app developers if the Diagnostic Report generating pop-up had mandatory fields for Name and email address, so they don’t get hundreds of anonymous reports in all sorts of languages with not identification of who sent it, or way to contact them to ask for additional details on the problem.
Let’s take a couple of steps back, as I’m not entirely sure I understand what the issue is here.
You’re using the LWR02, which exposes the alarm_presence capability. That capability is not correctly mapped in the Device Watchdog app, right? So the issue isn’t actually with the Heimdall app, which is what this thread is about? 
My comment about repairing was in regard to @DirkG’s LWR01 which was paired quite some time ago and currently exposing the alarm_motion capability.
Apologies, my confusion there was that DirkG’s LWR01 is working with the alarm_motion capability, it is my LWR02 that uses alarm_presence that is not seen by the app and doesn’t work.
If DirkG did a repair of his device and it changed to the alarm_presence, he would then be in the same predicament as I, with the app not seeing or working with the sensor.
I hope that makes sense?
And alarm_presence would be the correct capability to use here.
I think the proper solution would be to update the apps that currently only look at alarm_motion to also support alarm_presence and alarm_occupancy, rather than building fallbacks into every other app just to maintain compatibility with them.
After repairing the sensor, alarm_motion is still present.
In that case Lafaer is still using the motion clusters instead of the presence ones
I don’t disagree with that, at all, it seems this app doesn’t use or account for the alarm_presence… which is what the LWR02 uses. And also the Aqara FP300 uses both, but the alarm_motion is paired to the overly sensitive PIR sensor, whereas the more reliable mmWave radar sensor seems to be paired to the alarm_presence capability, so can’t be used in this app at present.
Also, @Doekse I do apologise for my mini rant about the logging, diagnostics reports and GDPR… but I do think they are valid points, after some of the discussions I have had in messages with app developers… so while we are talking, I would like to put forward the suggestions for this. Thank you kindly good sir 
