You mean the beta DTH in the bspranger/Xiaomi thread? That would also be me, with help and input from a few ST users, and notably with help and some fantastically useful code from user oltman on GitHub.
As for the adapted Hubitat device drivers, "you guys" = just me.
You should be able to follow the instructions listed below (posted by @veeceeoh) to do a manual pairing. The post is was written for the Smart Light Switch, but it worked for me with the Door/Window sensor. Also, if you haven't done so yet, first go and add its driver linked in the 1st post, and then do this.
NOTE: The devices with the New Zigbee Model ID are the new versions that don't work with the current device handlers.
An easy way to know that you've probably received one of the new versions of the above devices is that it will only pair as a generic "Device", instead of choosing the correct device driver.
To check the Zigbee Model ID, you should be able to view it while logged into your Hubitat hub when you view details about the device by clicking on it's name in the Devices page. Search for the "Data" row, near the bottom of the page, where you'll hopefully see something like this:
I don't have any of these new versions myself, and don't plan on purchasing more any time soon, so...
If any receives one of the above three models and it pairs as a "device" please post in this thread, and I'll explain how to get some log output which should hopefully help me to update the device driver to work correctly.
If you have a device with an Old Zigbee Model ID listed above, there's no need report back that they're working fine.
Since there's no mobile app for Hubitat like there is for SmartThings, I removed the human readable event time/date stamps from all of the Hubitat drivers because the only place you can view them is via the device details page for a single device when logged into your hub locally - in the Events list.
However I kept the Unix-format "Epoch" time/date stamps for use in WebCoRE, because that can be very helpful in creating Pistons.
If you just want to be able to view when events occurred for any device (not just Xiaomi devices), then click on the "Events" link at the top of the device details page for that device.
Was there some other reason you need to see human readable dates of events besides just viewing them?
Thanks for reporting in! However...
I messed up on that chart with the Zigbee Model IDs, and it's fixed now. Sorry about that!
The "old" Zigbee Model ID for the WXKG02LM that works fine with the current device drivers may appear either as lumi.sensor_86sw2Un or lumi.sensor_86sw2. Similarly, the "old" version of the WXKG03LM can appear either as lumi.sensor_86sw1lu or lumi.sensor_86sw1.
I only really need to hear from anyone who's recently bought one of the three listed devices which is only coming up as a generic "Device" when paired, and also has a New Zigbee Model ID.
Thanks for the info about Simple Event Logger. It looks like it would do the trick, but after searching, it doesn't look like anyone has ported it over yet. I will follow a thread where some have discussed it, but at this stage it doesn't look like anyone is taking on the challenge.
I have quite a few Xiaomi /Aqara devices and whenever I change to a new battery I see that it reports a battery level of 3.055V.
Would it be possible to change the max default voltage to this instead of 3.5 and maybe the min to 2.7V.
Mine never drop below 100% and changing to the above values starts to give a better reading. Not sure how accurate the readings are though.