It's a manufacturer specific cluster...
Unless you sniff the frames while this device is connected to it's native hub while monitoring what it produces via its native app, it's unlikely you will be able to decode these payloads.
Now having said all that, encoding 42 is an ascii string, which may be readable and easier to decode...
I've been able to pair my Konke motion sensor (which has the same device footprint) with your driver but for some reason it doesn't display or detect motion under the device attributes. Any ideas?
And I can confirm it works on Channel 15 but it didn't work on channel 24. I'm SmartThings user so I can't say anything about compatibility with Hubitat though.