You mean like this notice towards the beginning of the release notes for 2.0.5 that you surely read before applying the optional update whose installation you are in total control of to your hub? 
(It was also mentioned well before release in the Xiaomi driver thread by author, who was contacted by Hubitat staff during beta testing of 2.0.5 after your friendly neighborhood tester[s] discovered the issue.) That being said, if you haven't applied two or more hotfixes in 2.0.5 yet, a 2.0.4 build should still be available in the port 8081 interface for you to roll back to if you want. See: Rollback to 2.0.4? (and if it's too late for you and the Xiaomi drivers don't get updated before then, Support can probably manually make an older version available to your hub if you ask nicely, or at least I think this is something they've been able to do in the past).
Just tried on both my hubs and the "old," expected behavior is still happening for me, so I wasn't able to reproduce this. Firefox 65 on macOS 10.14, for what it's worth.
