For me, the Hubitat chose my new Xioami Door/Window device driver when I paired my Xiaomi "original" button and I can check the Events to make sure it's still connected and sending reports, but since the "Device" device handler produces log messages, you could keep your Log window open to watch for that. If left idle, it should send a "status report" message every 60 minutes which will look like this:
read attr - raw: 81470100003002FF4C0600100121BA0B21A813240100000000215D062058, dni: 8147, endpoint: 01, cluster: 0000, size: 30, attrId: FF02, encoding: 4C, value: 0600100121BA0B21A813240100000000215D062058
If the Iris SmartPlug can pass on all messages and allow Xioami devices to remain connected, that would be awesome. Thank you for the feedback, and let us all know how it does. I do wish the Hubitat could give ZigBee mesh routing information. I'm going to have to get a ZigBee sniffer myself.
Not yet. But I have already done all the testing I need to make it. The big problem is how to approach the functionality of the device driver, considering that the button's hardware supports multi-clicks, and sends unique messages for double to quadruple-clicks.
Please refer to my Xiaomi device driver forum thread for more detailed information on my findings with the round button. I'm hoping to get other user's input on what they'd like from the device driver before I sit down to complete it.
