Joins to Hubitat as Device, but there's no driver that works with it. None of the existing Aqara motion sensor drivers work. No motion state appears.
Here's the fingerprint, but I doubt that's going to help anything. Someone that knows how to write drivers needs to have one of these. That person is not me.
It doesn't join to the Mijia hub. They don't have a profile for the Aqara T1 or P1 devices, but it does join to HA using the Mijia Multimode hub as the controller with Zigbee HA, but again, it doesn't have a driver so no motion entity appears.
However, it does join to the Aqara HomeKit hub (the non E1 version) that is unsupported. You just have to tell the hub you're joining a T1 motion sensor and it pairs with all the options available.
But there's a catch when using it with the unsupported hub. Tapping more settings lets you get to the unique features of the sensor and do the stuff you couldn't do with the original sensor without physical modification.
Right after pairing, it will respond to adjusting the detection interval, turning the trigger indicator on or off, and setting the sensitivity.
But after a while, it stops responding to the settings changes, and will give you a failed to configure message.
You then have to remove the devices and rejoin it so you can get that short window to make changes to its configuration. But that seems to be a viable workaround.
It takes quite a long time to appear in HomeKit, but it eventually does. No settings can be changed in HomeKit, and even if you have the sensor configured to respond at quick intervals (10 seconds for example), HomeKit will not reset to no motion detected in less time than 30 seconds. Not unexpected, and it still makes the sensor useful for capturing motion frequently to keep lights on or capture every movement possible.
Not prefect, but not horrible either. As long as it keeps working with the Aqara hub I have, I'll keep it and just trigger a Hubitat Virtual Switch via HomeKit Automations.