IMPORTANT ANNOUNCEMENT FOR ALL XIAOMI / AQARA USERS
Hubitat staff have informed me that in the next firmware update, there will be a significant change in the way that the raw payload data of messages from ZigBee devices is parsed. The change was necessary in order to address an issue affecting certain kinds of messages (specifically with variable length data types.)
For the vast majority of device drivers, this upcoming change won't require any updates to the device driver code, because for messages following normal ZigBee standards, helper methods are available to convert the raw payload data into a format that can be easily used to generate device events.
Unfortunately, the entire collection of Xiaomi / Aqara device drivers that I am maintaining all have at least one function that relies on non-standard messages. This means I need to examine how the firmware change affects incoming message data, make necessary changes to the code, and then test it with my devices on my hub.
Although I could start making changes to the code of all of the device drivers before the firmware is released, I can't verify 100% that any of it will work until I've got it the new firmware running on my own hub, and I am not part of the beta testing program.
In addition, I am about to leave town until this weekend, so the soonest I can do anything would be the middle of next week. This is because maintaining this collection of device drivers is not my paid job and I work on these for free, in my spare time, when I am able to.
So if the next firmware is released before I am able to start making changes (which is likely), all I can do is ask for your patience. Please understand that upgrading to the new firmware will likely result in a complete loss of most, if not all, functionality of any Xiaomi / Aqara devices, until I am able to update the device drivers.
I apologize for any inconvenience this may cause, and again ask for your patience. Many thanks.
EDIT: All of my Xiaomi / Aqara device drivers have been updated with a compatibility fix for hub v2.0.5 or newer. Please see this post for details.
